Restarting alsasound causes xfce4-panel to disappear and the theme to change

[Erik Harrison]

On 7/4/05, John Shane <jslists at mtwafrica.org> wrote:
> On Mon, 04 Jul 2005 03:22:35 -0700
> "Brian J. Tarricone" <bjt23 at cornell.edu> wrote:
> 
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA1
> >
> > John Shane wrote:
> > > I've been trying to get sound working on my X30 ThinkPad with Suse 9.3.
> > > One of the things I've tried is to restart sound with the command
> > >
> > > /etc/init.d/alsasound restart
> > >
> > > Sound didn't start working but the xfce4 panel disappeared and the theme
> > > changed. Just to be sure I tried it several times and each time there was
> > > the same result.  What kind of conflict would cause that? IRQ?  Any
> > > suggestions how to trace the cause of this conflict?
> >
> > That's probably the xfce4-mixer plugin causing both xfce4-panel and
> > xfce-mcs-manager to crash.
> 
> Okay, so I removed the volume control plugin from the panel.  That's the
> mixer plugin, right?  I exited and saved the session without the mixer.
> Restarted xfce and tried the alsasound restart once more.  Same result.
> Panel disappears and the theme changes.  Are there any particular log
> files I could check or debug routines to try that would give clues?  John

Going down when the volume applet is running is expected because alsa
tries to kill all alsa using apps when it restarts, IIRC.

If you remove the volume applet from the panel, and the panel still
closes, try attatching GDB to the panel, and grabbing a backtrace when
it closes.



> _______________________________________________
> Xfce mailing list
> Xfce at xfce.org
> http://foo-projects.org/mailman/listinfo/xfce
> http://www.xfce.org
> 


-- 
"This brings me back to a time where I had no worries. 
All I needed to do was watch Perfect Strangers."
-Erik