Version: unspecified OS: Linux Sorry about the scarce info on versions above. Running Kubuntu 11.10 BETA 1 downloaded/installed a few days back (about 2011.09.19?). Reporting bug manually as requested per dialog of Crash Handler itself. Events: Muon Package Manager and Muon Software Center have been working erratically (sometimes installing stuff, sometimes not) and stopped working altogether reporting that access was refused because another package manager was active. To my knowledge I have never started another package manager on this system yet. Did a hard shutdown and restart several times to no avail - same error. To see what happens I tried starting muon with ~$ kdesudo muon This resulted in some complaining in terminal window: - - - - - - arpy@Amilo-Li-1718:~$ kdesudo muon QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: No such file or directory QFileSystemWatcher: failed to add paths: /home/arpy/.config/ibus/bus arpy@Amilo-Li-1718:~$ - - - - - - Nevertheless muon started and displayed full interface. Next try to load stored list of packages to be installed (failed previously, see above). This crashes muon and the Crash Handler pops up (reproduced twice). In an effort to start reporting the trouble experienced with muon I tried to save the backtrace info to a file (floppy disk icon). Now the Crash Handler "refreshes" and reports that it has crashed itself: Executable: drkonqi PID: 5018 Signal: Segmentation fault (11) requesting to report this manually to https://bugs.kde.org/ The backtrace is listed below. It is 0-star. Will try to install extra packages for debugging later (why are these not included in a beta release?) but have little hope since it all starts with an apparently inoperational package system anyway: ---------- Application: The KDE Crash Handler (drkonqi), signal: Segmentation fault [Current thread is 1 (Thread 0xb7763710 (LWP 5018))] Thread 2 (Thread 0xb5324b70 (LWP 5027)): #0 0x02777d10 in clock_gettime () from /lib/i386-linux-gnu/librt.so.1 #1 0x00213775 in ?? () from /usr/lib/i386-linux-gnu/libQtCore.so.4 #2 0x002e64b6 in ?? () from /usr/lib/i386-linux-gnu/libQtCore.so.4 #3 0x002e680a in ?? () from /usr/lib/i386-linux-gnu/libQtCore.so.4 #4 0x002e5053 in ?? () from /usr/lib/i386-linux-gnu/libQtCore.so.4 #5 0x002e50ed in ?? () from /usr/lib/i386-linux-gnu/libQtCore.so.4 #6 0x02bbee4c in g_main_context_prepare () from /lib/i386-linux-gnu/libglib-2.0.so.0 #7 0x02bbfbf7 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 #8 0x02bc01ea in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0 #9 0x002e5b37 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/i386-linux-gnu/libQtCore.so.4 #10 0x002b624d in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/i386-linux-gnu/libQtCore.so.4 #11 0x002b6491 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/i386-linux-gnu/libQtCore.so.4 #12 0x001b989b in QThread::exec() () from /usr/lib/i386-linux-gnu/libQtCore.so.4 #13 0x00296e9d in ?? () from /usr/lib/i386-linux-gnu/libQtCore.so.4 #14 0x001bc743 in ?? () from /usr/lib/i386-linux-gnu/libQtCore.so.4 #15 0x07bb8d31 in start_thread () from /lib/i386-linux-gnu/libpthread.so.0 #16 0x00a2d0ce in clone () from /lib/i386-linux-gnu/libc.so.6 Backtrace stopped: Not enough registers or memory available to unwind further Thread 1 (Thread 0xb7763710 (LWP 5018)): [KCrash Handler] #5 0x00e7aaed in KFileDialog::KFileDialog(KUrl const&, QString const&, QWidget*, QWidget*) () from /usr/lib/libkio.so.5 #6 0x0809179f in _start () -------------------- Reproducible: Always Steps to Reproduce: I suspect this to be installation specific ? Nevertheless: - Open terminal - Type at prompt: kdesudo muon - Wait for muon to open en show interface - Click File - Read Markings - muon crashes - Wait for Crash Handler to open - Click tab "Developer Information" - Click floppy disk icon (safe backtrace to file) - drkonqi crashes - Wait for Crash Handler to open again - Do as requested - manually file bug report Actual Results: Crash Handler Crashes and pops up again reporting this Expected Results: File created with backtrace of previous crash Running Kubuntu 11.10 BETA 1 on Fujitsu-Siemens Amilo Li 1718 Laptop (Intel Core Duo, T2350, 1.5GB RAM) with some of the desktop effects disabled for speed.
Created attachment 69449 [details] error screen
Thanks for the detailed description, but unfortunately the backtrace of drkonqi itself doesn't give much hint. At most it implies some problem within KFileDialog probvided by kdelibs, but I can't reproduce it. Close it for now.