tde-devels May 2013

devels@trinitydesktop.org

10 participants
54 discussions

Re: [trinity-devel] Tim: Unable to build a simple Qt3 test.

by Darrell Anderson

>I updated my GIT repo this morning. After building tqt3, I receive > >the following build failure when trying to build tqtinterface. I >noticed the failure last night when I tried to rebuild tqt3 and >tdeutils. I then saw the same failure trying to build tdeutils. >Something changed when the 1508 patches were merged to GIT, but I >don't know what. > >-- Checking for Qt3... >-- QT_PREFIX_DIR is set to QTDIR >-- QT_PREFIX_DIR : /opt/trinity >-- QT_INCLUDE_DIR: /opt/trinity/include >-- Native TQt3 detected >-- QT_LIBRARY_DIR: /opt/trinity/lib >-- QT_BINARY_DIR : /opt/trinity/bin >-- MOC_EXECUTABLE: /opt/trinity/bin/tqmoc (using Qt 3.5.0) >-- UIC_EXECUTABLE: /opt/trinity/bin/tquic >-- Performing Test HAVE_USABLE_QT3 >-- Performing Test HAVE_USABLE_QT3 - Failed >-- Looking for native TQt3... >-- Performing Test HAVE_USABLE_QT3 >-- Performing Test HAVE_USABLE_QT3 - Failed >CMake Error at cmake/modules/TDEMacros.cmake:23 (message): > ################################################# > > Unable to build a simple Qt3 test. > > ################################################# >Call Stack (most recent call first): > ConfigureChecks.cmake:194 (tde_message_fatal) > CMakeLists.txt:29 (include) > > >-- Configuring incomplete, errors occurred! Update: Reversing commit 9a4765a6 and rebuilding tqt3 avoids the build error with tqtinterface. I'll guess that something in the automated qt3-tqt3 update did not convert correctly? Darrell

10 years, 11 months

Tim: Unable to build a simple Qt3 test.

by Darrell Anderson

Tim, I updated my GIT repo this morning. After building tqt3, I receive the following build failure when trying to build tqtinterface. I noticed the failure last night when I tried to rebuild tqt3 and tdeutils. I then saw the same failure trying to build tdeutils. Something changed when the 1508 patches were merged to GIT, but I don't know what. -- Checking for Qt3... -- QT_PREFIX_DIR is set to QTDIR -- QT_PREFIX_DIR : /opt/trinity -- QT_INCLUDE_DIR: /opt/trinity/include -- Native TQt3 detected -- QT_LIBRARY_DIR: /opt/trinity/lib -- QT_BINARY_DIR : /opt/trinity/bin -- MOC_EXECUTABLE: /opt/trinity/bin/tqmoc (using Qt 3.5.0) -- UIC_EXECUTABLE: /opt/trinity/bin/tquic -- Performing Test HAVE_USABLE_QT3 -- Performing Test HAVE_USABLE_QT3 - Failed -- Looking for native TQt3... -- Performing Test HAVE_USABLE_QT3 -- Performing Test HAVE_USABLE_QT3 - Failed CMake Error at cmake/modules/TDEMacros.cmake:23 (message): ################################################# Unable to build a simple Qt3 test. ################################################# Call Stack (most recent call first): ConfigureChecks.cmake:194 (tde_message_fatal) CMakeLists.txt:29 (include) -- Configuring incomplete, errors occurred! Darrell

10 years, 11 months

[kinit wrapper] -> [tdeinit wrapper]

by Darrell Anderson

I notice in my xsession-error log a mixture of [tdeinit] and [kinit wrapper] identifiers. To remain consistent, should we change [kinit wrapper] to [tdeinit wrapper]? Darrell

10 years, 11 months

Re: [trinity-devel] kdesktoplockcontrol can never work

by Darrell Anderson

>during the research around kdesktop_lock I found that >kdesktoplockcontrol >(formerly pipe, now socket) can never work. Pipe / socket is >created in >folder /tmp/tdesocket-global, but into this folder can enter and >write >only 'root'. The folder is created with permissions 0644, which is >a bit >unusual for the folders. > >I also noticed (when I was allowed to write to the folder >tdesocket-global >also for others) that kdesktoplockcontrol and >kdesktoplockcontrol_out are >created but never removed. > >Please can anyone confirm my findings? >How kdesktoplockcontrol was intended? >Currently obviously can never work. I'm using pre R14 from GIT. I start X from the command line with startx and not in graphical mode with TDM. Therefore during a normal user session, /tmp/tdesocket-global does not exist because I am not using TDM. When I lock the screen I see the following created: $TMP/tde-$USER/kdesktop_lock_lockfile /tmp/tdesocket-global I do not see any files named kdesktoplockcontrol or kdesktoplockcontrol_out. There are no files in /tmp/tdesocket-global. /tmp/tdesocket-global is created with 0644 $USER:$USER permissions yet through konqueror and the command line I cannot access the directory. From my perspective, the /tmp/tdesocket-global directory should never be created when a user locks the screen, which is a user- based action, not global. Second, seems to me whenever /tmp/tdesocket-global is created the ownership should always be root:root, not $USER:$USER. Third, permissions should be 0755, not 0644. I remember raising the topic of housekeeping a long time ago. When I experiment with TDM to help with nominal testing, I notice that /tmp/tdesocket-global remains across a reboot, as does files in that directory. Darrell

10 years, 11 months

Error when deconnecting

by Jean Milot

Hi, I have this error ksmserver when i deconnect. [Thread debugging using libthread_db enabled] [KCrash handler] #5 0x00007fa6b283ba30 in IceProtocolShutdown () from /usr/lib/libICE.so.6 #6 0x00007fa6b2624756 in SmsCleanUp () from /usr/lib/libSM.so.6 #7 0x00007fa6aefd725b in KSMCloseConnectionProc(_SmsConn*, void*, int, char**) () from /opt/trinity/lib/libkdeinit_ksmserver.so #8 0x00007fa6b2626515 in _SmsProcessMessage () from /usr/lib/libSM.so.6 #9 0x00007fa6b283a9d4 in IceProcessMessages () from /usr/lib/libICE.so.6 #10 0x00007fa6aefd6dd2 in KSMServer::processData(int) () from /opt/trinity/lib/libkdeinit_ksmserver.so #11 0x00007fa6aefd86e5 in KSMServer::qt_invoke(int, QUObject*) () from /opt/trinity/lib/libkdeinit_ksmserver.so #12 0x00007fa6b3b4d564 in QObject::activate_signal(QConnectionList*, QUObject*) () from /usr/lib/libqt-mt.so.3 #13 0x00007fa6b3b4f47a in QObject::activate_signal(int, int) () from /usr/lib/libqt-mt.so.3 #14 0x00007fa6b3b690eb in QSocketNotifier::event(QEvent*) () from /usr/lib/libqt-mt.so.3 #15 0x00007fa6b3aef355 in QApplication::internalNotify(QObject*, QEvent*) () from /usr/lib/libqt-mt.so.3 #16 0x00007fa6b3af012e in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libqt-mt.so.3 #17 0x00007fa6b49dc3af in KApplication::notify(QObject*, QEvent*) () from /opt/trinity/lib/libkdecore.so.4 #18 0x00007fa6b3ae505e in QEventLoop::activateSocketNotifiers() () from /usr/lib/libqt-mt.so.3 #19 0x00007fa6b3aa0d05 in QEventLoop::processEvents(unsigned int) () from /usr/lib/libqt-mt.so.3 #20 0x00007fa6b3b06076 in QEventLoop::processEvents(unsigned int, int) () from /usr/lib/libqt-mt.so.3 #21 0x00007fa6aeff48ef in KSMServer::completeShutdownOrCheckpoint() () from /opt/trinity/lib/libkdeinit_ksmserver.so #22 0x00007fa6aeff61d6 in KSMServer::saveYourselfDone(KSMClient*, bool) () from /opt/trinity/lib/libkdeinit_ksmserver.so #23 0x00007fa6b262643c in _SmsProcessMessage () from /usr/lib/libSM.so.6 #24 0x00007fa6b283a9d4 in IceProcessMessages () from /usr/lib/libICE.so.6 #25 0x00007fa6aefd6dd2 in KSMServer::processData(int) () from /opt/trinity/lib/libkdeinit_ksmserver.so #26 0x00007fa6aefd86e5 in KSMServer::qt_invoke(int, QUObject*) () from /opt/trinity/lib/libkdeinit_ksmserver.so #27 0x00007fa6b3b4d564 in QObject::activate_signal(QConnectionList*, QUObject*) () from /usr/lib/libqt-mt.so.3 #28 0x00007fa6b3b4f47a in QObject::activate_signal(int, int) () from /usr/lib/libqt-mt.so.3 #29 0x00007fa6b3b690eb in QSocketNotifier::event(QEvent*) () from /usr/lib/libqt-mt.so.3 #30 0x00007fa6b3aef355 in QApplication::internalNotify(QObject*, QEvent*) () from /usr/lib/libqt-mt.so.3 #31 0x00007fa6b3af012e in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libqt-mt.so.3 #32 0x00007fa6b49dc3af in KApplication::notify(QObject*, QEvent*) () from /opt/trinity/lib/libkdecore.so.4 #33 0x00007fa6b3ae505e in QEventLoop::activateSocketNotifiers() () from /usr/lib/libqt-mt.so.3 #34 0x00007fa6b3aa0d05 in QEventLoop::processEvents(unsigned int) () from /usr/lib/libqt-mt.so.3 #35 0x00007fa6b3b060e1 in QEventLoop::enterLoop() () from /usr/lib/libqt-mt.so.3 #36 0x00007fa6b3b05f92 in QEventLoop::exec() () from /usr/lib/libqt-mt.so.3 #37 0x00007fa6aefd67a5 in kdemain () from /opt/trinity/lib/libkdeinit_ksmserver.so #38 0x0000000000407bb7 in ?? () #39 0x00000000004088e2 in ?? () #40 0x000000000040903d in ?? () #41 0x000000000040a2a7 in main () Thanks for your help. Sincerely, Jean Milot

10 years, 11 months

Vote for favorite desktop

by Darrell Anderson

I'm not fond of polls but you might want to vote for Trinity: http://www.tuxmachines.org/ Somebody please forward to the user's mail list. :-) Darrell

10 years, 11 months

KDM resolution problem / crash in kcm displaymanager

by François Andriot

Hello, in my current 3.5.13.1 installation, I still have trouble setting the correct screen resolution for TDM. When going into the "kcmshell displaymanager", I always crash when saving settings, and they are not saved at all. (they are supposed to be in something like /opt/trinity/share/displayconfig/... ) Using GDB I see it SEGV line 115 of the following file: http://git.trinitydesktop.org/cgit/tdelibs/tree/krandr/libkrandr.cc?id=v3.5… I see that a patch to avoid crash was submitted and backported in SRU: http://git.trinitydesktop.org/cgit/tdelibs/tree/krandr/libkrandr.cc?h=origi… Basically, the "delete" is conditional. Good point. But I think the true problem is not to avoid the "delete" function, but to know why we go in there. Looking at this file, line 287: http://git.trinitydesktop.org/cgit/tdebase/tree/kdm/kfrontend/kgapp.cpp?h=o… I see that the "ICC Profile" parameter is set to "" (empty string). Back to the "KRandrSimpleAPI::getIccFileName" in tdelibs, I see that the profileName variable is checked 3 times: |84 if (profileName != NULL) {| |91 if (profileName != NULL) { | |111 if (profileName != "") { |So, if profileName is set to ""|, the 2 first tests are positive, and the third is negative. We create variable|||"t_config" but then delete variable "t_systemconfig". Then it (used to) crash. I think something must be clarified here: if the function is meant to receive "no profile" as paramater, we must choose if this is NULL or or an empty string. Or we can check both value if both must be valid, e.g: || |||if ((profileName != NULL) && (profileName != "")) {| |What do you think ? |

10 years, 11 months

Re: [trinity-devel] Odd cmake files being included in some packages and installed

by Darrell Anderson

>> tdelibs.cmake >> tderesources.cmake >> twin.cmake >> >> The files are installed from the following packages: >> >> tdebase >> tdegraphics >> tdelibs >> tdepim >> tdesdk >> tdeutils >> >> What is causing this? > >These are so called "exported targets" and contains info like >complete path to >shared object and its dependencies. Very nice feature of cmake. > >http://www.cmake.org/Wiki/CMake/Tutorials/Exporting_and_Importing_T >argets What is the value? How do I stop the exporting behavior? Darrell

10 years, 11 months

Odd cmake files being included in some packages and installed

by Darrell Anderson

I noticed the following files being installed in $PREFIX/share/cmake: certmanager.cmake cervisia.cmake indexlib.cmake kgantt.cmake kicker.cmake kmail.cmake knotes.cmake konqueror.cmake korganizer.cmake ktnef.cmake kviewshell.cmake libkcal.cmake libkholidays.cmake libkmime.cmake libkonq.cmake libkpgp.cmake libkpimexchange.cmake libkpimidentities.cmake libkscan.cmake libksieve.cmake libksimcore.cmake libtdenetwork.cmake libtdepim.cmake mimelib.cmake tdelibs.cmake tderesources.cmake twin.cmake The files are installed from the following packages: tdebase tdegraphics tdelibs tdepim tdesdk tdeutils What is causing this? Darrell

10 years, 11 months

Bugzilla maintainers: Nominal bugzilla change

by Darrell Anderson

Bugzilla maintainers: We should update a bugzilla text string label: KDE Version String -> TDE Version String Darrell

10 years, 11 months

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

tde-devels May 2013