I've had a complete, utter and total X.org lockup during oowriter menu access
happen on two(!) entirely different(!) Linux installations recently.
(make that two out of about 8 Linux installations that I'm having more
or less access to, where it crashed "the entire box", then do the math
and you'll realize how annoying this issue is...)

a) Dell Inspiron 8000, Debian unstable, current updates,
01:00.0 VGA compatible controller: ATI Technologies Inc Rage Mobility M4 AGP
OOo 2.2.0 or 2.2.1 at the point of this crash (3 weeks ago?)

b) P4 box, RHEL 5 beta, 
using a semi-working/unstable(?) SiliconMotion X.org driver

IMHO this bug is EXTREMELY SEVERE and should be tracked as much as
possible.

I believe that in the notebook case even ssh login was impossible (may
have been "helped" by -mm kernel installation, though).
In the P4 case even kill -9'ing OOo and X.org remotely did NOT help,
it kept showing a frozen picture instead of cleanly reverting to
text mode (driver issue probably).

>From my development experience it may be a problem of OOo taking the
X11 keyboard grab during menu access and then somehow freezing while
holding the grab. X.org keyboard grab handling seems very problematic
and annoying, especially in a debug session during development
(those optionally configurable keyboard grab busting X.org key combos help,
but it's still very annoying).

My opinion is that this bug is NOT really an OOo issue, rather it's a very
severe limitation of X server operation (if it indeed is a
"freeze during keyboard grab" issue) and should thus be forwarded to
X.org for discussion.

This bug deserves severity "Apocalypse" or so, I'd think.
(Severity "important" definitely doesn't cut it)

Oh, I actually forgot the most annoying part of the problem:
A deadly keyboard grab kills access to keyboard *entirely*,
but in *some* cases only (this OOo crash was one of those, on both boxes):
i.e. not even console key combos work and there's no way to get back
to another tty to be able to kill the X server.
Ctrl-Alt-Backspace doesn't work either.
This is what makes the whole issue extremely ugly and
singularly unacceptable, thus prolonged discussion between X.org
and kernel groups would be in order, to provide a workable workaround/fix
for those keyboard grab issues.

My fingers were itching to already CC *both* X.org and LKML,
but then I managed to prevent that from happening ;)

Thanks,

Andreas Mohr


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to