On Monday 03 December 2007, Kevin Donnelly wrote: > Sorry, Randall, it does - this has happened on at least two 10.2 machines > of mine, but I haven't tracked down which update was responsible yet. I > have noticed, though, that moving the .kde folder out of the way so that a > new one is created seems to get kicker working normally again. > > To the OP, the easiest way to deal with this (without moving your .kde > folder, which means re-entering all your user data) is to go to > ~/.kde/Autostart, and run: > ln -s /opt/kde3/bin/kicker kicker > That will mean that kicker gets started independently each time the desktop > launches. > > --
This once happened on my opensuse 10.2 machine. It was caused by a .desktop file in the .kde directory; if I remember correctly it was kcmkicker.desktop and contained only 2 lines without an Exec line, which caused kicker not to launch when logging in. I hope this helps. -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
