Re: Possible Show-Stopper bug in X
gsstark@MIT.EDU (Gregory S. Stark) writes:
> Brenden seemed to think it was related to PCI detection changes in the
> 3.3.2.2 XF86 release which sounds right to me. Have you tried 3.3.2.2-2 ?
> I'm about to try it tonight. Brenden didn't close the bug so I'm not
> optimistic, but he did say it closed every critical bug so maybe.
I just tried 3.3.2.2-2 and it didn't help. In fact it was much worse, it
didn't correctly restore the text mode after the crash.
Just to be clear: DO NOT try 3.3.2.2-2 if you've had this problem already and
you don't have some network access or a serial console to log in and run
restoretextmode.
Incidentally here's a useful hack:
in /etc/kbd/default.map bind Spawn_Console to some unused key:
control keycode 127 = Spawn_Console
in /etc/inittab:
kb::kbrequest:restoretextmode -r /var/tmp/restoretext.regs
and run:
restoretextmode -w /var/tmp/restoretext.regs
Then you can press that key combination to restore text mode after an svgalib
app, or now X, has messed it up. On a multi-user system /var/tmp might not be
a good choice for security though.
greg
--
To UNSUBSCRIBE, email to debian-devel-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Reply to: