Actually, it's also having the same problems with STOP. I'm not sure why, but the Freevo threaded Xine seems to take a LONG time to die.
If I run the same commands manually, and pass it "quit" it stops very quickly, but the current "auto-kill" kills Xine before it has time to quit, which it does in more than 3 seconds. So, by increasing the time.sleep(0.3) value to something bigger, I was able to do a clean shutdown of Xine; however, I'm still not sure what is taking so long :) On Sun, Sep 07, 2003 at 07:20:43PM +0200, Dirk Meyer wrote: > Aubin Paul wrote: > > On Sun, Sep 07, 2003 at 06:14:05PM +0200, Dirk Meyer wrote: > >> Than we should find the bug before 1.4. > > > > Indeed :) > > > >> It should do this. EXIT and STOP are mapped to STOP. This sends 'quit' > >> to xine and than waits 3 secs for xine to quit. If this doesn't > >> happen, Freevo will force xine to quit. It works for me. > > > > It should; but what seems to happen is that if I hit EXIT (not STOP) > > then Xine is killed. If I hit STOP it exits cleanly. > > Can you add some more debugs to find the bug. It should both map to > the same event. > > > Dischi > > > -- > If you choke a Smurf, what color does it turn? ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Freevo-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freevo-devel
