Version: 3.5.3 (using KDE 3.5.3, Debian Package 4:3.5.3-1 (testing/unstable)) Compiler: Target: i486-linux-gnu OS: Linux (i686) release 2.6.17-ck1-p4s I pressed the right mouse button and then I had then attached crash backtrace.
Created attachment 16910 [details] backtrace of the crash.
From the backtrace you have a source build, right? Did you apply any patches at all?
*** Bug 118531 has been marked as a duplicate of this bug. ***
*** Bug 123789 has been marked as a duplicate of this bug. ***
*** Bug 127715 has been marked as a duplicate of this bug. ***
*** Bug 128175 has been marked as a duplicate of this bug. ***
*** Bug 128571 has been marked as a duplicate of this bug. ***
I'm using debian build packages + debian debug packages: kdelibs-data, kdelibs-dbg, kdelibs4c2a, kdelibs4-dev, kdebase-dbg, qt-x11-free-dbg, kde-i18n-es. One question: Have you change the title?, if so why doesn't if appear in any comment. If you need further information, don't hesitate to ask. Thank you.
Yes, I changed the title, but it shows up in "view bug activity", and not as a comment. Bugzilla is funny like that. Anyway, I have -tons- of questions; basically I would like to try to reproduce this... First of all, it would be nice if you started konqueror from a shell/command-line and told me what it outputs before crashing. I am also interested in seeing what your knotify.desktop file looks like --- it should be either in your KDE install directory (somewhere under /usr for debian), or perhaps in ~/.kde...
Created attachment 16940 [details] My knotify.desktop file. Unfortunately this has been a random and unique crash, so I'll be difficult to reproduce the crash. Anyway, I attach the knotify.desktop file which I've found under /usr/share/services in debian. Please let me know of any test/info I can provide.
I have had the same crash again. I did the following IIRC: (I had kontact already opened) 1)Preview a calendar file inside konqueror. 2)Press third mouse button so the file open in a new instance of korganizer. This will bring kontact to foreground with the korganizer part. 3)Close totally kontact 4)Do right click into konqueror on that file. After this I got a crash, but I couldn't repeat this. In general, seems the crash is related to korganizer and right clicking on the file into konqueror. As long as I'm unable to repeat the crash I couldn't get the konsole output for konqueror. Let me know if you need further info.
I had one more crash. Definately on right click. Maybe kdesvn package has anything to do here since I have had some DCOP error messages from it.
*** Bug 131214 has been marked as a duplicate of this bug. ***
*** Bug 133536 has been marked as a duplicate of this bug. ***
*** Bug 136874 has been marked as a duplicate of this bug. ***
Though I have no proof, but I think the bug is surely a consequence of DCOP connection "pollution" effect I described in bug#122020 However, this bug might not be that particular case with X-KDE-GetActionMenu, but another place in the code where DCOP call with timeout is being used (DANGEROUS!). I suggest tracking and fixing those error-prone pieces of code. Raúl: If you're using debian unstable (or etch), please tell us if you've ever experienced this bug after "3 Nov 2006" (unstable) or "10 Nov 2006" (etch) 4:3.5.5a.dfsg.1-3 release of kdelibs.
Thanks for the comments, Modestas. I've not reviewed that action so recently, but I hadn't noticed that doing anything else. Anyway I'll pay special attention and try to repeat the bug. I'll keep you informed.
*** Bug 140900 has been marked as a duplicate of this bug. ***
*** Bug 141959 has been marked as a duplicate of this bug. ***
If there is anything I can do to help kill this bug, I'd like to help. It is quite a nuisance for me, since in my experience, Konqueror, one of my favorite KDE applications, crashes about once or twice a day. Generally it's on right clicks it seems, so it might always be this one bug.
*** Bug 142405 has been marked as a duplicate of this bug. ***
Uhm, does anyone know if this still happens in KDE 4.x?
It can't happen in 4.x. It was a bug in DCOP.