Summary: | Amarok 2.1 repeatedly crashes when trying to set Custom album cover | ||
---|---|---|---|
Product: | [Applications] amarok | Reporter: | Balakrishnan Nair <balaknair> |
Component: | general | Assignee: | Amarok Developers <amarok-bugs-dist> |
Status: | RESOLVED DUPLICATE | ||
Severity: | crash | ||
Priority: | NOR | ||
Version: | 2.1.1 | ||
Target Milestone: | --- | ||
Platform: | Unlisted Binaries | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Balakrishnan Nair
2009-07-18 06:07:16 UTC
Sorry, but your backtrace lacks quite some debugging symbols. If you can reproduce this crash, please see here on how to reproduce a valid backtrace: http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports On Ubuntu, you need to install the amarok-dbg files at least. Ideally you should install all debugging packages for the applications you are running. After filing this bug report, I uninstalled Amarok 2 and dependencies(including configuration files), and installed Amarok 1.4(using a Launchpad PPA https://launchpad.net/~bogdanb/+archive/ppa ) since Amarok 2 had become pretty much unusable with the collection full of errors. It would keep updating the collection database and new errors kept popping up. Reinstalling Amarok 2 or manually rescanning the collection didn't seem to make any difference. So I just switched to Amarok 1.4 and rescanned the collection(SQLite). It was only then that I saw Myriam Schweingruber's comment here. So I then uninstalled 1.4 and reinstalled Amarok 2 and the dbg package(~180 MB). The entire collection at ~/Music was rescanned, and library info now shows correctly including album art. The trouble is, I no longer get the crash when assigning custom covers, and can't reproduce the bug. I've tried all the stuff I was doing when the trouble started, but so far Amarok has remained frustratingly stable. Everything seems OK, including the Gnome Multimedia Keys plugin. Since the bug seems to have been marked Resolved (in Amarok 2.2) here https://bugs.kde.org/show_bug.cgi?id=200249 I'm going to hope for the best and stick with things as they are for now and not mess up my current set-up. I'll update this with as much debugging info as possible if this happens again(fingers crossed). Regards to all and many thanks. You are welcome, thanks for your report and feedback. Marking as solved then (duplicate of 200249). Feel free to reopen if you should come across this again once Amarok 2.2. is released. *** This bug has been marked as a duplicate of bug 200249 *** |