Xfce4 Mixer

Volume control panel item shows zero volume even if volume is nonzero

Bug #570993 reported by Jarno Suni on 2010-04-27

This bug affects 3 people

Affects		Status	Importance	Assigned to	Milestone
	Xfce4 Mixer	Unknown	Unknown	xfce-bugs #5716
	xfce4-mixer (Ubuntu)	Fix Released	Medium	Unassigned

Bug Description

Binary package hint: xfce4-mixer

Boot Xuibuntu live CD. If you play a sound file by e.g. totem, volume is nonzero, but not according to the volume control in panel. Rolling middle button on the panel item has effect on the icon, but not on volume. But if you right-click the panel item and then click on "Properties" and then on "Close", the mixer setting starts to have effect.

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: xfce4-mixer 1:4.6.1-2ubuntu1
ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-21-generic i686
Architecture: i386
Date: Tue Apr 27 22:50:47 2010
LiveMediaBuild: Xubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100427)
ProcEnviron:
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: xfce4-mixer

Tags:

Revision history for this message

Jarno Suni (jarnos) wrote on 2010-04-27:

Dependencies.txt Edit (4.8 KiB, text/plain; charset="utf-8")

Jarno Suni (jarnos) on 2010-04-28

tags:

added: xubuntu

Jarno Suni (jarnos) on 2010-04-28

summary:

- Volime control panel item shows zero volume even if volume is nonzero
+ Volume control panel item shows zero volume even if volume is nonzero

Revision history for this message

Markhor (markhor) wrote on 2010-05-18:

Exactly the same for me

Revision history for this message

Charlie Kravetz (cjkgeek) wrote on 2010-05-18:

I can not reproduce this issue. I have turn on my audio controls by double-clicking the speaker, then click "select controls" for alsa, then select pulse audio, "select controls" for master. Then I can control the volume. I can then right-click the speaker, select properties, choose what I am controlling to use the volume control. This is the same way I have using the volume control in Xubuntu for at least 4 releases now.

If you are trying to control the volume without choosing what to control, it does not work in Xubuntu.

Revision history for this message

Jarno Suni (jarnos) wrote on 2010-05-18:

IMO the Master track for alsa mixer is the sound default for the volume control plugin in Xubuntu 10.04. Xubuntu should use the default, if user has not selected otherwise. As far as I know, selecting controls in xfce4-mixer does not turn on the controls, it just turns them visible in the mixer. Visiting the properties dialog should not be required to enable the default.

Revision history for this message

Markhor (markhor) wrote on 2010-05-18:

My problem is not that I can't control something. It is all ok.

I have hot keys on my laptop to control sound volume (Fn+up or down arrow). When I press those keys, volume changes, that's ok. But volume manager icon does not update.

Revision history for this message

Charlie Kravetz (cjkgeek) wrote on 2010-05-29:

Markhor:
Thanks for helping improve Xubuntu. However, the hot keys on the keyboard is a completely different bug. Please file a new bug report for that issue.

Revision history for this message

Charlie Kravetz (cjkgeek) wrote on 2010-07-20:

This is also present in Maverick now. Upon starting Xubuntu, the mixer is shown muted, and volume has no bars. If a sound is played, the sound is heard, but the mixer has no effect on volume until it is unmuted and properties selected and closed.

Changed in xfce4-mixer (Ubuntu):
importance:	Undecided → Medium
status:	New → Triaged
tags:	added: maverick

Revision history for this message

Nikola M (nikolam) wrote on 2014-03-02:

xfce4-mixer mutes the sound before slider ends Edit (7.2 KiB, image/jpeg)

Still present in 13.10 64bit.
I use USB sound card
Bus 002 Device 002: ID 0d8c:000e C-Media Electronics, Inc. Audio Adapter (Planet UP-100, Genius G-Talk)
I posted a screenshot where xfce4-mixer mutes the sound way before slider end.

Revision history for this message

Theo Linkspfeifer (lastonestanding) wrote on 2018-08-21:

This was fixed long ago (4.10).