Update: I suspect this has something to do with MIDI.  I've unplugged my USB-MIDI device & this doesn't happen anymore.  The USB-MIDI device works as expected except for this.  I'm using an M-Audio keystation loaded through Alsa, except in pd I'm accessing it via default-midi rather than alsa-midi because alsa-midi hangs on starting pd.  Any ideas?

Thanks again,

-David

On 3/11/06, david golightly <davigoli@gmail.com> wrote:
Hey Devs,

I've found a bug, doubtless someone here knows what's going on - I've got pd-0.39-2extended on my linux box running 2.6.15-4rt kernel/alsa/jack.  I start jack, fine, start pd, loads & works fine, but if I close & restart pd more than 3 times, pd won't load correctly anymore unless I reboot my machine.  Pd window will open, command line reads:

normally, I see this (pd working correctly):

Pd version 0.39-2extended-test1
compiled 23:27:31 Feb 26 2006
port 5401
TCL_LIBRARY="/usr/local/lib/pd/tcl/library" TK_LIBRARY="/usr/local/lib/pd/tk/library"  "/usr/local/lib/pd/bin/pd-gui" 5401
Waiting for connection request...
... connected
device 2: tried /dev/midi02 READ/WRITE; returned -1
device 2: tried /dev/midi2 READ/WRITE; returned 5

I quit, then reload, the quit, then reload, and I notice that this time pd didn't actually quit - although the window is closed, the bash shell isn't freed.  Then if I restart pd, I see this:

Pd version 0.39-2extended-test1
compiled 23:27:31 Feb 26 2006
port 5408
TCL_LIBRARY="/usr/local/lib/pd/tcl/library" TK_LIBRARY="/usr/local/lib/pd/tk/library"  "/usr/local/lib/pd/bin/pd-gui" 5408
Waiting for connection request...
... connected
device 2: tried /dev/midi02 READ/WRITE; returned -1

and the Pd window will open, but the Windows and Media menus are not populated, & I can't open any files.  pstree reveals 2 running pd & pd-gui processes.  sudo killall pd; sudo killall pd-gui isn't effective in killing them.

What's going on here?  Why is pd not quitting completely?  Additionally, sometimes pd will cause the jack server to stop unexpectedly.

Hopefully this is a known issue & I've just done something blockheaded here....

Thanks,

David