Bug 91276 – xfce4-mixer crashes panel on alsa restart

• Product: Gentoo Linux
• Status: RESOLVED UPSTREAM

[Description genbug 2005-05-03 00:57:25 UTC]

/etc/init.d/alsasound restart from xterm under xfce4 takes out the whole xfce panel

Reproducible: Always
Steps to Reproduce:
1.start system with alsa , start xfce4 with mixer on panel
2.open xterm and run /etc/init.d/alsasound restart
3.

Actual Results:  
poof ! No more xcfe-panel.

Expected Results:  
xfce-mixer becomes inoperable / greyed-out but panel remains funtional.

[Comment 1 Roland Bär 2005-05-03 02:59:31 UTC]

Wether it make sense to restart this boot service or not:
Can confirm this for:
- xfce4-mixer-4.2.0
- xfce4-mixer-4.2.1
and corresponding xfce4-panel's

The underlying reason seams to be that "/dev/mixer" gets poll()"ed", and
during restart invalid => SIGKILL 

[Comment 2 genbug 2005-05-03 03:33:57 UTC]

You may have this configured as a boot service but that is your choice nothing to do with the software.

And it does make sense sometimes restart a service, and this should be possible without this sort of collateral dammage.

Thanks anyway for you good technical input to this bug report.

[Comment 3 Roland Bär 2005-05-03 06:16:21 UTC]

I have filled in an upstream bugreport:
http://bugzilla.xfce.org/show_bug.cgi?id=935

[Comment 4 Helmut Eberharter 2005-06-07 14:28:11 UTC]

i noticed this bug with amarok (everytime a new song gets/is selected)

[Comment 5 Dominik Kozaczko 2006-01-08 13:28:59 UTC]

Confirmed on Xfce-4.2.2
This happens even if xfce4-mixer isn't started (not attached to panel)

[Comment 6 Brad Cowan (RETIRED) 2006-02-17 13:03:33 UTC]

I'm closing this as it's a known upstream problem

[Comment 7 genbug 2006-02-17 15:51:06 UTC]

 RESOLVED UPSTREAM

it's known and recognised upstream, I dont see the solution. 

If it is  RESOLVED UPSTREAM please post details. I opened a bug "upstream"
on this and have not had any notification of a resolution. 

Thx.

[Comment 8 Josh Nichols (RETIRED) 2006-12-19 19:55:08 UTC]

RESOLVED UPSTREAM means it's an issue that we can't deal with (ie it is beyond our skills to fix), and it's up to upstream to fix it.

[Comment 9 Samuli Suominen (RETIRED) 2008-12-16 19:09:51 UTC]

*** Bug 251216 has been marked as a duplicate of this bug. ***