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 679122 - gnome-volume-control: Sound at 100% and no sound output
Summary: gnome-volume-control: Sound at 100% and no sound output
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: 670159
TreeView+ depends on / blocked
 
Reported: 2011-02-21 16:41 UTC by Alexander Todorov
Modified: 2017-12-06 12:45 UTC (History)
3 users (show)

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


Attachments (Terms of Use)
gnome-volume-manager screenshot. (24.49 KB, image/png)
2011-02-21 16:41 UTC, Alexander Todorov
no flags Details

Description Alexander Todorov 2011-02-21 16:41:32 UTC
Created attachment 479954 [details]
gnome-volume-manager screenshot.

Description of problem:
I have 2 sound cards on my laptop. 1st is the integrated sound card, the second is C-Media USB sound card (a USB docking station actually). 

When I try to play sound using the C-Media card as output there's nothing coming out of the speakers. See steps to reproduce for more info.


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. Perform clean RHEL6 desktop install. 
2. Connect the USB sound card to the computer.
3. Login into GNOME as normal user (not root).
4. Using rhythmbox playing online radio (or other sound app) verify that the laptop integrated sound card works. In my case I can hear the music that's playing.
5. Open gnome-volume-control  and under Output select the USB card. 
  
Actual results:
No sound on the USB card.

Expected results:
There is sound on the USB card.

Additional info:
As seen on the screenshot the Output volume slider is at 100% but there was no sound coming out of the device. After I moved the slider left and right again suddenly the music appeared on the external USB card. 

This makes me think that the default output level for the USB device is 0% but the gnome-volume-manager doesn't detect that.  We have 2 issues then:

1) default output level is 0
2) the GUI doesn't take this into account. 


I have no idea how/where can I check what is the default sound level on a clean install but I can re-test if necessary.

Comment 2 Alexander Todorov 2011-03-06 18:39:44 UTC
Possible duplicate of bug #664586.

Comment 3 Alexander Todorov 2011-03-06 18:47:12 UTC
Lennart,
can you tell if this is duplicate or related to 664586?

Comment 5 RHEL Program Management 2011-07-06 01:30:23 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 6 RHEL Program Management 2012-09-21 16:03:32 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 7 RHEL Program Management 2013-10-14 01:10:01 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 8 Jan Kurik 2017-12-06 12:45:59 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.