Bug 125956

Summary: Kmixer does not remember volume settings when altered by a second program; unmuting leaves sound at zero
Product: [Fedora] Fedora Reporter: Flavio Cardone <fcardone>
Component: kdemultimediaAssignee: Than Ngo <than>
Status: CLOSED DUPLICATE QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 2CC: mattdm
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2005-07-28 13:12:21 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 Flavio Cardone 2004-06-14 15:21:02 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:
Hello -

Kmixer has the following problems:

1) if you alter the volume using another program (say xine or xmms),
when you start Kmixer it will show the volume gauges not where you
left them with the second program, but how you left them on Kmixer -
no matter what their actual value is

2) When you mute using Kmixer's tray icon, and you unmute, the icon
will be green (ie volume on) but the main volume gauge will be at zero.

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


How reproducible:
Always

Steps to Reproduce:
1. just use Kmixer as described above
2.
3.
    

Actual Results:  see above

Expected Results:  see above

Additional info:

Comment 1 Matthew Miller 2005-04-26 16:41:44 UTC
Fedora Core 2 is now maintained by the Fedora Legacy project for
security updates only. If this problem is a security issue, please
reopen and reassign to the Fedora Legacy product. If it is not a
security issue and hasn't been resolved in the current FC3 updates or
in the FC4 test release, reopen and change the version to match.

Comment 2 Than Ngo 2005-07-28 13:12:21 UTC

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