Bug 230676

Summary:	Amarok crashes when restarting after adding an Info applet to the middle pane
Product:	[Applications] amarok	Reporter:	Mahendra Tallur <mahen>
Component:	general	Assignee:	Amarok Developers <amarok-bugs-dist>
Status:	RESOLVED DUPLICATE
Severity:	normal	CC:	A.Fettouhi, lfranchi, scarpino, simon.esneault
Priority:	NOR
Version:	2.3.0
Target Milestone:	---
Platform:	Arch Linux
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Mahendra Tallur 2010-03-14 11:36:41 UTC

Version:           2.3.0 (using KDE 4.4.1)
OS:                Linux
Installed from:    Archlinux Packages

Hi ! First, congrats to the devs & triagers ;)

Here's an issue a few of us reproduced on Archlinux. (KDE 4.4.1, Amarok 2.3.0)

- start Amarok
- add an "Info" applet to the middle pane
- quit
- restart

--> you'll get a crash each time, until you remove the ~/.kde4/share/config/amarok_homerc file

Here's what I get in the terminal :

"amarok(8491)/kdecore (KSycoca) KSycocaPrivate::openDatabase: Trying to open ksycoca from  "/var/tmp/kdecache-mahen/ksycoca4"
QDBusObjectPath: invalid path ""
Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
amarok(8491)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig:
amarok(8491)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig:
amarok(8491)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig:
Calling appendChild() on a null node does nothing.
amarok(8491)/libplasma Plasma::ThemePrivate::config: using theme for app "amarok"
QGraphicsLinearLayout::removeAt: invalid index 1
<unknown program name>(8490)/: 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" " 

[mahen@mahen ~]$ KCrash: Application 'amarok' crashing..."

Cheers !

Comment 1 André Fettouhi 2010-03-14 11:56:51 UTC

Can also confirm this on arch linux 64 bit installation.

Comment 2 Mikko C. 2010-03-14 12:43:57 UTC

iirc, this is/was a bug in QT. Not sure if it's fixed yet. Leo?

Comment 3 Myriam Schweingruber 2010-03-14 12:46:36 UTC

Yes, this is a known Qt bug, already reported upstream. 
FWIW, if you report a crash, please provide the backtrace generated by Dr. Konqi, the konsole output is usually not sufficient as it doesn't give the code lines where the crash happens. Thank you.

*** This bug has been marked as a duplicate of bug 227639 ***

Comment 4 André Fettouhi 2010-03-14 12:57:27 UTC

How is it then resolved? Is it fixed in the next version of qt 4.6.3?

Comment 5 Myriam Schweingruber 2010-03-16 01:01:33 UTC

Andrö, please follow the bug upstream, since the bug tracker systems are different, it is not possible to link the bugs. Since this is not an Amarok or KDE bug which this particular bugtracker is about, but a Qt one, the bug has been pushed upstream and is therefore closed on our bugtracker.