Hello all,

I just installed the beta of Kubuntu 10.4 and it upgraded to Amarok 2.4. However, when I try to start Amarok it exits with a segfult and gives this readout:

Code: Select all

myurko@desktop:~$ amarok
Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
amarok(19594)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig:
amarok(19594)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig:
amarok(19594)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig:
Calling appendChild() on a null node does nothing.
QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: No such file or directory
QFileSystemWatcher: failed to add paths: /home/myurko/.config/ibus/bus
Bus::open: Can not get ibus-daemon's address.
IBusInputContext::createInputContext: no connection to ibus-daemon
<unknown program name>(19593)/: Communication problem with  "amarok" , it probably crashed.
Error message was:  "org.freedesktop.DBus.Error.ServiceUnknown" : " "The name org.kde.amarok was not provided by any .service files" "

myurko@desktop:~$ KCrash: Application 'amarok' crashing...
sock_file=/home/myurko/.kde/socket-desktop/kdeinit4__0
QSocketNotifier: Invalid socket 38 and type 'Read', disabling...

Does anyone know what is causing this?

Your report is a bit puzzling, because the current release of Amarok is 2.3. Even GIT is 2.3-GIT. That said, perhaps you could try starting Amarok from the console:

Code: Select all

amarok -d

Some of that output might give you some insight into what is breaking. Some people are having an issue with the info applet, which causes Amarok to crash (segfault) on next startup. If that seems to be the problem, searching this forum for 'info applet' will give you the workarounds available.

Hope this helps,

Valorie

I should note that in some cases the "-d" argument doesn't suffice. It's safer to do this here:

Code: Select all

amarok -d --nofork