Re: [linux-audio-user] how to force an alsa midi cleanup?

From: Fernando Lopez-Lezcano <nando@email-addr-hidden>
Date: Wed May 17 2006 - 22:09:47 EEST

On Wed, 2006-05-17 at 03:12 -0700, Robert Persson wrote:
> On Tuesday 16 May 2006 19:56 you were like:
> > On 5/16/06, Robert Persson <ireneshusband@email-addr-hidden> wrote:
> > > The situation I have right at the moment is that the connection graph in
> > > qjackctl is showing midi ports for rosegarden, even though there is no
> > > rosegarden running (I have double-checked using "ps -A | grep rose").
> >
> > I've been having this problem a lot lately with Rosegarden. I'm using
> > Rosegarden4. I've been getting rid of it by doing "killall
> > rosegarden4". The Rosegarden sequencer process is named something
> > different, like "rosegardensequencer". You might try killing that as
> > well.
>
> I've done all those things -- clicked refresh, killalled rosegarden and
> anything like rosegarden, kill -9ed rosegarden, kill -9ed anything to do with
> wine or dssi, then chopped them up and fed them to the wolves, and then blown
> up the wolves. But it's still there. And now it's been joined by non-existent
> session of muse sequencer (which hadn't been behaving at all even when it did
> exist, at least as far as midi connections went).
>
> I guess I've got to get around to that reboot I was planning.

Most probably.
Have you checked /var/log/messages and/or the output of dmesg? Most
probably you will find a kernel oops that somehow touched the alsa
driver only. A reboot is the only option if that happened.

-- Fernando
Received on Thu May 18 04:15:05 2006

This archive was generated by hypermail 2.1.8 : Thu May 18 2006 - 04:15:05 EEST