Bug 412581 - Permissions for sound and video devices do not permit user access
Summary: Permissions for sound and video devices do not permit user access
Keywords:
Status: CLOSED DUPLICATE of bug 411321
Alias: None
Product: Fedora
Classification: Fedora
Component: hal
Version: 8
Hardware: i386
OS: Linux
low
urgent
Target Milestone: ---
Assignee: David Zeuthen
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2007-12-05 18:43 UTC by Peter Gückel
Modified: 2013-03-06 03:53 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-02-24 18:30:04 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Peter Gückel 2007-12-05 18:43:00 UTC
Description of problem:

Since th elast spate of updates (about 150Mb) on Monday, all of the permissions
for the video* and audio devices are set to 660 for root, meaning that no user
account can access a video or audio device. This crashes arts and amarok and
tvtime and others are unable to open neither video nor sound devices. Manually
changing the permissions to 666 for the said devices solves the problem, but
must be done each boot.

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

?

How reproducible:

log in and notice that it is not possible to access any multimedia devices and
that there is a message displayed on the screen about /dev/dsp permission denied
(just the tip of the iceberg of the problem).

Steps to Reproduce:
1. Boot computer
2. Log in
3. Voilà
  
Actual results:

No sound or video for user, but all fine for root account

Expected results:

Users should be able to use multimedia (sound and video) devices.

Additional info:

none comes to mind

Comment 1 Luis Villa 2007-12-05 19:53:49 UTC
This is a duplicate of bug 411321; I can't mark it as such, but as the filer,
you can, kwhiskerz.

Comment 2 Peter Gückel 2008-02-24 18:30:04 UTC

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


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