Bug 144643 - console permission definition for <sound> is not flexible enough
console permission definition for <sound> is not flexible enough
Status: CLOSED WONTFIX
Product: Fedora
Classification: Fedora
Component: pam (Show other bugs)
3
All Linux
medium Severity medium
: ---
: ---
Assigned To: Tomas Mraz
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2005-01-10 03:39 EST by Todd Warner
Modified: 2007-11-30 17:10 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2005-01-10 03:51:32 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:


Attachments (Terms of Use)

  None (edit)
Description Todd Warner 2005-01-10 03:39:42 EST
I should have filed this a year ago when I noticed it - sorry...

In my household, my FC3 box has two users: my wife and I. We each have
our own desktop, and we both like to be logged in all day for the most
part. We do this, of course, by setting up gdm.conf to crank up two X
servers in two vt's: edit /etc/X11/gdm/gdm.conf and make sure under
[servers] it reads
0=Standard
1=Standard

Restart X

The problem: the first person to log in gains permission to use the
sound devices, the other does not have permission.

My workaround: we (our users) are in the same group (tandm in this
case). I edited /etc/security/console.perms and changed the <sound>
console permissions to be...
<console>  0660 <sound>      0600 root.tandm
instead of the old
<console>  0660 <sound>      0600 root.root

Restarted things and bingo... sound in both.

I there must be some default that works well for each.
Comment 1 Todd Warner 2005-01-10 03:40:49 EST
"I there must be some default that works well for each."
...should have been...
"I think there must be some default that works well for each."
Comment 2 Tomas Mraz 2005-01-10 03:51:32 EST
I'm sorry but the default won't be changed. Your solution is correct
and exactly what has to be done to support such configuration as yours.
However it would be of no use on normal one-user-in-time desktops.

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