Re: X11 just froze, and /var/log/syslog (dmesg)'s output seems to mean something

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Camaleón writes: > On Tue, 18 May 2010 20:08:02 +0200, Merciadri Luca wrote: > >> Camaleón writes: > >>> Just review your "/var/log/Xorg.0.log". If X crashed there must >>> something there :-? >> Nothing really interesting there. Just: >> >> == >> A

Re: X11 just froze, and /var/log/syslog (dmesg)'s output seems to mean something

On Tue, 18 May 2010 20:08:02 +0200, Merciadri Luca wrote: > Camaleón writes: >> Just review your "/var/log/Xorg.0.log". If X crashed there must >> something there :-? > Nothing really interesting there. Just: > > == > AUDIT: Tue May 18 18:01:04 2010: 3716 X: client 33 rejected from local > host

Re: X11 just froze, and /var/log/syslog (dmesg)'s output seems to mean something

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Camaleón writes: > On Tue, 18 May 2010 18:08:24 +0200, Merciadri Luca wrote: > >> I realized that my computer (this one, Debian Lenny, w. k. >> 2.6.26-2-686-bigmem) was frozen. I tried escaping from the screensaver, >> but nothing worked, except laun

Re: X11 just froze, and /var/log/syslog (dmesg)'s output seems to mean something

On Tue, 18 May 2010 18:08:24 +0200, Merciadri Luca wrote: > I realized that my computer (this one, Debian Lenny, w. k. > 2.6.26-2-686-bigmem) was frozen. I tried escaping from the screensaver, > but nothing worked, except launching another tty, and restarting gdm. > Here is the interesting output

X11 just froze, and /var/log/syslog (dmesg)'s output seems to mean something

Hi, I realized that my computer (this one, Debian Lenny, w. k. 2.6.26-2-686-bigmem) was frozen. I tried escaping from the screensaver, but nothing worked, except launching another tty, and restarting gdm. Here is the interesting output I obtained by looking at /var/log/syslog and dmesg: == [24892