Bug 198131

Summary:	Amarok blocks phonon startup and causes "Removed Sound devices" notification
Product:	[Frameworks and Libraries] Phonon	Reporter:	Davide Rondini <davide.rondini>
Component:	Xine backend	Assignee:	Matthias Kretz <kretz>
Status:	RESOLVED WORKSFORME
Severity:	normal	CC:	amarok-bugs-dist, colin, martin.sandsmark, myriam, rdieter
Priority:	NOR
Version:	4.3.0 (KDE 4.2.0)
Target Milestone:	---
Platform:	Fedora RPMs
OS:	Linux
Latest Commit:		Version Fixed In:	4.4.1

Description Davide Rondini 2009-06-28 10:21:15 UTC

Version:            (using KDE 4.2.4)
OS:                Linux
Installed from:    Fedora RPMs

On login, sometimes my system blocks for about a minute. Kwin runs, but
applications don't start and KDE menu don't appear. After that time, I hear the
login sound and everything starts working normally. I suppose it is something
related to phonon because sometimes after the block a window appears saying:

KDE detected that one or more internal sound devices were removed.
Do you want KDE to permanently forget about these devices?
This is the list of devices KDE thinks can be removed:
Output: Default

The output field vary randomly between one of the sound devices I see in KDE
system settings, which are:

PulseAudio (which I set ad preferred device)
HDA Intel (ACL883 Analog)
PulseAudio Sound Server
Default

If I try to remove devices as the dialog asks, they will reappear at next
reboot and the problem persists.

After a period of testing I realized that the problem is generated when I leave amarok opened when shutting down. This causes Amarok to be loaded at login, causing some conflict. If I close Amarok before shutdown, the new boot is always normal.

I filed this bug in Fedora bug tracking and they suggested me to post it here.

https://bugzilla.redhat.com/show_bug.cgi?id=489839

The problem started with update to KDE 4.2.0 with amarok 2.0.1, and persists with 4.2.4 and amarok 2.1

Comment 1 Mark Kretschmann 2009-06-28 14:12:01 UTC

Sounds more like a KDE/Phonon issue to me. Reassigning.

Comment 2 Myriam Schweingruber 2009-11-08 21:44:46 UTC

Which phonon backend are you using? This might be a duplicate of bug 188444

Comment 3 Davide Rondini 2009-11-10 09:01:20 UTC

I'm using Xine backend. It don't seem to me that the bug is the same as 188444. I worked it around by exluding amarok from being restarted in new session. It seems like that durng login amarok tries to access audio resources before phonon has completed its initialization, and this causes some kind of conflict.

Comment 4 Myriam Schweingruber 2009-11-10 19:08:57 UTC

Since Phonon is started on KDE start and before Amarok, so I very much doubt that. Asking the devs.

Comment 5 Myriam Schweingruber 2010-04-06 13:04:22 UTC

I can't reproduce this here, using Kubuntu 10.04 beta with KDE SC 4.4.2