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 111627 - Mute state not shown in Gnome Volume Control applet
Summary: Mute state not shown in Gnome Volume Control applet
Keywords:
Status: CLOSED DUPLICATE of bug 106138
Alias: None
Product: Fedora
Classification: Fedora
Component: redhat-artwork
Version: 1
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Alexander Larsson
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2003-12-06 20:19 UTC by Mads Villadsen
Modified: 2007-11-30 22:10 UTC (History)
0 users

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

Attachments (Terms of Use)

Description Mads Villadsen 2003-12-06 20:19:14 UTC 
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4.1)
Gecko/20031114 Galeon/1.3.10

Description of problem:
With the bluecurve theme the muted state of the Gnome Volume Control
applet is not shown.

However the low/medium/high volume states are shown.

Version-Release number of selected component (if applicable):
redhat-artwork-0.88-1

How reproducible:
Always

Steps to Reproduce:
1. Add volume control applet to panel.
2. Right-click applet.
3. Select Mute.
4. Applet looks the same as before.
    

Actual Results:  No difference in appearance of applet.

Expected Results:  Applet should be shown with a red slash across to
indicate the muted state.

Additional info:
Comment 1 Miloslav Trmac 2003-12-06 21:20:00 UTC 
This is a duplicate of bug 106138.
Triage->Duplicate 106138
Comment 2 Aleksey Nogin 2004-01-07 05:22:55 UTC 

*** This bug has been marked as a duplicate of 106138 ***
Comment 3 Red Hat Bugzilla 2006-02-21 19:00:19 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.