Version: (using KDE KDE 3.4.0) Installed from: SuSE RPMs OS: Linux I noticed I was running out of disk space. I checked and found a 40GB ~/.xsession-errors file. It seems the line QString::arg(): Argument missing: /konqsidebartng/kicker_entries/amarok.desktop, 599999 the last number changes every line. So there is 40GBs of this line repeating. I was playing around with panels and such on the kicker trying to use the top right of my screen. It "crashed" on something. I kept going without it for about 14-18 hours just for fun. During this time I found a kicker process running. So it didn't completely die. I killed it. However the .xsession-error file kept growing.
Assigned to wrong place.. this is most likely a kicker bug, not amaroK.
if kicker was killed, but the .xsession-error file kept growing, then it wasn't kicker. if more information can be provided as to what caused the kicker crash, then i'll be happy to look into this bug. otherwise i'll close it sometime next week as invalid.
Seems like mine problem is the same. I use KDE 3.5 I run out of space too and was very surprised when I found out ~/.xsession-errors has more than 2GB! These are the last lines before starting repeating the last line forever: X Error: BadWindow (invalid Window parameter) 3 Major opcode: 6 Minor opcode: 0 Resource id: 0x1c00019 QApplication::postEvent: Unexpected null receiver kio (KDirWatch): WARNING: KDirWatch::removeDir can't handle 'krusader.desktop' ASSERT: "holders" in kdirlister.cpp (418) fatal error in KDirWatch fatal error in KDirWatch fatal error in KDirWatch fatal error in KDirWatch ps aux showed that kicker stays running after I log out and produces these errors. After I kill the process the .xsession-errors files stops increasing. Seems like it started to occur after I upgraded krusader to 1.70. I have (and had it before too) its launcher icon in kicker. That may have to do someting with it. Next, when I won't kill the kicker process and log into KDE again, kicker crashes, the file stops increasing and the "fatal error in KDirWatch" lines are followed by: kicker: crashHandler called KCrash: Application 'kicker' crashing... ERROR: kicker is already running! Later I can post the backtrace of kicker crash.
yay! two different problems in the same BR, and neither with backtraces. this week has had to have seen the WORST bug reporting i've seen in a while =/ ok... first problem: please post the `kde-config --prefix`/share/apps/konqsidebartng/kicker_entries/amarok.desktop file from your disk as an attachment to this BR. note that i can not reproduce the problem. as for the KDirWatch problem, that's not a kicker problem. that's a problem with KDirWatch. if you want to avoid the log file filling up, turn off debug logging. otherwise, without a backtrace, i can't even start to help you.
No response; closing