Bug 492500

Summary: Amarok fails to start in gnome after recent update
Product: [Fedora] Fedora Reporter: Cameron Cross <cameroncros>
Component: amarokAssignee: Aurelien Bompard <gauret>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 10CC: gauret, rdieter, smparrish
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-03-27 02:26:05 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Cameron Cross 2009-03-27 01:43:39 UTC
Description of problem:
amarok fails to start in gnome.

Version-Release number of selected component (if applicable):
Qt: 4.4.3
KDE: 4.2.1 (KDE 4.2.1)
Amarok: 2.0.2

How reproducible:
consistently

Steps to Reproduce:
1.update
2.try start amarok
3.splash screen comes up and stays until you kill the process
  
Actual results:
amarok(4202)/phonon (KDE plugin): QDBusError("org.freedesktop.DBus.Error.ServiceUnknown", "The name org.kde.kded was not provided by any .service files") 
amarok(4202)/phonon (KDE plugin): QDBusError("org.freedesktop.DBus.Error.ServiceUnknown", "The name org.kde.kded was not provided by any .service files") 


Expected results:
amarok starts


Additional info:
D-Bus Message Bus Daemon 1.2.4
Amarok starts up fine in kde.

Comment 1 Rex Dieter 2009-03-27 02:26:05 UTC

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