tde-users December 2013

users@trinitydesktop.org

32 participants
27 discussions

tdebase-3.5.13.1 tqt3integration 'tqAppClass' was not declared in this scope

by Jerry Nettrouer II

[100%] Building CXX object tqt3integration/libqtkde/CMakeFiles/qtkde-shared.dir/qtkde.cpp.o cd /tmp/tdebase-3.5.13.1/build/tqt3integration/libqtkde && /usr/bin/c++ -Dqtkde_shared_EXPORTS -DHAVE_CONFIG_H -O2 -march=i486 -mtune=i686 -fvisibility=hidden -fvisibility-inlines-hidden -DQT_NO_ASCII_CAST -DQT_CLEAN_NAMESPACE -DQT_NO_STL -DQT_NO_COMPAT -DQT_NO_TRANSLATION -DQT_THREAD_SUPPORT -D_REENTRANT -include tqt.h -I/usr/lib/qt3/include -I/usr/include/tqt -DQT_NO_ASCII_CAST -DQT_CLEAN_NAMESPACE -DQT_NO_STL -DQT_NO_COMPAT -DQT_NO_TRANSLATION -DQT_THREAD_SUPPORT -D_REENTRANT -include tqt.h -fPIC -I/tmp/tdebase-3.5.13.1/build/tqt3integration/libqtkde -I/tmp/tdebase-3.5.13.1/tqt3integration/libqtkde -I/tmp/tdebase-3.5.13.1/build -I/tmp/tdebase-3.5.13.1/build/tqt3integration/utils -I/usr/lib/qt3/include -I/usr/include/tqt -o CMakeFiles/qtkde-shared.dir/qtkde.cpp.o -c /tmp/tdebase-3.5.13.1/tqt3integration/libqtkde/qtkde.cpp In file included from /tmp/tdebase-3.5.13.1/tqt3integration/libqtkde/qtkde.cpp:145:0: /tmp/tdebase-3.5.13.1/build/tqt3integration/utils/tqtkde_functions.cpp: In function 'QStringList getOpenFileNames(const QString&, QString*, long int, const QCString&, const QString&, QString*, bool)': /tmp/tdebase-3.5.13.1/build/tqt3integration/utils/tqtkde_functions.cpp:34:262: error: 'tqAppClass' was not declared in this scope /tmp/tdebase-3.5.13.1/build/tqt3integration/utils/tqtkde_functions.cpp: In function 'QString getSaveFileName(const QString&, const QString&, QString*, long int, const QCString&, const QString&, QString*)': /tmp/tdebase-3.5.13.1/build/tqt3integration/utils/tqtkde_functions.cpp:64:270: error: 'tqAppClass' was not declared in this scope /tmp/tdebase-3.5.13.1/build/tqt3integration/utils/tqtkde_functions.cpp: In function 'QString getExistingDirectory(const QString&, long int, const QCString&, const QString&)': /tmp/tdebase-3.5.13.1/build/tqt3integration/utils/tqtkde_functions.cpp:93:94: error: 'tqAppClass' was not declared in this scope /tmp/tdebase-3.5.13.1/build/tqt3integration/utils/tqtkde_functions.cpp: In function 'QColor getColor(const QColor&, long int, const QCString&)': /tmp/tdebase-3.5.13.1/build/tqt3integration/utils/tqtkde_functions.cpp:116:72: error: 'tqAppClass' was not declared in this scope /tmp/tdebase-3.5.13.1/build/tqt3integration/utils/tqtkde_functions.cpp: In function 'QFont getFont(bool*, const QFont&, long int, const QCString&)': /tmp/tdebase-3.5.13.1/build/tqt3integration/utils/tqtkde_functions.cpp:139:102: error: 'tqAppClass' was not declared in this scope /tmp/tdebase-3.5.13.1/build/tqt3integration/utils/tqtkde_functions.cpp: In function 'int messageBox1(int, long int, const QString&, const QString&, int, int, int)': /tmp/tdebase-3.5.13.1/build/tqt3integration/utils/tqtkde_functions.cpp:165:115: error: 'tqAppClass' was not declared in this scope /tmp/tdebase-3.5.13.1/build/tqt3integration/utils/tqtkde_functions.cpp: In function 'int messageBox2(int, long int, const QString&, const QString&, const QString&, const QString&, const QString&, int, int)': /tmp/tdebase-3.5.13.1/build/tqt3integration/utils/tqtkde_functions.cpp:190:160: error: 'tqAppClass' was not declared in this scope make[2]: *** [tqt3integration/libqtkde/CMakeFiles/qtkde-shared.dir/qtkde.cpp.o] Error 1 make[2]: Leaving directory `/tmp/tdebase-3.5.13.1/build' make[1]: *** [tqt3integration/libqtkde/CMakeFiles/qtkde-shared.dir/all] Error 2 make[1]: Leaving directory `/tmp/tdebase-3.5.13.1/build' make: *** [all] Error 2

9 years, 6 months

libogg0 conflicts with libogg0:i386 under ubuntu precise

by Stefan Endrullis

Hi folks, I'm using trinity on a 64 bit Ubuntu precise (12.04) installation and I want to report a very annoying bug caused by a package conflict of libogg0 from the trinity repository: https://bugs.launchpad.net/trinity-desktop/+bug/977103 Since trinity's libogg0 conflicts with Ubuntu libogg0:i386 several 32 bit applications such as adobe reader can no longer be installed on 64 bit trinity installations. Is there really a conflict between libogg0 and libogg0:i386 that needs to be in the package definition or can one just remove this tag? Best Regards, Stefan

10 years, 9 months

kmail 3.5.13.2

by Greg Madden

Wheezy amd64 Slavek repo. key binding 'ctl+a' used to select all messages in a folder, then 'ctl + j' would apply filters to the selected messages. 'ctl + a" not longer selects all messages. What happened? -- Peace, Greg

11 years, 1 month

Release date for R14?

by Jan Stolarek

Hi, I wanted to ask about current status of R14. I found the roadmap here: http://trinity.etherpad.trinitydesktop.org/39? Are things going more or less according to this schedule and we can expect R14 in a month or so? I'm asking because I'm planning to update to Wheezy on one of my machines, but I can delay it for a month or two and just install R14 without bothering to upgrade from 3.5.13.2. Janek

11 years, 2 months

TDE nighly builds & jessie binutils

by Dr. Nikolaus Klepp

Hi all! I'm going to do some tests on jessie & TDE nightly builds. It looks like some packages from TDE do not want binutils from jessie. Well, non of these packages are vital, but I thought I'd let you know. tdescreensaver-trinity : Hängt ab von: binutils (< 2.23.52.20130829) aber 2.23.90.20131017-1 ist installiert. tdeartwork-theme-window-trinity : Hängt ab von: binutils (< 2.23.52.20130829) aber 2.23.90.20131017-1 ist installiert. kworldclock-trinity : Hängt ab von: binutils (< 2.23.52.20130829) aber 2.23.90.20131017-1 ist installiert. eyesapplet-trinity : Hängt ab von: binutils (< 2.23.52.20130829) aber 2.23.90.20131017-1 ist installiert. tdeartwork-style-trinity : Hängt ab von: binutils (< 2.23.52.20130829) aber 2.23.90.20131017-1 ist installiert. kmoon-trinity : Hängt ab von: binutils (< 2.23.52.20130829) aber 2.23.90.20131017-1 ist installiert. kteatime-trinity : Hängt ab von: binutils (< 2.23.52.20130829) aber 2.23.90.20131017-1 ist installiert. fifteenapplet-trinity : Hängt ab von: binutils (< 2.23.52.20130829) aber 2.23.90.20131017-1 ist installiert. ktux-trinity : Hängt ab von: binutils (< 2.23.52.20130829) aber 2.23.90.20131017-1 ist installiert. kweather-trinity : Hängt ab von: binutils (< 2.23.52.20130829) aber 2.23.90.20131017-1 ist installiert. amor-trinity : Hängt ab von: binutils (< 2.23.52.20130829) aber 2.23.90.20131017-1 ist installiert. tdescreensaver-xsavers-trinity : Hängt ab von: binutils (< 2.23.52.20130829) aber 2.23.90.20131017-1 ist installiert. Hängt ab von: xscreensaver-data aber es soll nicht installiert werden. kodo-trinity : Hängt ab von: binutils (< 2.23.52.20130829) aber 2.23.90.20131017-1 ist installiert. Nik -- Please do not email me anything that you are not comfortable also sharing with the NSA. Dr. Nikolaus Klepp Einnehmerstraße 14 A-4810 Gmunden Tel.: +43 650 82 11 724 email: office(a)klepp.biz

11 years, 2 months

a puzzle, maybe or maybe not trinity-related

by dep

hi, folks. this is a puzzle; it's something that has happened occasionally for years but now has become frequent enough to be an annoyance, and i do not know enough about the mechanisms involved even to begin to troubleshoot it. here's what happens: i am going merrily along and doing my work when i send an email message or go to a webpage and get errors that the host could not be found -- the usual dns error. when this happens i use the handy system settings network configurator and invariably discover that all the nameservers that i have listed are now gone. i presume that this application writes to /erc/resolv.conf (which is now a link to a resolv.conf someplace else, in /run/resolv.conf, which is heaven knows where but i suppose is one of those virtualized filesystems the boys are so proud of). anyway, i usually keep three domain nameservers there, just in case one goes down. something is causing them to disappear. i haven't fiddled with this stuff since resolv.conf was hard-coded such that you'd su root, edit /etc/resolv.conf, save the file, and be happy evermore. but now the file says not to edit it because it will be overwritten anyway. so. any guesses as to what might be making my list of nameservers disappear? that failing, any good recipe for troubleshooting it to see who is eating my nameservers? and if not that, is there anyplace i can put them so that they won't get overwritten? thanks very much and merry christmas, everybody! -- dep The shortest distance between you and playing great acoustic guitar: the great new instructional DVDs from Marjorie Thompson, available at www.MarjorieThompson.com

11 years, 2 months

Trinity 3.5.13.2 on OS12.3, unresolved dependency

by Jagged O'Neill

High everyone, I have just installed Trinity from the binary repositories. I strictly followed the instructions on http://www.trinitydesktop.org/wiki/bin/view/Documentation/OpenSUSEBinaryIns… but zypper complained about a missing dependency. I'd bet a lot that was the accessibility package, because I clearly remember that I thought "Heck, I'm not that disabled...". It downloaded everything, then installed everything (at least it looked like that). But I couldn't get it to run. There was no startkde, no starttde, no kwin, no twin, no whatever. But it certainly installed a lot of files in /opt. To let you have a figure without sending the whole ls-lR: $ du -sh /opt/* 61M /opt/kde3 377M /opt/trinity That was yesterday. Now before sending this email, I just called YaST to check back for the dependency message, which now is obviously altered to trinity-desktop-3.5.13.2-2.oss123.opt.noarch requires trinity-tdeaddons >= 3.5.13.2, but this requirement cannot be provided There is a package called trinity-kdeaddons in the repo, but its size is just 0 bytes; the corresponding debugsource seems healthy (3.4MiB). This is the same for trinity-tdeaccessibility (0 vs. 2.7MiB). Other zero-size packages (except the meta packages) are: - trinity-gwenview-i18n-debugsource - trinity-kaffeine-mozilla-debugsource - trinity-kstreamripper-debugsource - trinity-libqt3-jni-devel - trinity-libtrinity-jni-devel - trinity-python-trinity-debugsource - trinity-rosegarden-debugsource - trinity-smartcardauth-debugsource - trinity-tdeadmin - trinity-tdeartwork (though YaST shows it as installed, but also describes it as a meta package) - trinity-tdebindings (shown as installed) - trinity-tdebindings-devel - trinity-tdebindings-java (shown as installed) - trinity-tdebindings-xparts-extras - trinity-tdegames - trinity-tdegames-devel - trinity-tdemultimedia - trinity-tdepim - trinity-tdesdk - trinity-tdesdk-devel - trinity-tdeutils - trinity-tdewebdev That's what I've found; maybe I missed a few --- operating yast over a low bandwidth vnc is a bit clumsy. Now YaST shows 1058 packages overall; rpm -qa reports 168 packages (I didn't count those shown as installed in YaST), and I'm sure that the download contained of 223 individual files. I have no idea which of the packages didn't install due to unresolved dependencies, or which are simply not covered by the trinity-desktop meta package, but many things that I actually expected were not installed, like kwin/twin, startkde/starttde, etc. when trying to install trinity-twin, YaST shows the missing tdeaddons dependency again, referring to trinity-desktop, not trinity-twin. I select "break trinity-desktop-3.5.13.2-2.oss123.opt.noarch by ignoring some of its dependencies" actually selects twin for installation. I will see how far this will work. Most of the above zero-sized files are not that important, but I definitely want to have kicker. Anyway, I think it'd be great if this would be fixed. No need to do it today though :-) Have a merry X-mas, best regards and thanks in advance, Jagged

11 years, 3 months

gui freeze.

by Felmon Davis

greetings! using Trinity Desktop, David Hare's exegnu, on Acer Aspire One 722 with kernel 3.2.0-0.bpo.4-686-pae. I can run Manjaro 3.9.4-1-xxx and Debian Trinity kernel 2.6.32-6-686 (also Hare's version) on this boxlet without a problem except I was fumbling with getting wifi started on the latter, thus the bright idea to up the kernel. (I can afford to 'play' on this machine.) the trouble is that booting into the gui causes touchpad and mouse to freeze at the login screen, requiring a reboot. I can boot via grub to the bash shell, get in as user and run 'sudo startx' or 'sudo kdm' and there's no problem. I've fished around but hoped someone would have a quick insight or fix. thanks. F. -- Felmon Davis Truth emerges more readily from error than from confusion. -- Francis Bacon

11 years, 3 months

never mind

by dep

of course, one minute after i hit send on the previous note the lightbulb went on and i thought of the proper google search term and now, apparently, the disappearing nameserver is, um, resolved. sorry. -- dep The shortest distance between you and playing great acoustic guitar: the great new instructional DVDs from Marjorie Thompson, available at www.MarjorieThompson.com

11 years, 3 months

TDE on freshly installed Debian 7.3.0 issue...

by sp2lob

Hello all, I would like to install Trinity Desktop Environment release Wheezy [Debian 7.0] (v3.5.13.2) on freshly installed Debian 7.3.0 (by means of 3 DVD installation discs). Architecture is amd64 with 64GB RAM. Followed verbatim Debian Trinity Repository Installation Instructions. I'm stuck at the very beginning with following error message: root@deb:~# apt-get install desktop-base-trinity kde-trinity Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: kde-trinity : Depends: kde-core-trinity (>= 5:47) but it is not going to be installed E: Unable to correct problems, you have held broken packages. root@deb:~# I found some interesting posts on the list in regards of similar issue: http://trinity-users.pearsoncomputing.net/?0::5093 But, my question is whether it got solved finally? At this stage of system I would not tamper unnecessarily, basically just to avoid new install. Could you please provide some guidance, how to overcome presented issue? Best regards. Tom - sp2lob

11 years, 3 months

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

tde-users December 2013