Undecodable token error ??

Thymox · 11-18-2002, 02:33 PM

Recently... i.e. after I installed Mandy 9.0, I keep getting some rather nasty errors appearing on tty1 and they seem to be causing rather complete crashes!

At first I thought it might have been the This system does not support ACPI error, but I am now getting these and the system still works. However, when I get an Undecodable token \001b (hex) [36l error, X stops completely (although XMMS keeps plaing nicely in the background) and a nice simple <CTRL><ALT><BackSpace> doesn't sort things. Even a <ALT><SysRq><S> (or <U>) doesn't work. The only one that seems to make do anything is <Alt><SysRq><B>... but that doesn't unmount any filesystems, so I'd prefer not to do that, if I can get away with it

Anyway, to conclude:

I'm getting undecodable token errors, and I can't find out what the hell they're all about, and they seem to be bringing my system down fairly completely - what is it, what does it mean, and why am I getting them?

Cheers muchly people!

Thymox · 11-18-2002, 04:26 PM

Ooh... I've just had another, and my system is still up... for the time being. This is now causing me to doubt my initial diagnosis... I'll keep you posted.

Thymox · 11-18-2002, 05:16 PM

OK, perhaps it's not the undecodable token error... but I've got a new one for ya:

Code:

** CRITICAL **: file mozilla.cpp: line 134 (gboolean mozilla_preference_set (const char *, const char *)): assertion `new_value != NULL' failed.
Gnome-Message: res is -1 instead of 4
Gnome-Message: gnome_execute_async_with_env_fds: returning -1

** WARNING **: failed to execute download command.
mcop warning: user defined signal handler found for SIG_PIPE, overriding
GetModeLine - scrn: 0 clock: 175500
GetModeLine - hdsp: 1600 hbeg: 1664 hend: 1856 httl: 2160
              vdsp: 1200 vbeg: 1201 vend: 1204 vttl: 1250 flags: 5
GetModeLine - scrn: 0 clock: 175500
GetModeLine - hdsp: 1600 hbeg: 1664 hend: 1856 httl: 2160
              vdsp: 1200 vbeg: 1201 vend: 1204 vttl: 1250 flags: 5
GetModeLine - scrn: 0 clock: 175500
GetModeLine - hdsp: 1600 hbeg: 1664 hend: 1856 httl: 2160
              vdsp: 1200 vbeg: 1201 vend: 1204 vttl: 1250 flags: 5
GetModeLine - scrn: 0 clock: 175500
GetModeLine - hdsp: 1600 hbeg: 1664 hend: 1856 httl: 2160
              vdsp: 1200 vbeg: 1201 vend: 1204 vttl: 1250 flags: 5

Any thoughts?

Thymox · 11-18-2002, 06:11 PM

And yet more...

I can try to kill it with <Ctrl><C>, upon which I get

Code:

waiting for X server to shut down. The application 'nt' lost its connection to the display :0.0;
most likely the X server was shut down or you killed/destroyed
the application.
.........kdeinit: Fatal IO error: client killed


xinit:  X server slow to shut down, sending KILL signal.

waiting for server to die ...
xinit:  Can't kill server
[gsewell@grants gsewell]$

and all seems fine... untill I try to do anything. Even simply giving the command ls causes the thing to hang! This is really annoying me now, and I'd appreciate any input, no matter how silly you think it might be!

Cheers.