Bug 3221

Summary:	No sound device (only Dummy Output) can be initialised since the upgrade to systemd
Product:	Mageia	Reporter:	Rémi Verschelde <rverschelde>
Component:	RPM Packages	Assignee:	Mageia Bug Squad <bugsquad>
Status:	RESOLVED DUPLICATE	QA Contact:
Severity:	normal
Priority:	Normal	CC:	mageia
Version:	Cauldron
Target Milestone:	---
Hardware:	i586
OS:	Linux
Whiteboard:
Source RPM:		CVE:
Status comment:
Bug Depends on:
Bug Blocks:	2120

Description Rémi Verschelde 2011-10-29 16:31:32 CEST

Description of problem:
I installed systemd when it was pushed to Cauldron a few days ago. Since then I experience a few issues, among those the loss of my audio output.

Before using systemd, pavucontrol and kmix would use "Internal audio analog stereo" as the default audio output. After the update, this output was not listed anymore and the only possible choice was "Dummy Output", which results in no sound.

I found a workaround for this issue on openSUSE's Bugzilla: https://bugzilla.novell.com/show_bug.cgi?id=718760
Adding my user to the "audio" group allowed me to initialise my sound device again. There isn't much info on the bug report I listed before, because it was flagged as a duplicate of this bug: https://bugzilla.novell.com/show_bug.cgi?id=717397
I did not read the whole bug report, though, because the quick fix worked for me.


How reproducible:
Every time I boot Cauldron if my user does not belong to the "audio" group.


Steps to Reproduce:
1. Use systemd
2. Boot
3. Open kmix or pavucontrol

Manuel Hiebel 2011-10-29 16:53:20 CEST

Blocks: (none) => 2120

Manuel Hiebel 2011-10-29 16:58:48 CEST

CC: (none) => mageia

Comment 1 Colin Guthrie 2011-10-29 18:12:22 CEST

Please fix your pam.d system-auth file that RPM warned you about during upgrade. 

There are a few duplicate bugs here about this and it's been mentioned several times on mageia-devel mailing list, so please try harder to find duplicates before reporting bugs (i.e. searching for "sound systemd" would have found the duplicate bug - actually it only finds this and the duplicate bug!). 

Of course it could be something else in which case please ignore my chastising and reopen :D (and of course I see you did try and search on other distros for a bug, but just not for closed bugs in our own distro it seems, so please don't take my comments above too much to heart as I mean it in a friendly way!)

And, yes, we do need to handle this better before mga2, as expecting every user to do this is probably a little too optimistic. Rest assured there have been discussions about how best to handle the pam.d files and perhaps not treat them as configuration files quite so much as we do now.

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

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

Comment 2 Rémi Verschelde 2011-10-29 18:41:18 CEST

This issue was indeed a duplicate of bug 2982.

In fact I searched and found this bug report in our Bugzilla yesterday, but didn't have the time to read it thoroughly. And today, when I tried to fix this issue, I only remembered that I had searched the Bugzilla, but not that I found something.

So, sorry for this duplicate, I'll be more careful next time :)