| Summary: | Amarok crashes on startup. | ||
|---|---|---|---|
| Product: | [Applications] amarok | Reporter: | Ryan J Redding <rinkydinksrj> |
| Component: | general | Assignee: | Amarok Bugs <amarok-bugs-null> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | crash | ||
| Priority: | NOR | ||
| Version First Reported In: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Gentoo Packages | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
Ryan J Redding
2009-05-05 05:59:53 UTC
Crash happens -every- time I try to start amarok. URL: svn://anonsvn.kde.org/home/kde/trunk/extragear/multimedia/amarok Repository Root: svn://anonsvn.kde.org/home/kde Repository UUID: 283d02a7-25f6-0310-bc7c-ecb5cbfe19da Revision: 963610 Node Kind: directory Schedule: normal Last Changed Author: nhnielsen Last Changed Rev: 963585 Last Changed Date: 2009-05-04 17:34:40 -0500 (Mon, 04 May 2009) Running it from the command line: rjames@rjames-gentoo ~/Documents $ dbus-launch amarok amarok(17255) Phonon::KdePlatformPlugin::createBackend: using backend: "Xine" InnoDB: The log sequence number in ibdata files does not match InnoDB: the log sequence number in the ib_logfiles! 090504 22:52:04 InnoDB: Database was not shut down normally! InnoDB: Starting crash recovery. InnoDB: Reading tablespace information from the .ibd files... InnoDB: Restoring possible half-written data pages from the doublewrite InnoDB: buffer... <unknown program name>(17250)/: Communication problem with "amarok" , it probably crashed. Error message was: "org.freedesktop.DBus.Error.NoReply" : " "Message did not receivea reply (timeout by message bus)" " rjames@rjames-gentoo ~/Documents $ KCrash: Application 'amarok' crashing... sock_file=/home/rjames/.kde4.2/socket-rjames-gentoo/kdeinit4__0 Meh. Totally stupid on my part. Corrupted collection db. -Duh-. Maybe amarok should handle this gracefully though? Removing collection and rescanning seems to fix. Lost all my ratings/playlists but oh well. As far as I'm concerned this can be closed. This is due to the mysql upgrade in the gentoo tree. Downgrade it and it'll work fine. More info: http://mail.kde.org/pipermail/amarok/2009-April/008315.html *** This bug has been marked as a duplicate of bug 190184 *** |