| Summary: | Amarok crashing on start after updating to Cauldron | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Nikita Krupenko <krnekit> |
| Component: | RPM Packages | Assignee: | Juan Luis Baptiste <juan.baptiste> |
| Status: | RESOLVED DUPLICATE | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | curtis_mageia, fundawang, n9nu, sebastien.guerin.news |
| Version: | Cauldron | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| URL: | https://bugs.kde.org/show_bug.cgi?id=306520 | ||
| Whiteboard: | |||
| Source RPM: | amarok | CVE: | |
| Status comment: | |||
|
Description
Nikita Krupenko
2012-09-12 20:36:45 CEST
Manuel Hiebel
2012-09-16 11:55:30 CEST
Assignee:
bugsquad =>
juan.baptiste I'm having the same problem even after removing ~/.kde4/share/apps/amarok In my case, I've been keeping up with Cauldron daily. Console output: amarok: BEGIN: void MountPointManager::loadDevicePlugins(const QList<Plugins::PluginFactory*>&) amarok: [MountPointManager] initializing: "amarok_device_massstorage" amarok: BEGIN: void MountPointManager::createHandlerFromDevice(const Solid::Device&, const QString&) amarok: [MountPointManager] Device added and mounted, checking handlers amarok: BEGIN: virtual bool MassStorageDeviceHandlerFactory::canHandle(const Solid::Device&) const amarok: END__: virtual bool MassStorageDeviceHandlerFactory::canHandle(const Solid::Device&) const [Took: 0s] amarok: [MountPointManager] found handler for "/org/freedesktop/UDisks/devices/sdc2" amarok: BEGIN: virtual DeviceHandler* MassStorageDeviceHandlerFactory::createHandler(const Solid::Device&, const QString&, SqlStorage*) const amarok: [MassStorageDeviceHandler] Found existing UUID config for ID "1" , uuid "7e9765ba-b218-4727-8217-30cea29f6904" KCrash: Application 'amarok' crashing... KCrash: Attempting to start /usr/lib64/kde4/libexec/drkonqi from kdeinit sock_file=/home/curtis/.kde4/socket-Parkes/kdeinit4__0 unnamed app(23289): Communication problem with "amarok" , it probably crashed. Error message was: "org.freedesktop.DBus.Error.NoReply" : " "Message did not receive a reply (timeout by message bus)" " Backtrace with amarok-debug package: #20 0x00007f1e21b999fb in ~Stream (this=0x20e0570, __in_chrg=<optimized out>) at /usr/include/QtCore/qdebug.h:64 #21 ~QDebug (this=<optimized out>, __in_chrg=<optimized out>) at /usr/include/QtCore/qdebug.h:88 #22 MassStorageDeviceHandlerFactory::createHandler (this=<optimized out>, device=..., udi=..., s=0x1714680) at /usr/src/debug/amarok-2.6.0/src/core-impl/collections/db/sql/device/massstorage/MassStorageDeviceHandler.cpp:172 #23 0x00007f1e612ddf52 in MountPointManager::createHandlerFromDevice (this=this@entry=0x1cc8f80, device=..., udi=...) at /usr/src/debug/amarok-2.6.0/src/MountPointManager.cpp:503 #24 0x00007f1e612e0ae8 in MountPointManager::loadDevicePlugins (this=0x1cc8f80, factories=...) at /usr/src/debug/amarok-2.6.0/src/MountPointManager.cpp:124 #25 0x00007f1e612e6b84 in Plugins::PluginManager::init (this=this@entry=0x1b4ad60) at /usr/src/debug/amarok-2.6.0/src/PluginManager.cpp:104 #26 0x00007f1e612e7904 in Plugins::PluginManager::PluginManager (this=0x1b4ad60, parent=<optimized out>) at /usr/src/debug/amarok-2.6.0/src/PluginManager.cpp:65 #27 0x00007f1e612e7ab7 in Plugins::PluginManager::instance () at /usr/src/debug/amarok-2.6.0/src/PluginManager.cpp:44 #28 0x00007f1e612c7d8e in pluginManager () at /usr/src/debug/amarok-2.6.0/src/PluginManager.h:76 #29 MainWindow::MainWindow (this=0x1b49d20) at /usr/src/debug/amarok-2.6.0/src/MainWindow.cpp:140 #30 0x00007f1e612a2db8 in App::continueInit (this=this@entry=0x7fff6ddbf680) at /usr/src/debug/amarok-2.6.0/src/App.cpp:545 #31 0x00007f1e612a4527 in App::App (this=0x7fff6ddbf680) at /usr/src/debug/amarok-2.6.0/src/App.cpp:184 #32 0x0000000000408c30 in main (argc=2, argv=0x7fff6ddbf7e8) at /usr/src/debug/amarok-2.6.0/src/main.cpp:304 CC:
(none) =>
curtis_mageia
Sébastien GUERIN
2012-09-23 17:49:56 CEST
CC:
(none) =>
sebastien.guerin.news If I delete my amarok app folder in .kde4/share/apps, amarok will start normally. No folder rescan is performed. When I quit, it crashes. Starting it again produces the same crash as above. Should I file a new bug for the crash on a fresh config folder?
Sébastien GUERIN
2012-09-29 20:43:06 CEST
Hardware:
i586 =>
All |