RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 682562 - gnome-volume-control doesn't respect PULSE_SINK/PULSE_SOURCE
Summary: gnome-volume-control doesn't respect PULSE_SINK/PULSE_SOURCE
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: gnome-media
Version: 6.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: rc
: ---
Assignee: Bastien Nocera
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-03-06 18:57 UTC by Alexander Todorov
Modified: 2017-12-06 10:54 UTC (History)
0 users

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-12-06 10:54:07 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Alexander Todorov 2011-03-06 18:57:21 UTC 
Description of problem:
gnome-volume-control will not respect the PULSE_SINK/PULSE_SOURCE environment variables.

On a system with 2 sound cards where both variables are set via a script in /etc/profile.d (i.e. when the user logs in) the 2nd card is the default. Audio is playing correctly (with minor issues in bug #679122) but the sound control programs are not controlling the correct device. They still think that card 0 is the default card.

According to pulseaudio(1):
       These environment settings take precedence -- if set -- over the configuration settings from client.conf (see above).


Version-Release number of selected component (if applicable):
gnome-media-2.29.91-6.el6.i686
pulseaudio-0.9.21-13.el6.i686


How reproducible:
Always

Steps to Reproduce:
1. Use a system with 2 sound cards. I have 1 internal card and additional USB sound card.
2. Configure the USB card as default via a script:

# cat /etc/profile.d/usb-sound-init.sh 
#!/bin/bash

export PULSE_SINK="alsa_output.usb-C-Media_Electronics_Inc._USB_Multimedia_Audio_Device-00-Device.analog-stereo"
export PULSE_SOURCE="alsa_input.usb-C-Media_Electronics_Inc._USB_Multimedia_Audio_Device-00-Device.analog-stereo"

3. Login into GNOME. 
4. Open up gnome-terminal and verify that $PULSE_SINK/$PULSE_SOURCE are set correctly. 
5. Start gnome-volume-control
  
Actual results:
gnome-volume-control thinks that card0 (the internal card) is the default not taking into account the environment variables.

Expected results:
gnome-volume-control will properly parse PA environment variables and update the UI accordingly. 

Additional info:
Comment 2 RHEL Program Management 2011-03-06 19:18:08 UTC 
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unfortunately unable to
address this request at this time. Red Hat invites you to
ask your support representative to propose this request, if
appropriate and relevant, in the next release of Red Hat
Enterprise Linux. If you would like it considered as an
exception in the current release, please ask your support
representative.
Comment 3 RHEL Program Management 2012-09-21 16:03:26 UTC 
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unable to address this
request at this time.

Red Hat invites you to ask your support representative to
propose this request, if appropriate, in the next release of
Red Hat Enterprise Linux.
Comment 4 RHEL Program Management 2013-10-14 01:08:55 UTC 
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unable to address this
request at this time.

Red Hat invites you to ask your support representative to
propose this request, if appropriate, in the next release of
Red Hat Enterprise Linux.
Comment 5 Jan Kurik 2017-12-06 10:54:07 UTC 
Red Hat Enterprise Linux 6 is in the Production 3 Phase. During the Production 3 Phase, Critical impact Security Advisories (RHSAs) and selected Urgent Priority Bug Fix Advisories (RHBAs) may be released as they become available.

The official life cycle policy can be reviewed here:

http://redhat.com/rhel/lifecycle

This issue does not meet the inclusion criteria for the Production 3 Phase and will be marked as CLOSED/WONTFIX. If this remains a critical requirement, please contact Red Hat Customer Support to request a re-evaluation of the issue, citing a clear business justification. Note that a strong business justification will be required for re-evaluation. Red Hat Customer Support can be contacted via the Red Hat Customer Portal at the following URL:

https://access.redhat.com/
Note You need to log in before you can comment on or make changes to this bug.