Bug 241921

Summary:	Amarok will not start on KDE 4.5b2
Product:	[Applications] amarok	Reporter:	Tom Brommage <brommage>
Component:	general	Assignee:	Amarok Bugs <amarok-bugs-null>
Status:	RESOLVED NOT A BUG
Severity:	crash	CC:	kfunk
Priority:	NOR
Version First Reported In:	2.3.1
Target Milestone:	---
Platform:	Ubuntu
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Tom Brommage 2010-06-16 16:29:36 UTC

Version:           2.3.1 (using Devel) 
OS:                Linux

Several attempts to start Amarok, all unsuccessful since upgrade to 4.5b2.





Reproducible: Didn't try

Steps to Reproduce:
Start Amarok.

Actual Results:  
tom@tom-desktop:~$ amarok --debug
QStringList Solid::Backends::KUPnP::KUPnPManager::findDeviceByDeviceInterface(Solid::DeviceInterface::Type)  error:  "org.freedesktop.DBus.Error.ServiceUnknown" 

QStringList Solid::Backends::KUPnP::KUPnPManager::findDeviceByDeviceInterface(Solid::DeviceInterface::Type)  error:  "org.freedesktop.DBus.Error.ServiceUnknown" 

QStringList Solid::Backends::KUPnP::KUPnPManager::findDeviceByDeviceInterface(Solid::DeviceInterface::Type)  error:  "org.freedesktop.DBus.Error.ServiceUnknown" 

virtual QStringList Solid::Backends::KUPnP::KUPnPManager::allDevices()  error:  "org.freedesktop.DBus.Error.ServiceUnknown" 

QStringList Solid::Backends::KUPnP::KUPnPManager::findDeviceByDeviceInterface(Solid::DeviceInterface::Type)  error:  "org.freedesktop.DBus.Error.ServiceUnknown" 

QStringList Solid::Backends::KUPnP::KUPnPManager::findDeviceByDeviceInterface(Solid::DeviceInterface::Type)  error:  "org.freedesktop.DBus.Error.ServiceUnknown" 

QStringList Solid::Backends::KUPnP::KUPnPManager::findDeviceByDeviceInterface(Solid::DeviceInterface::Type)  error:  "org.freedesktop.DBus.Error.ServiceUnknown" 

virtual QStringList Solid::Backends::KUPnP::KUPnPManager::allDevices()  error:  "org.freedesktop.DBus.Error.ServiceUnknown" 

QStringList Solid::Backends::KUPnP::KUPnPManager::findDeviceByDeviceInterface(Solid::DeviceInterface::Type)  error:  "org.freedesktop.DBus.Error.ServiceUnknown" 

QStringList Solid::Backends::KUPnP::KUPnPManager::findDeviceByDeviceInterface(Solid::DeviceInterface::Type)  error:  "org.freedesktop.DBus.Error.ServiceUnknown" 

QStringList Solid::Backends::KUPnP::KUPnPManager::findDeviceByDeviceInterface(Solid::DeviceInterface::Type)  error:  "org.freedesktop.DBus.Error.ServiceUnknown" 

virtual QStringList Solid::Backends::KUPnP::KUPnPManager::allDevices()  error:  "org.freedesktop.DBus.Error.ServiceUnknown" 

Calling appendChild() on a null node does nothing.
amarok(1809)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig:
amarok(1809)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig:
amarok(1809)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig:
QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: No such file or directory
QFileSystemWatcher: failed to add paths: /home/tom/.config/ibus/bus
Bus::open: Can not get ibus-daemon's address. 
IBusInputContext::createInputContext: no connection to ibus-daemon 
QGraphicsLinearLayout::removeAt: invalid index 1
amarok(1809)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig:
<unknown program name>(1808)/: Communication problem with  "amarok" , it probably crashed. 
Error message was:  "org.freedesktop.DBus.Error.NoReply" : " "Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken." "

Comment 1 Tom Brommage 2010-06-16 22:44:12 UTC

*** Bug 241920 has been marked as a duplicate of this bug. ***

Comment 2 Tom Brommage 2010-06-16 22:47:11 UTC

*** Bug 241919 has been marked as a duplicate of this bug. ***

Comment 3 Tom Brommage 2010-06-16 22:51:24 UTC

Workaround: Deleting the entire folder $HOME/.kde/share/apps/amarok will allow Amarok to start.

Comment 4 Kevin Funk 2010-07-08 16:06:46 UTC

Looks more like a zombie Amarok process didnt let you restart the application. Closing as invalid (did not have problems after upgrading KDE either).