Every time I launch xfce4-mixer, from the volume icon in XFCE or from console, it crashes. The only info I have is "Segmentation fault"
Steps to Reproduce:
1. Launch xfce4-mixer from console or volume icon
Steps to Reproduce:
What does cmds 'dmesg' and 'cat ~/.xsession-errors' say about it?
Try also to start xfce4-mixer with debugging enabled, 'xfce4-mixer -d'.
xsession-errors says nothing about this. Dmesg returns:
[ 4572.471752] xfce4-mixer: segfault at 28 ip 0000003b034aab45 sp 00007fffb9599470 error 4 in libgtk-x11-2.0.so.0.2400.17[3b03400000+421000]
And "xfce4-mixer -d" returns the typical list of devices and channels, followed by the "segfault" notice.
Unfortunately my x86_64 machine broke down, so currently I can't debug this more. :\
Finally managed to test this, but I can't reproduce. Is this still valid?
It's still valid for me, even with latest XFCE update. Same error.
I want to report it still happens in Mageia 3 in 2014-08-13.
It happened as I changed a setting, Auto-Mute, one of the toggles, to On or Enabled. The mixer dialog closed instantly. Now the speaker icon is shown, it works (volume can be changed with the mousewheel, for instance) but when I right-click on it and select "Run audio mixer", xfce4-mixer opens, draws the dialog and dies (segfault message when run on the terminal).
After removing Pulseaudio and using alsamixer to disable the Auto-Mute, regrettably nothing changed. Still can use it to change the volume, though.
I have a machine with Mageia 4 (64-bit, too), let me see... this behavior is no longer present in Mageia 4. Auto-mute was even enabled, I disabled, re-enabled and the mixer works flawlessly.
As Mageia 3 approaches end-of-life, maybe this can be marked WONTFIX. Just a suggestion, other people might have different needs.
SUGGESTION: Mark as WONTFIX.
Mageia 3 changed to end-of-life (EOL) status 4 months ago.
Mageia 3 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of Mageia
please feel free to click on "Version" change it against that version of Mageia
and reopen this bug.
Thank you for reporting this bug and we are sorry it could not be fixed.
The Mageia Bugsquad