Version: 1.2 (using KDE 3.3.2, (3.1)) Compiler: gcc version 3.3.5 (Debian 1:3.3.5-8) OS: Linux (i686) release 2.4.25-1-686 v1.2 no longer starts (hidden or otherwise) when logging in with KDE. This is unexpected for an application that uses the system tray.
WORKSFORME, but other people have reported this too. I don't understand it yet.
OK. Where do I start looking for what's different on Debian unstable compared to your setup? For reference, I'm running Klipper, KwikDisk, KsCD, KGpg, KDE Wallet and KMail in the system tray. It did use to work with all of those but maybe now there's an overload issue? If you use the same list, does Amarok still start up at login? I spend most of my time in Gnome development, rather than KDE, so what should I be looking for to put some light on why KDE starts amarok for some people and not others?
I can't really say. Maybe check your ~/.xsession logs for some amaroK output from the amarok binary. Thanks.
I get no output into ~/.xsession-errors from amarok. Amarok is being saved by KDE session, I get this in ~/.kde/share/config/ksmserverrc clientId7=10d0c6deca000111092361800000161280010 count=7 discardCommand7= program7=amarokapp restartCommand7=amarokapp,-session,10d0c6deca000111092361800000161280010_1110923710_970 restartStyleHint7=0 userId7=neil That restartCommand7 is key. I logged out, switched to a console login, edited ~/.kde/share/config/ksmserverrc to change restartCommand7=amarokapp to restartCommand7=amarok (leaving the ,-session... intact) and amarok restarted as it used to when I logged in using the GUI. So, to me, it would appear that amarok is reporting itself to ksmserver as amarokapp instead of amarok. Thereby causing ksmserver to try to restart amarokapp which doesn't exist. Does that help?
I had this problem too with Debian unstable's 1.2.1-1 package. s/amarokapp/amarok/ in ksmserverrc fixed it for me. Thanks for the tip Neil. Now I know how KDE session management works. [sorry for duplicate email; I now see I need to have an account on bugs.kde.org and that whether you guys get CCed is up to you, not me] Thanks, Brian
this problem stays in 1.2.3-1 (deb too)
*** This bug has been confirmed by popular vote. ***
Neil wrote: "So, to me, it would appear that amarok is reporting itself to ksmserver as amarokapp instead of amarok. Thereby causing ksmserver to try to restart amarokapp which doesn't exist." Why does amarokapp not exist? It must exist, for amarokapp is the actual amaroK binary.
Debian patches amaroK to install amarokapp in /usr/lib/amarok/amarokapp (instead of /usr/bin/amarokapp), so the session manager doesn't find it when it restores the session.
So, can we close this? I guess this should go into the debian bug database.
Okay, I will close this. The Debian bug report is here: bughttp://bugs.debian.org/cgi-bin/bugreport.cgi?bug=302852
Sorry, something got wrong with the link, here it is again: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=302852
* Stefan Siegel [Sun, 03 Apr 2005 13:34:52 +0200]: > Debian patches amaroK to install amarokapp > in /usr/lib/amarok/amarokapp (instead of /usr/bin/amarokapp), so the > session manager doesn't find it when it restores the session. Uhm, thanks for the heads up. I had noticed it and was buggering me. ;-) For the record, this was working fine (afaict) until this commit: amarok/src/amarokcore/main.cpp - revision 1.47 date: 2005/01/27 00:51:42; author: mhowell; state: Exp; lines: +2 -2 * We no longer adjust argv[0] from amarokapp to amarok as this was what was breaking DrKonqi (at least for me). I don't know if this regresses anything else, but if it does we need to think about this. So the fix would be trivial, but DrKonqi has issues with it. Oh well.