Bug 81710 - logging in at runlevel 5 skips most console.perms
logging in at runlevel 5 skips most console.perms
Status: CLOSED NOTABUG
Product: Red Hat Linux
Classification: Retired
Component: pam (Show other bugs)
8.0
All Linux
medium Severity medium
: ---
: ---
Assigned To: Nalin Dahyabhai
Jay Turner
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2003-01-13 00:05 EST by Martin Flack
Modified: 2015-01-07 19:02 EST (History)
1 user (show)

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


Attachments (Terms of Use)

  None (edit)
Description Martin Flack 2003-01-13 00:05:03 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20021003

Description of problem:
/etc/security/console.perms is programmed to differentiate between console and
xconsole logins, which means if you operate in runlevel 5 and login graphically
(as compared with logging in at a tty first and then running startx) device
files such as /dev/audio are not set to your user's ownership.

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1. Login at gdm.
2. Try to play audio.

    

Actual Results:  Permission error.

Expected Results:  Audio playing.

Additional info:

[root@solvent security]# diff -u console.perms~ console.perms
--- console.perms~      2002-08-02 11:08:29.000000000 -0400
+++ console.perms       2003-01-12 23:53:16.000000000 -0500
@@ -70,3 +70,4 @@

 <xconsole> 0600 /dev/console 0600 root.root
 <xconsole> 0600 <dri>       0600 root
+<xconsole> 0600 <sound>      0600 root
Comment 1 Martin Flack 2003-01-13 00:10:35 EST
Oops, I'm wrong, I didn't have pam_console.so in my /etc/pam.d/gdm file. It does
work.

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