Bug 790891 - Corrupt volume level at AlsaMixer on RHEL 6.2 GA JP.
Summary: Corrupt volume level at AlsaMixer on RHEL 6.2 GA JP.
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: xorg-x11-drv-intel
Version: 6.2
Hardware: x86_64
OS: Linux
unspecified
urgent
Target Milestone: rc
: 6.2
Assignee: Adam Jackson
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-02-15 16:47 UTC by Xiao Yousheng
Modified: 2012-03-05 19:23 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
SYSTEM SN OR ID: NA17173217 Form Factor: Planar Type: IS7XM Planar Level: Rev:1.0 Planar SN: 11S11200805UUDE121310Z BIOS Level: 9SKT22A CPU 1 :Ivy Bridge E3-1275, V2,3.50GHz DIMM 1:Samsung PC3-12800E 2GB,M391B5773DH0-CK0 DIMM 2: DIMM 3: DIMM 4: Monitor Type:DELL 2407
Last Closed: 2012-03-05 19:23:49 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Xiao Yousheng 2012-02-15 16:47:28 UTC 
Description of problem:
[Linux]Corrupt volume level at AlsaMixer on RHEL 6.2 GA JP.

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


How reproducible:


Steps to Reproduce:
 1.Install RHEL 6.2 GA 
 2.Install audio driver L7AUD05US17 and then reboot. 
 3.Logout. 
 4.Login with root and Language select JP. 
 5.Launch AlsaMixer in terminal. 
 6.You can see the screen is corrupt.
  
Actual results:


Expected results:


Additional info:
Comment 1 Adam Jackson 2012-02-15 19:59:48 UTC 
(In reply to comment #0)

>  1.Install RHEL 6.2 GA 
>  2.Install audio driver L7AUD05US17 and then reboot. 

What in the world is "L7AUD05US17"?  It's not something we ship, as far as I know.
Comment 2 Adam Jackson 2012-03-01 20:03:17 UTC 
Reporter, please, respond.  I appreciate your continued dedication to filing bug reports, but as far as I can tell you have _never_ followed up with any additional information I've requested, which makes it very difficult to work on any issues you report since I generally don't have the same hardware you do.
Comment 3 Adam Jackson 2012-03-05 19:23:49 UTC 
Closing per comment #2.  Please reopen when you have provided the requested information.
Note You need to log in before you can comment on or make changes to this bug.