Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.

Bug 118970

Summary: alsa interface muted on startup
Product: [Fedora] Fedora Reporter: Malcolm Amir Hussain-Gambles <malcolm>
Component: alsa-libAssignee: Bill Nottingham <notting>
Status: CLOSED DUPLICATE QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: rawhideCC: rvokal
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2006-02-21 19:02:06 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Malcolm Amir Hussain-Gambles 2004-03-23 13:49:23 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6)
Gecko/20040207 Firefox/0.8

Description of problem:
On startup the alsa mixer is muted, and cannot change this unless
I launch xine and click unmute. Then everything works fine.
Not sure this is in the right area, but need to default to unmuted
rather than muted on boot

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


How reproducible:
Always

Steps to Reproduce:
1.Boot
2.no sound
3.run xine
4.click unmute
5.sound works
    

Actual Results:  Sound is muted until xine unmutes it

Expected Results:  Should boot with sound on rather than off, as the
sound in the 
panel (i.e. gnome volume control) doesn't seem to use the alsa mixer
directly
i.e. selecting mute and unmute does nothing from boot, it works
once xine unmutes the sound

Additional info:

Comment 1 Bill Nottingham 2004-03-23 17:28:45 UTC

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

Comment 2 Red Hat Bugzilla 2006-02-21 19:02:06 UTC
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.