Version: (using KDE KDE 3.1) Installed from: Debian stable Packages OS: Linux Hello The Debian PPC packages I installed recently were missing the "libx11globalcomm.la" file. I realize this is not a bug in KDE, but in the packaging. The bug I'm reporting is what resulted from this situation: The missing file caused applications like noatun to crash. This caused Knotify to be triggered, but knotify depended on the file, too, so knotify crashed recursively. Left unattended, this eventually disabled our computer due all the memory being filled with knotify processes. Then a system reboot was necessary. (We started booting KDE and then went to make dinner...) It seems like a bug in KDE that knotify calls itself when it crashes, because this can happen recursively. Either the recursion should be detected and prevented, or crashes of knotify should be handled some other way. It looks like there have been other cases that caused this: http://bugs.kde.org/simple_search.cgi?id=knotify+crash+often Since this still happening, I assume those other bugs were resolved by fixing whatever caused knotify to crash in the first place, not by solving the problem of it crashing recursively in a general way. To reproduce: move aside libx11globalcomm.la, or another file that knotify needs, then run knotify.
*** Bug 53858 has been marked as a duplicate of this bug. ***
Subject: kdelibs/arts/knotify CVS commit by pfeiffer: - try to detect crashes and offer to disable arts output in that case prevents infinite knotify spawning and crash handlers CCMAIL: 53857-close@bugs.kde.org M +87 -7 knotify.cpp 1.69 M +1 -3 knotify.h 1.22
Subject: Please confirm your message re: knotify shouldn't handle it's own crashes to prevent recursion This is an automatically generated response to your message. I'm trying to reduce the amount of junk mail (spam) that Mark is receiving. Your message attached below is being held because the address <bugzilla@ktown.kde.org> has not been verified. To release your original message for delivery, simply reply to this message (no need to type anything else), or just send an empty message to the following address: mark-tmda-confirm-1044155909.56135.de8487@summersault.com This confirmation verifies that your message is legitimate and not junk mail. You should only have to confirm your address once, but I do apologize for any convenience. (If you're interested to learn how this spam prevention system works, or how to reduce your own incoming junk mail, Summersault can help! See http://www.summersault.com/services/email.html ) ------- You are receiving this mail because: ------- You reported the bug, or are watching the reporter. You are a voter for the bug, or are watching someone who is. http://bugs.kde.org/show_bug.cgi?id=53857 carpdjih@mailbox.tu-berlin.de changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution| |FIXED ------- Additional Comments From carpdjih@mailbox.tu-berlin.de 2003-02-02 04:18 ------- Subject: kdelibs/arts/knotify CVS commit by pfeiffer: - try to detect crashes and offer to disable arts output in that case prevents infinite knotify spawning and crash handlers CCMAIL: 53857-close@bugs.kde.org M +87 -7 knotify.cpp 1.69 M +1 -3 knotify.h 1.22
Created attachment 25099 [details] backtrace of knotify crash for bug 53587
This just happened to me...I'm not sure what caused the initial crash, but restarting the computer did not help with the recursive popups. Had to create a new user profile. Attached the bactrace.