Bug 194843

Summary:	Application Amarok is crashing at start on Ubuntu 9.0.4
Product:	[Applications] amarok	Reporter:	Nilesh Mahajan <mahajan.nilu>
Component:	general	Assignee:	Amarok Bugs <amarok-bugs-null>
Status:	RESOLVED DUPLICATE
Severity:	crash
Priority:	NOR
Version First Reported In:	2.0.2
Target Milestone:	---
Platform:	Ubuntu
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Nilesh Mahajan 2009-06-01 11:05:13 UTC

Version:           2.0.2 (using KDE 4.2.2)
OS:                Linux
Installed from:    Ubuntu Packages

I installed amarok on ubuntu 9.0.4 using apt-get install. After that when I run amarok,
 then it crashes giving following error message :

amarok(7745) Phonon::KdePlatformPlugin::createBackend: using backend:  "Xine"
ASSERT: "d" in file /usr/include/ksharedptr.h, line 120
KCrash: Application 'amarok' crashing...
sock_file=/home/nmahajan/.kde/socket-pnq-nmahajan/kdeinit4__0
<unknown program name>(7744)/: 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)" "

bytetrace:

(gdb) run

Starting program: /usr/bin/amarok
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb30bb950 (LWP 8638)]
amarok(8641) Phonon::KdePlatformPlugin::createBackend: using backend:  "Xine"
ASSERT: "d" in file /usr/include/ksharedptr.h, line 120
<unknown program name>(8638)/: 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)" "


Program exited with code 0377.
KCrash: Application 'amarok' crashing...
sock_file=/home/nmahajan/.kde/socket-pnq-nmahajan/kdeinit4__0
(gdb)

Comment 1 Myriam Schweingruber 2009-06-01 11:25:14 UTC

I am sorry, but this backtrace is not useful as you are missing debugging symbols. You need to install the -dbg packages.
Also, this is a duplicate of another bug

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