Bug 492500 - Amarok fails to start in gnome after recent update
Summary: Amarok fails to start in gnome after recent update
Keywords:
Status: CLOSED DUPLICATE of bug 491813
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-27 01:43 UTC by Cameron Cross
Modified: 2009-03-27 02:26 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-03-27 02:26:05 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)

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 ***
Note You need to log in before you can comment on or make changes to this bug.