Bug 751902 - Sound works only for root on a Fedora16 installation running in multi-user.target (runlevel 3)
Summary: Sound works only for root on a Fedora16 installation running in multi-user.ta...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: pulseaudio
Version: 16
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Lennart Poettering
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-11-08 00:51 UTC by Vinu Moses
Modified: 2013-02-13 16:19 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-02-13 16:19:21 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Vinu Moses 2011-11-08 00:51:30 UTC
Description of problem:
In a newly installed Fedora 16 system running on multi-user.target (runlevel 3) as the default runlevel, sound works only for root and not for any other user on the system.

If I log into KDE or Gnome as root, sound works fine.

But if I log into KDE or Gnome as any other user, there is no working sound. Pulseaudio shows only a "Dummy Audio" sound output and does not list the internal sound card.

I may be wrong, but I assume that this is a problem with permissions for access to the sound card as a normal user.

Version-Release number of selected component (if applicable):
pulseaudio-0.9.23-1.fc16.x86_64 (I am not sure if this should be filed under PulseAudio or some other component)

How reproducible:
Always

Steps to Reproduce:
1. Do a fresh install of Fedora 16.
2. Change the default runlevel to multi-user.target (runlevel 3) by running "ln -s /lib/systemd/system/multi-user.target /etc/systemd/system/default.target" as root.
3. Reboot
4. Login as root and startx. Sound works.
5. Logout and login as a normal user and startx. No sound.
  
Actual results:
Sound does not work for any user other than root.

Expected results:
Sound should work in multi-user.target (runlevel 3) for all users and not just root.

Additional info:
In graphical.target (runlevel 5) on the same system, sound works for all users, and not just root.

My hardware profile is available at
http://www.smolts.org/client/show/pub_57069a9a-7216-4214-abe4-6a752f54367c

Comment 1 wagner17 2011-11-09 23:40:54 UTC
I have the same problem too.  My workaround was to add my id to the "audio" group in /etc/group, logout and do "pulseaudio -k" and startx.  I am sure this isn't it the proper solution (I didn't have to do this on F15).

Comment 2 Alex Tucker 2011-11-10 22:12:10 UTC
I have the same symptoms on a upgrade from F15.  The /dev/snd/* don't appear to get ACLs (no + on an ls -l, and logged in user not listed with getfacl /dev/snd/*)

Adding logged in user to "audio" group works around the issue, as noted in comment 1.

Trying to unravel this is hard, as a number of things have changed, e.g. hal is no more.  One thing of note is that "systemd-loginctl list-users" returns no users as being logged in when running KDE or Gnome, launched from either GDM or KDM.

Comment 3 Marina Fadeeva 2011-11-12 21:03:44 UTC
I've the same problem on my two Fedora systems (both upgraded from FC15). 
Workaround from comment 1 works fine. Thanks for the tip!
The bug is really annoying and in previous Fedora versions sound worked well in the 3rd runlevel.

Comment 4 Alex Tucker 2011-11-14 17:36:14 UTC
It appears that the /etc/pam.d/* files can end up in an inconsistent state after an upgrade, which leads to systemd not realizing a user is logged in to the current session and so the ACLs for /dev/* don't get set up accordingly, and so no sound.

David Howells pointed this out in bug 746470 and referred to the underlying bug 753160.  Following his advice and running "authconfig --update --nostart", moving ~/.pulse to e.g. ~/.pulse.old, then logging out and back in has fixed the issue for me (as well as some other issues with ACLs in /dev/*)

Comment 5 wagner17 2011-11-15 08:21:36 UTC
On a clean install there are ACLs on /dev/snd/* but for the heck I ran "authconfig --update --nostart" however there was still no sound in X when booting from runlevel 3.

I can get sound on the console if I play a sound file using aplay.  Once I do startx though "pactl stat" shows that the null sink is being used.

Comment 6 Tomi Leppikangas 2011-11-22 18:01:05 UTC
Same problem here. Fresh FC16 install. In runlevel 5 graphical login sound works, runlevel 3 in text console sound works, after startx sound doesn't work. Same problems with all devices that should have acls.


After logging in in runlevel 3:
[~]# ck-list-sessions 
Session1:
        unix-user = '1000'
        realname = 'Tomi Leppikangas'
        seat = 'Seat1'
        session-type = ''
        active = TRUE
        x11-display = ''
        x11-display-device = ''
        display-device = '/dev/tty1'
        remote-host-name = ''
        is-local = TRUE
        on-since = '2011-11-22T17:48:45.321110Z'
        login-session-id = '2'

[~]# getfacl /dev/snd/pcmC0D0c 
getfacl: Removing leading '/' from absolute path names
# file: dev/snd/pcmC0D0c
# owner: root
# group: audio
user::rw-
user:tomilepp:rw-
group::rw-
mask::rw-
other::---


After starting X with startx:
[~]# ck-list-sessions 
Session1:
        unix-user = '1000'
        realname = 'Tomi Leppikangas'
        seat = 'Seat1'
        session-type = ''
        active = FALSE
        x11-display = ''
        x11-display-device = ''
        display-device = '/dev/tty1'
        remote-host-name = ''
        is-local = TRUE
        on-since = '2011-11-22T17:48:45.321110Z'
        login-session-id = '2'
        idle-since-hint = '2011-11-22T17:51:45.473957Z'
Session2:
        unix-user = '1000'
        realname = 'Tomi Leppikangas'
        seat = 'Seat1'
        session-type = ''
        active = TRUE
        x11-display = ':0'
        x11-display-device = '/dev/tty2'
        display-device = ''
        remote-host-name = ''
        is-local = TRUE
        on-since = '2011-11-22T17:51:19.018383Z'
        login-session-id = '2'

[~]# getfacl /dev/snd/pcmC0D0c 
getfacl: Removing leading '/' from absolute path names
# file: dev/snd/pcmC0D0c
# owner: root
# group: audio
user::rw-
group::rw-
mask::rw-
other::---


If i switch back to console [shft+alt+F1] sound works again:
[~]# ck-list-sessions 
Session1:
        unix-user = '1000'
        realname = 'Tomi Leppikangas'
        seat = 'Seat1'
        session-type = ''
        active = TRUE
        x11-display = ''
        x11-display-device = ''
        display-device = '/dev/tty1'
        remote-host-name = ''
        is-local = TRUE
        on-since = '2011-11-22T17:48:45.321110Z'
        login-session-id = '2'
Session2:
        unix-user = '1000'
        realname = 'Tomi Leppikangas'
        seat = 'Seat1'
        session-type = ''
        active = FALSE
        x11-display = ':0'
        x11-display-device = '/dev/tty2'
        display-device = ''
        remote-host-name = ''
        is-local = TRUE
        on-since = '2011-11-22T17:51:19.018383Z'
        login-session-id = '2'

[~]# getfacl /dev/snd/pcmC0D0c 
getfacl: Removing leading '/' from absolute path names
# file: dev/snd/pcmC0D0c
# owner: root
# group: audio
user::rw-
user:tomilepp:rw-
group::rw-
mask::rw-
other::---

Comment 7 wagner17 2012-03-08 04:12:31 UTC
This bug also applies to Fedora 17 alpha but I am not sure if I should file a new bug or if there is a way to change this bug report to say that it also affects that version.

Comment 8 Riccardo 2012-04-24 21:44:41 UTC
I have the same problem.... :-(

Comment 9 Tomi Leppikangas 2012-06-18 14:00:38 UTC
Bug 806491 has same problem?

Comment 10 wagner17 2012-06-27 05:21:56 UTC
Using the partial solution suggested in that bug fixes the issue for me.  Thanks for pointing out the bug!
https://bugzilla.redhat.com/show_bug.cgi?id=806491#c9

It was disturbing to read in the bug comments that systemd does not support startx.  I didn't realize booting into runlevel 3 and using startx was so quaint that it's no longer supported.

Comment 11 Riccardo 2012-06-27 07:16:01 UTC
Ok. I added my username to all groups interested in the sound. After some reboots it works now. Too bad, because the strength of Linux was just the freedom to customize. If now the system is only developed for graphics .... I'm sorry.
Thank You for Your support.

Comment 12 Fedora End Of Life 2013-01-16 14:59:07 UTC
This message is a reminder that Fedora 16 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 16. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '16'.

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 Fedora version prior to Fedora 16'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 Fedora 16 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 Fedora, you are encouraged to click on 
"Clone This Bug" and open it against that version of Fedora.

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 Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 13 Fedora End Of Life 2013-02-13 16:19:24 UTC
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 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 
Fedora please feel free to reopen this bug against that version.

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


Note You need to log in before you can comment on or make changes to this bug.