Bug 492182 - Amarok hangs on startup
Summary: Amarok hangs on startup
Keywords:
Status: CLOSED DUPLICATE of bug 492143
Alias: None
Product: Fedora
Classification: Fedora
Component: amarok
Version: 10
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Aurelien Bompard
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-03-25 19:06 UTC by Zuzana
Modified: 2009-03-25 19:23 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-03-25 19:13:49 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Zuzana 2009-03-25 19:06:49 UTC
Description of problem:
Amarok hangs on startup.

Version-Release number of selected component (if applicable):
amarok-2.0.2-3.fc10.i386

How reproducible:
Always

Steps to Reproduce:
1. run amarok
2.
3.
  
Actual results:
amarok hangs with the following errors:
$ amarok
amarok(3036)/phonon (KDE plugin): QDBusError("org.freedesktop.DBus.Error.ServiceUnknown", "The name org.kde.kded was not provided by any .service files") 
amarok(3036)/phonon (KDE plugin): QDBusError("org.freedesktop.DBus.Error.ServiceUnknown", "The name org.kde.kded was not provided by any .service files") 
<unknown program name>(3035)/: 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." " 


Expected results:
no errors, amarok starts

Additional info:
Only splash image is displayed.

Comment 1 Rex Dieter 2009-03-25 19:13:49 UTC

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

Comment 2 Rex Dieter 2009-03-25 19:14:41 UTC
To be sure it's a dup,
rpm -q libX11
(is it libX11-1.1.5-1.fc10 ?)

and for giggles, are you using nvidia binary drivers or not?

Comment 3 Zuzana 2009-03-25 19:23:41 UTC
Yes, it is libX11-1.1.5-1.fc10.i386.

I have VESA drivers enabled without any hardware acceleration.


Note You need to log in before you can comment on or make changes to this bug.