| Summary: | Amarok segfaults on exit | ||
|---|---|---|---|
| Product: | [Applications] amarok | Reporter: | Vit Pelcak <vit> |
| Component: | general | Assignee: | Amarok Developers <amarok-bugs-dist> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | crash | CC: | cfeck, santiag77e |
| Priority: | NOR | ||
| Version: | 2.4.90 (2.5 beta) | ||
| Target Milestone: | 2.6 | ||
| Platform: | openSUSE | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: | New crash information added by DrKonqi | ||
|
Description
Vit Pelcak
2011-12-07 08:59:03 UTC
I can't reproduce this here with current git. Was this a one-time crash or is it reproducible? Just onetime crash. Doesn't backtrace provide enough info to find problem? drkonqui suggested, that this backtrace is useful. (In reply to comment #2) > Just onetime crash. > > Doesn't backtrace provide enough info to find problem? drkonqui suggested, that > this backtrace is useful. Well, a crash needs to be reproducible else there is not really much that we can do. The crash happens in ScannerJob::run(), so it probably was still scanning... Hm. Could be. Whenever I start Amarok, I get error: GREPME MySQLe query failed! (2000) on init. Vit, please check your database, the error you see on start can indicate a table corruption which Amarok can't repair. See also http://amarok.kde.org/wiki/MySQL_Server#Repair_a_Corrupted_Database If that doesn't help I strongly suggest you run the amarokcollectionscanner to see if other errors occur. I didn't use external MySQL database at all. After downgrading back to 2.4.3 problem disappeared. To repair a corrupt database the command is the same for the external as for the internal MySQL. You should run the amarokcollectionscanner nonetheless just to make sure there is not a database problem. Well, but that command fails since I don't know mysql password since I didn't set any. I ran amarokcollectionscanner and donwgraded amarok to 2.4.3. No problems ever since. thank you for your suggestions. FWIW: if you didn't set a MySQL password then there is none Hm. Then that error message: GREPME MySQLe query failed! (2000) on init. is kinda pointless. Created attachment 71434 [details]
New crash information added by DrKonqi
amarok (2.4.3) on KDE Platform 4.7.2 (4.7.2) "release 5" using Qt 4.7.4
- What I was doing when the application crashed:
I was exiting Amarok as I found that reloading of my collection was not advancing.
-- Backtrace (Reduced):
#6 QXmlStreamReader::atEnd (this=0x1ba6c90) at xml/qxmlstream.cpp:570
[...]
#8 0x00007f3a70ef9d31 in ThreadWeaver::JobRunHelper::runTheJob (this=0x7f3a4176ddc0, th=0xfbf510, job=0x1ba6c20) at /usr/src/debug/kdelibs-4.7.2/threadweaver/Weaver/Job.cpp:106
#9 0x00007f3a70ef9e5c in ThreadWeaver::Job::execute (this=0x1ba6c20, th=0xfbf510) at /usr/src/debug/kdelibs-4.7.2/threadweaver/Weaver/Job.cpp:135
#10 0x00007f3a70ef953f in ThreadWeaver::ThreadRunHelper::run (this=0x7f3a4176de40, parent=0xcbb3e0, th=0xfbf510) at /usr/src/debug/kdelibs-4.7.2/threadweaver/Weaver/Thread.cpp:95
#11 0x00007f3a70ef95fb in ThreadWeaver::Thread::run (this=0xfbf510) at /usr/src/debug/kdelibs-4.7.2/threadweaver/Weaver/Thread.cpp:142
(In reply to comment #11) > Hm. > > Then that error message: > GREPME MySQLe query failed! (2000) on init. Please have a look at this downstream bug: https://bugzilla.novell.com/show_bug.cgi?id=712749 *** This bug has been marked as a duplicate of bug 260987 *** |