Can’t open “Change sound volume and sound events” since i’ve moved to MATE 1.8.0. (from 1.6) And there’s no sound control in the panel.
How to do that it will work?
One bug report I’ve managed to find where ‘mate-volume-control’ is not working as expected, (but the issue is reported to be with the incorrect primary audio device selected).
On 19/07/14 18:26, andranique wrote:
>
> Can’t open “Change sound volume and sound events” since i’ve moved to
> MATE 1.8.0. (from 1.6) And there’s no sound control in the panel.
> How to do that it will work?
I installed a clean Mate 1.8 (i.e. no prior Mate 1.6) DE and observed
the same issue - no Mate Volume Control Applet running (Segmentation
fault reported when command ‘mate-volume-control-applet’ is run in
console mode). And as this was hanging the system a bit, I disabled it
in ‘System–>Preferences–>Startup Application (Preferences)–>Volume
Control’.
I have the Pulse Audio Server installed/running and I could get volume
control via laptop controls or via VLC (or other media) player volume
control, and also via launching the following programs (after installing
them):
gmixer - Simple and Lightweight Audio Mixer
pavucontrol - PulseAudio Volume Control
Since none of the above options will provide a neat integrated
notification tray volume button control, I followed the link provided by
Deano Ferrari
(http://linux.derkeiler.com/Mailing-Lists/Debian/2014-06/msg00215.html)
and took the advice given there to install volti (An GTK+ application
for controlling audio volume). This works well for me and provides a
tray icon/button for volume control.
The following info is from Yast Software Management module:
"Volti is an GTK+ application for controlling audio volume from system
tray/notification area.
Features:
no pulseaudio, gstreamer, phonon etc. only alsa is needed
internal mixer application, but you can choose any mixer app you prefer
left click opens volume scale (slider)
scroll wheel on tray icon changes volume, increment in percents is
configurable"
Cheers
PS: Thanks to Deano for providing the pointers (links) to this
reasonable workaround!