Bug 505204 - Totem volume control greyed out in absence of pulseaudio
Totem volume control greyed out in absence of pulseaudio
Product: Fedora
Classification: Fedora
Component: totem (Show other bugs)
All Linux
low Severity medium
: ---
: ---
Assigned To: Bastien Nocera
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2009-06-10 20:10 EDT by W. Michael Petullo
Modified: 2009-06-11 04:15 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2009-06-11 04:15:38 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description W. Michael Petullo 2009-06-10 20:10:32 EDT
Description of problem:
Totem's volume control is greyed out and totem is not playing audio tracks when pulseaudio is not installed. Once I installed pulseaudio, totem's volume controls became available.

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

How reproducible:
Every time

Steps to Reproduce:
1. Ensure pulseaudio is not installed
2. Setup GStreamer to use the "automatic" audio sink using gstreamer-preferences
3. Run totem
Actual results:
The volume control in the main application window is greyed out.

Expected results:
The volume control should work regardless of whether the application is using pulsesink or alsasink.

Additional info:
Audio devices are no longer assigned the proper permissions when I log in. pam_console used to do this, but ConsoleKit does not seem to. On the other hand, ConsoleKit seems to set the permissions for /dev/apm-bios, /dev/console, /dev/fb, etc.
Comment 1 Bastien Nocera 2009-06-11 04:15:38 EDT
Well, it's not going to work well at all, given the code in totem-use-pulsesink-volume.patch.

We force-use pulsesink, to try and get it to handle the per-application volume. This is done using playbin2 in F12, and I won't be fixing this for F-11.

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