Bug 247475 - Muon Crashes when searching on a package and clicking on it
Summary: Muon Crashes when searching on a package and clicking on it
Status: RESOLVED DUPLICATE of bug 247439
Alias: None
Product: muon
Classification: Applications
Component: libqapt (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR crash
Target Milestone: ---
Assignee: Jonathan Thomas
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-08-12 09:44 UTC by Miquel Torres
Modified: 2010-08-30 09:11 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
console output with crashing muon (999 bytes, text/plain)
2010-08-12 20:11 UTC, Dirk Sarpe
Details
backtrace from muon crash (2.70 KB, text/plain)
2010-08-12 20:13 UTC, Dirk Sarpe
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Miquel Torres 2010-08-12 09:44:18 UTC
Application: muon (1.0)
KDE Platform Version: 4.4.2 (KDE 4.4.2)
Qt Version: 4.6.2
Operating System: Linux 2.6.32-24-generic x86_64
Distribution: Ubuntu 10.04.1 LTS

-- Information about the crash:
Steps to reproduce:
- in the search box, type "firefox"
- Click on the first item on the package list (which should be "Firefox")
- Muon crashes


 -- Backtrace:
Application: Muon Package Manager (muon), signal: Aborted
[Current thread is 1 (Thread 0x7f99174fc760 (LWP 2807))]

Thread 2 (Thread 0x7f99040da710 (LWP 2808)):
#0  0x00007f991324ff83 in *__GI___poll (fds=<value optimized out>, nfds=<value optimized out>, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:87
#1  0x00007f99104484a9 in ?? () from /lib/libglib-2.0.so.0
#2  0x00007f99104488fc in g_main_context_iteration () from /lib/libglib-2.0.so.0
#3  0x00007f9915268566 in QEventDispatcherGlib::processEvents (this=0x2b32350, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:414
#4  0x00007f991523d992 in QEventLoop::processEvents (this=<value optimized out>, flags=) at kernel/qeventloop.cpp:149
#5  0x00007f991523dd6c in QEventLoop::exec (this=0x7f99040d9db0, flags=) at kernel/qeventloop.cpp:201
#6  0x00007f9915147d59 in QThread::exec (this=<value optimized out>) at thread/qthread.cpp:487
#7  0x00007f991521e178 in QInotifyFileSystemWatcherEngine::run (this=0x2b66de0) at io/qfilesystemwatcher_inotify.cpp:248
#8  0x00007f991514a775 in QThreadPrivate::start (arg=0x2b66de0) at thread/qthread_unix.cpp:248
#9  0x00007f9914eba9ca in start_thread (arg=<value optimized out>) at pthread_create.c:300
#10 0x00007f991325c6fd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#11 0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7f99174fc760 (LWP 2807)):
[KCrash Handler]
#5  0x00007f99131a9a75 in *__GI_raise (sig=<value optimized out>) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
#6  0x00007f99131ad5c0 in *__GI_abort () at abort.c:92
#7  0x00007f9913a5f8e5 in __gnu_cxx::__verbose_terminate_handler() () from /usr/lib/libstdc++.so.6
#8  0x00007f9913a5dd16 in ?? () from /usr/lib/libstdc++.so.6
#9  0x00007f9913a5dd43 in std::terminate() () from /usr/lib/libstdc++.so.6
#10 0x00007f9913a5ddc6 in __cxa_rethrow () from /usr/lib/libstdc++.so.6
#11 0x00007f991523debd in QEventLoop::exec (this=<value optimized out>, flags=<value optimized out>) at kernel/qeventloop.cpp:214
#12 0x00007f9915241aab in QCoreApplication::exec () at kernel/qcoreapplication.cpp:981
#13 0x000000000041623c in main (argc=<value optimized out>, argv=<value optimized out>) at /build/buildd/muon-1.0/src/main.cpp:54

Possible duplicates by query: bug 247474, bug 247439, bug 247311, bug 247239, bug 247058.

Reported using DrKonqi
Comment 1 Jonathan Thomas 2010-08-12 14:19:09 UTC
Is this crash reproducible? If so, could you install debug symbols via Dr. Konqi's "Install Debug Symbols" button and get a fresh backtrace please? Also, konsole output of when the crash occurs could also be helpful.
Comment 2 Miquel Torres 2010-08-12 15:33:17 UTC
Yes, I happens 100% of the time.
That trace is with the Debug Symbols already installed.

Here the console output:
--------------------------------
Qt has caught an exception thrown from an event handler. Throwing
exceptions from an event handler is not supported in Qt. You must
reimplement QApplication::notify() and catch all exceptions there.

terminate called after throwing an instance of 'std::logic_error'
  what():  basic_string::_S_construct NULL not valid
KCrash: Application 'muon' crashing...
sock_file=/home/miquel/.kde/socket-mede/kdeinit4__0
QSocketNotifier: Invalid socket 35 and type 'Read', disabling...
--------------------------------

Hope that helps
Comment 3 Jonathan Thomas 2010-08-12 15:38:56 UTC
I think that there is a high likelihood of this being bug 247439, though the backtrace doesn't really say where in the LibQApt code this exception comes from. :(

Is there anything special about your Firefox packages? (E.g. from an unusual source or maybe locally installed) Could you post the output of apt-cache show firefox?
Comment 4 Miquel Torres 2010-08-12 17:32:24 UTC
Nope, my firefox packages are the usual, but you are right it is very strange that it only happens with Firefox. It probably is a special case of dpkg returning null vars or something, as in the other bug you reference.

For completeness, after launching muon from the console I get this:
-------------------------------
QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: No such file or directory
QFileSystemWatcher: failed to add paths: /home/miquel/.config/ibus/bus
Bus::open: Can not get ibus-daemon's address. 
IBusInputContext::createInputContext: no connection to ibus-daemon
-------------------------------

That is without crashing and before doing anything at all.
Comment 5 Dirk Sarpe 2010-08-12 20:11:33 UTC
Created attachment 50077 [details]
console output with crashing muon
Comment 6 Dirk Sarpe 2010-08-12 20:13:19 UTC
Created attachment 50078 [details]
backtrace from muon crash

backtrace output from crashing muon
Comment 7 Dirk Sarpe 2010-08-12 20:15:01 UTC
Same here with firefox. Firefox was installed with kubuntus "Firefox 1-click Installer" if I recall correctly. Console output and backtrace are above this post.
Comment 8 Jonathan Thomas 2010-08-27 13:11:37 UTC
Could you try updating to Muon 1.0.1 and see if this is still an issue?
Comment 9 Dirk Sarpe 2010-08-28 10:00:27 UTC
Works for me now. Great!
Comment 10 Jonathan Thomas 2010-08-28 13:44:06 UTC
Cool! It was most likely bug 247439 after all, but I had to be sure. :)

*** This bug has been marked as a duplicate of bug 247439 ***
Comment 11 Miquel Torres 2010-08-30 09:11:50 UTC
yey! fixed with 1.0.1