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 123688 - gnome-volume-control does not visually change to indicate mute condition
Summary: gnome-volume-control does not visually change to indicate mute condition
Keywords:
Status: CLOSED DUPLICATE of bug 106138
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-media
Version: 2
Hardware: i386
OS: Linux
medium
low
Target Milestone: ---
Assignee: Colin Walters
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2004-05-20 01:38 UTC by Ben Steeves
Modified: 2007-11-30 22:10 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2006-02-21 19:03:20 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)

Description Ben Steeves 2004-05-20 01:38:29 UTC 
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6)
Gecko/20040510 Epiphany/1.2.4

Description of problem:
When "mute" is selected, the gnome-volume-control icon should change
to indicate that main output is muted (a red bar through the speaker
is the typical graphic).

Version-Release number of selected component (if applicable):
gnome-media-2.6.0-1

How reproducible:
Always

Steps to Reproduce:
1. Mute the volume in gnome-volume-control
    

Actual Results:  Icon indicates previous volume level, not muted status.

Expected Results:  Icon should change to indicate volume is muted (or
at least 0).

Additional info:
Comment 1 Marc Deslauriers 2004-05-22 04:12:44 UTC 
Looks like bug #106138
Comment 2 Colin Walters 2004-09-22 03:03:02 UTC 
Indeed, thanks for finding that Marc.

*** This bug has been marked as a duplicate of 106138 ***
Comment 3 Red Hat Bugzilla 2006-02-21 19:03:20 UTC 
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.
Note You need to log in before you can comment on or make changes to this bug.