I'm seeing these messages in my xsession log. The standard as-is message looks like that in the subject line. My messages now look like this:
[kinit] Could not load library (artswrapper)! Trying exec...
[kinit] Could not load library (/usr/local/bin/run_conky)! Trying exec...
[kinit] Could not load library (/usr/bin/VBoxClient-all)! Trying exec...
I added the [kinit] prefix in a patch I have not yet submitted to clarify the source of the message. I also patched the error string with the %s parameter to identify the object of the message.
The message sort of makes sense. kinit is trying to load/run/launch something that is not a library but is an executable. Browsing the source code (tdelibs/kinit/kinit.cpp) indicates there is a distinction between libraries and executables. Therefore I'm wondering whether the message should be displayed, clutters the xsession log, or should be revised.
As you can see from the as-is format, the message is not informative at all. Worse, the exclamation mark is misleading and needlessly disturbing to anybody reading the log. An exclamation mark should indicate something serious that needs attention but that is not the case here. The message is somewhat informative but is not emergency. If the message is valuable then rewording would help. Possibly something like:
[kinit] artswrapper is an executable and not a library. Launching with exec...
If there are no objections then I'd like to patch that error string as above and push to GIT.
Darrell
I'm seeing this message in my xsession log. The message occurs during the session shutdown.
Watching the log through tail, the message occurs after selecting any logout option. I believe the error is caused by the "Saving your sessions" dialog. I enabled logout confirmation and the error does not appear until after I confirm the logout, which is when the "Saving your sessions" dialog appears.
The message itself is in TQt3 qabstractlayout.cpp:609:
qWarning( "TQLayout \"%s\" added to %s \"%s\", which already has a"
" layout", TQObject::name(), parent->className(),
parent->name() );
Any ideas what to look for in the code and how to resolve?
Darrell
Tim, all,
In the arch qt3 build, there was a sed statement to include qglobal.h in qtimer.h:
# missing include "qglobal.h" in include/qtimer.h fix
sed -ie 's/define QTIMER_H/&\n#include "qglobal.h"/g'
"$pkgdir$_prefix/include/qtimer.h"
Is that needed for ntqtimer.h?
--
David C. Rankin, J.D.,P.E.
Tim,
If you already know this then never mind, but I needed to patch tdelibs and tdebase against today's GIT updates for some remaining tde-config renaming. The patches are here:
http://humanreadable.nfshost.com/trinity/patches/tdebase
Also two additional patches to build tdebase caused by recent tqt changes.
:)
Darrell
Guys, Gals,
When building TQt3 to replace Qt3, what is the name for the recommended
install dir (i.e. $QTDIR)? I am going to put it in /opt, so should it go in:
/opt/TQt3
or should I use it as a direct replacement and put it in
/opt/Qt3?
Specifically, I am attempting this on archlinux where I have only used Qt3
before. Is this advisable, or should I just stay with Qt3?
If I install TQt3, then will updating /etc/profile.d/qt3.sh be the proper
way to tell the rest of the system where to find Qt3 --or-- should I create a
new profile named tqt3.sh with that information??
--
David C. Rankin, J.D.,P.E.
An interesting idea:
https://www.mozilla.org/en-US/collusion/
I bet the Mozilla people do their own tracking too. I wonder whether the add-on will disclose that?
My real concern is whether any Trinity apps perform or allow tracking that users might not be aware or approve.
Amarok? Akregator? Konqueror? KMail? IMs?
The question is not how to block such activities but whether users are fully informed that Trinity apps perform or allow tracking and have options in an apps' configuration to prevent the tracking.
Darrell