Summary: | Amarok crashes on startup | ||
---|---|---|---|
Product: | [Applications] amarok | Reporter: | andy.reddy |
Component: | Collection Browser | Assignee: | Amarok Developers <amarok-bugs-dist> |
Status: | RESOLVED DUPLICATE | ||
Severity: | crash | CC: | ralf-engels, tobyfox |
Priority: | NOR | ||
Version: | 2.4.3 | ||
Target Milestone: | 2.5 | ||
Platform: | openSUSE | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Attachments: | Config file that causes it to crash on startup for me |
Description
andy.reddy
2011-09-18 12:00:05 UTC
Did you try erasing the configuration files and start again? Ral: this looks the same as bug 233170, fixed some versions back. *** Bug 282302 has been marked as a duplicate of this bug. *** Deleting all $HOME/.kde/share/config/amarok* worked - thanks very much! Would be cool to figure out which configuration setting did it, so the bug could be fixed and so that I don't lose all my settings =) If it happens again I'll try to figure out at least which file is responsible. Cheers. Thank you for the feedback. The problem is most likely in the Collection Browser settings. Created attachment 63757 [details]
Config file that causes it to crash on startup for me
I spoke too soon. I backed up my config files before deleting them, and added them back chunk by chunk and then line by line to see which caused the crash. Bizarrely, it is the line "amarok_service_magnatunestoreEnabled=false" under [Plugins] in amarokrc that causes the crash. When I put it in, Amarok crashes on startup, when I delete it, Amarok starts fine. I've attached the config file, with the line in, that causes it to crash. Could you also test if this also happens with the Jamendo service? This would confirm it is the same bug as bug 233170 I'm not sure what you mean by test it with the Jamendo service. The line "amarok_service_magnatunestoreEnabled=false" in amarokrc causes it to crash on startup - the line "amarok_service_jamendoEnabled=false" is in my amarokrc and doesn't cause any problems. I have never, to my knowledge, used either the Magnatune store nor Jamendo - I assume they are only in my config file because I at some point went through the preferences and had a look at the plugins. As would be expected, the line "amarok_service_magnatunestoreEnabled=true" is fine - my Amarok only crashes when the Magnatunes store is explicitly disabled. Enabling Jamendo also does not cause problems. I played around with it a little more, running amarok --debug from a terminal and comparing output with Magnatunes enabled and disabled. I am not at all familiar with Amarok or debugging any KDE software, but if it's of any help, and not completely irrelevant, here is what I found. When the Magnatunes store is disabled and it crashes on startup, it does so after fetching tracks and a CollectionTreeItemModelBase::handleSpecialQueryResult() call. The final lines of the debug output is: [...lots of things I can attach if you're interested] amarok: END__: void Collections::ScriptableServiceQueryMaker::fetchTracks() [Took: 0.012s] amarok: BEGIN: virtual void CollectionTreeItemModelBase::queryDone() amarok: END__: virtual void CollectionTreeItemModelBase::queryDone() [Took: 0s] amarok: BEGIN: virtual void CollectionTreeItemModelBase::queryDone() amarok: END__: virtual void CollectionTreeItemModelBase::queryDone() [Took: 0s] amarok: BEGIN: virtual void CollectionTreeItemModelBase::queryDone() amarok: END__: virtual void CollectionTreeItemModelBase::queryDone() [Took: 0s] amarok: BEGIN: void CollectionTreeItemModelBase::handleSpecialQueryResult(CollectionTreeItem::Type, Collections::QueryMaker*, const Meta::DataList&) amarok: [CollectionTreeItemModelBase] Received special data: 45 amarok: BEGIN: CollectionTreeItem::CollectionTreeItem(CollectionTreeItem::Type, const Meta::DataList&, CollectionTreeItem*, CollectionTreeItemModelBase*) amarok: END__: CollectionTreeItem::CollectionTreeItem(CollectionTreeItem::Type, const Meta::DataList&, CollectionTreeItem*, CollectionTreeItemModelBase*) [Took: 0s] amarok: END__: void CollectionTreeItemModelBase::handleSpecialQueryResult(CollectionTreeItem::Type, Collections::QueryMaker*, const Meta::DataList&) [Took: 0s] QSocketNotifier: Invalid socket 37 and type 'Read', disabling... KCrash: Application 'amarok' crashing... KCrash: Attempting to start /usr/lib/kde4/libexec/drkonqi from kdeinit QSocketNotifier: Invalid socket 52 and type 'Read', disabling... When there is no crash, with Magnatunes enabled, fetching tracks is followed up by some LastFm stuff (and handleSpecialQueryResult() is called much later if at all). With no crash the debug is: [...lots of things I can attach if you're interested] amarok: END__: void Collections::ScriptableServiceQueryMaker::fetchTracks() [Took: 0.012s] amarok: BEGIN: virtual void CollectionTreeItemModelBase::queryDone() amarok: END__: virtual void CollectionTreeItemModelBase::queryDone() [Took: 0s] amarok: BEGIN: virtual void CollectionTreeItemModelBase::queryDone() amarok: END__: virtual void CollectionTreeItemModelBase::queryDone() [Took: 0s] amarok: BEGIN: virtual void CollectionTreeItemModelBase::queryDone() amarok: END__: virtual void CollectionTreeItemModelBase::queryDone() [Took: 0s] "OK 2587ad232fa04a94b36f853df08827c2 http://post.audioscrobbler.com:80/np_1.2 http://post2.audioscrobbler.com:80/protocol_1.2" amarok: BEGIN: void LastFmService::onGetUserInfo() [...and then it carries on with LastFm stuff and continues starting up with another 100 or so lines] Of course, when Magnatune is disabled and it crashes there are no debug messages about Magnatune, and when it is enabled there are plenty. The crashing vs. non-crashing debug output seems consistent over several tries. I've no clue what any of this is, obviously, and kudos to you for working on it, though I must say I'm happy to know that I can just leave Magnatunes enabled and forget about it. Let me know if there's anything else you'd like me to try out or look at. Thank you for the valuable feedback. *** This bug has been marked as a duplicate of bug 233170 *** |