| Summary: | Muon Crashes when searching on a package and clicking on it | ||
|---|---|---|---|
| Product: | [Unmaintained] muon | Reporter: | Miquel Torres <tobami> |
| Component: | libqapt | Assignee: | Jonathan Thomas <echidnaman> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | crash | CC: | dns_hmpf |
| Priority: | NOR | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | unspecified | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: |
console output with crashing muon
backtrace from muon crash |
||
|
Description
Miquel Torres
2010-08-12 09:44:18 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. 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 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? 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. Created attachment 50077 [details]
console output with crashing muon
Created attachment 50078 [details]
backtrace from muon crash
backtrace output from crashing muon
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. Could you try updating to Muon 1.0.1 and see if this is still an issue? Works for me now. Great! 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 *** yey! fixed with 1.0.1 |