Bug#258164: Bug#260981: /usr/bin/xine: crashed x windows

[Dan Jacobson <jidanni@jidanni.org>]

S> A user space application such as xine must not be able to interfer with
S> the interrupt handlers that manage your mouse or even the Num Lock key...

I was root, because I didn't chmod /dev/hdd yet. Now done.

S> If it helps debugging, you can try "xine -V none" to start xine without
S> video output. My guess is that won't crash your machine.

Now as regular user, I see the logo, I click the x to close it, and
poof, I am back at the xdm login prompt. Maybe I didn't even need to
click and it would have happened.

Logs only say
X connection to :0.0 broken (explicit kill or server shutdown).
The application 'Gecko' lost its connection to the display :0.0;
most likely the X server was shut down or you killed/destroyed
the application.

and

Fatal server error:
Caught signal 8.  Server aborting

S> If that's true, something about the XShm extension is probably causing the
S> crash...

S> you could also try "(unset DISPLAY; aaxine)" or just run "aaxine" from a
S> text console to verify that the xine engine works fine if you don't use X
S> at all.

That works.

I can play dvds fine with
$ mplayer -ao oss -vf eq=32 dvd://1
BTW.

Anyways, now trying
$ (sleep 200; pstree -al>file;killall xine;killall -9 xine)& xine dvd:/1

One can hear the sound fine, but just sees a blue window for the
movie.

Then when one moves the mouse over any of the buttons, within seconds
all gets locked up again, except the mouse.  The screen turns into a
grey moving mess.  200 passes but it is no help. Again one must walk
over and hit reset.

I am just hoping that you will leave ALT CTRL F1 usable so one can get
to the console at all times.