On Tue, 2004-10-26 at 03:03, mike lewis wrote: > Just to be clear, it looks like xine is not quiting, wheres for me, > xine is gone but the video is locked..
The xine process disappears, so I suppose it quits. Display isn't xine, but the Freevo menu, however alle input is locked, and the leftover picture you get, might be due to using framebuffers, which doesn't store freevos last picture in a backbuffer like X. > So, last step to confirm: > run xine from within freevo, then ssh to the box and run: > ps aux | grep xine > kill -2 'xines_pid' I did this, and xine exited cleanly, leaving me a usable interface. > There may be more than on, if so, kill them all.. If -2 does not > work, win it with -9. Now, after xine is no longer running, is freevo > working again? If so, it looks like xine is the cause, not listening > to the 'quit' command from stdctl. But xine disappears, so more likely it might be freevo which does not detect that it has quit. If Freevo is still waiting for the xine-pid, X11 displays the last backbuffer of the freevo window. In your framebuffer, however , the locked freevo will not update the screen, nor does the framebuffer recall the last freevo picture, and so leaves a residue xine frame on the monitor. > Let me know how it goes.. For me, xine quits fine, but leaves a lock > on the fbvideo dev. I am going to try df_xine, hopefully directfb > will be better than vidixfb.. > > Mick - Jesper
signature.asc
Description: This is a digitally signed message part
