Bug 7009

Summary:	Amarok prevents pulseaudio to manage soundcard
Product:	Mageia	Reporter:	François Andriot <albator78>
Component:	RPM Packages	Assignee:	Mageia Bug Squad <bugsquad>
Status:	RESOLVED OLD	QA Contact:
Severity:	minor
Priority:	Normal	CC:	juan.baptiste, mageia, stormi-mageia
Version:	2	Keywords:	NEEDINFO
Target Milestone:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Source RPM:	phonon-gstreamer	CVE:
Status comment:

Description François Andriot 2012-08-11 00:11:16 CEST

Description of problem:

Hello, I'm running Mageia 2 with KDE4 desktop, all updates installed. KDE4 is configured to restore my previous session when I login. So when I'm using Amarok (among others), log off, then log in again, Amarok is restarted automatically.

But, at relogin time, Amarok is started, but I see a KDE popup saying something like "Do you want that KDE forgets the following audio device ?" and it is indicating my motherboard-integrated sound card...

I close the KDE popup (answering Yes or No does not matter), then I use "pavucontrol" and see that Pulseaudio does not manage my soundcard, and does not see amarok connected ...

It looks like Amarok is starting too fast, or too early, in the session opening process; so it fails to connect to pulseaudio (which may be not started yet ...), and fallbacks to using Alsa directly, thus preventing other processes to access the soundcard.

As soon as I close Amarok, the soundcard re-appears in pavucontrol. Then, I  restart Amarok, and this time it connects to pulseaudio and everything is OK again. Until the next logoff/logon ...

So, the easy workaroung is to exclude "amarok" from the KDE session restoration.

Comment 1 Manuel Hiebel 2012-08-19 11:33:13 CEST

same issue with the kde updates 4.8.5 in testing ? if yes maybe you should report it at upstrem

CC: (none) => juan.baptiste, mageia

Comment 2 Colin Guthrie 2012-08-29 23:26:49 CEST

Well I don't think it'll be Amarok directly, as it doesn't actually poke directly at sound stuff and always just defers to Phonon.

Can you let me know which Phonon backend you are using?

Comment 3 François Andriot 2012-09-03 19:39:28 CEST

Hello, I'm using gstreamer backend.
And I did not try kde 4.8.5 from -testing repository, I want to stay on stable.

Comment 4 Samuel Verschelde 2013-09-06 18:32:47 CEST

Does it still happen now that KDE 4.8.5 has been submitted to mga2 updates?

Keywords: (none) => NEEDINFO
CC: (none) => stormi
Source RPM: amarok-2.5.0-3.mga2.src.rpm => phonon-gstreamer

Comment 5 Manuel Hiebel 2013-10-22 12:10:54 CEST

This message is a reminder that Mageia 2 is nearing its end of life.
Approximately one month from now Mageia will stop maintaining and issuing updates for Mageia 2. At that time this bug will be closed as WONTFIX (EOL) if it remains open with a Mageia 'version' of '2'.

Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Mageia version prior to Mageia 2's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Mageia 2 is end of life.  If you would still like to see this bug fixed and are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia.

Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Mageia release includes newer upstream software that fixes bugs or makes them obsolete.

-- 
The Mageia Bugsquad

Comment 6 Manuel Hiebel 2013-11-23 16:14:15 CET

Mageia 2 changed to end-of-life (EOL) status on ''22 November''. Mageia 2 is no
longer maintained, which means that it will not receive any further security or
bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of Mageia
please feel free to click on "Version" change it against that version of Mageia
and reopen this bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

--
The Mageia Bugsquad

Status: NEW => RESOLVED
Resolution: (none) => OLD