Summary: | Crash in DaapCollection on startup | ||
---|---|---|---|
Product: | [Applications] amarok | Reporter: | Myriam Schweingruber <myriam> |
Component: | Collections/DAAP | Assignee: | Amarok Developers <amarok-bugs-dist> |
Status: | RESOLVED FIXED | ||
Severity: | crash | CC: | dima, ian.monroe |
Priority: | HI | ||
Version: | 2.3-GIT | ||
Target Milestone: | --- | ||
Platform: | Unlisted Binaries | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Myriam Schweingruber
2009-10-12 19:57:05 UTC
Ian, could you have a look, please? I can't start Amarok anymore at all... *** Bug 210379 has been marked as a duplicate of this bug. *** I have also seen this crash several times. This bug has been in Amarok since about forever (beginning of 2.0 development or so). Note: I'm not even using DAAP at all. It crashes anyway. I find that very serious. This is what we found out: 09:11 < markey> eean: args, I realized where that DAAP crash might come from. when a plugin couldn't be loaded correctly, PluginManager shows a warning dialog. it should block, but somehow that DAAP collection code gets executed in the meantime 09:11 < markey> KMessageBox::error( 0, i18n( "<p>KLibLoader could not load the plugin:<br/><i>%1</i></p>" 09:11 < markey> "<p>Error message:<br/><i>%2</i></p>", 09:11 < markey> service->library(), 09:11 < markey> loader->lastErrorMessage() ) ); 09:11 < markey> and that == FAIL 09:11 < eean> yea it doesn't block 09:11 < eean> it processevents 09:11 < markey> it's coincidence that it happens with DAAP, it's just because that's the first loaded plugin Ok, I think I've fixed it: commit 65fd8ba50bfc6e797f4c1c243f4ac745a28482ae Author: Mark Kretschmann <kretschmann@kde.org> Date: Wed Oct 14 09:26:54 2009 +0200 Fix stupid random crash with loading DaapCollection. The crash wasn't actually caused by the collection itself, but rather by a warning dialog that PluginManager showed. Thanks to processEvents() greatness, other things ran concurrently while it should have blocked. BUG: 210363 |