Sounds like X is dying on vt switch.
I guess so.
I assume this doesn't happen when xscreensaver isn't running?
Indeed.
If X is indeed crashing, can you attach your X log after the crash?
(should be /var/log/Xorg.0.log, or /var/log/Xorg.0.log.old after X has
been restarted)
In the interests
reassign 445104 xserver-xorg-core
severity 445104 important
thanks
On Thu, Oct 4, 2007 at 11:01:47 +0200, Edward Welbourne wrote:
Sounds like X is dying on vt switch.
I guess so.
I assume this doesn't happen when xscreensaver isn't running?
Indeed.
If X is indeed crashing, can you
Thanks, I'm reassigning this bug to the X server. The complete log and
your xorg.conf would be useful.
OK.
file src=/var/log/Xorg.0.log.old
X Window System Version 1.3.0
Release Date: 19 April 2007
X Protocol Version 11, Revision 0, Release 1.3
Build Operating System: Linux Debian (xorg-server
reassign 445104 xserver-xorg-video-intel
forcemerge 431373 445104
thank you
Edward Welbourne wrote:
0: /usr/bin/X(xf86SigHandler+0x81) [0x80c8631]
1: /lib/i686/cmov/libc.so.6 [0xb7e0b898]
2: /usr/bin/X [0x80f9895]
3: /usr/bin/X [0x80fa30a]
4: /usr/bin/X(xf86_reload_cursors+0xbd)
Package: xscreensaver
Version: 5.03-2
Severity: critical
Justification: causes serious data loss
Ever since switching to a Dell flat-screen (2007FPb - I was previously
using a CRT) I've experienced a problem where:
* I lock my X session,
* I switch to a virtual console (Ctrl-Alt-F1, etc.),
On Wed, Oct 3, 2007 at 10:58:12 +0200, Edward Welbourne wrote:
My .xsession-errors ends in: quote
X connection to :0.0 broken (explicit kill or server shutdown).
Gdk-ERROR **: Fatal IO error 104 (Connection reset by peer) on X server :0.0.
X connection to :0.0 broken (explicit kill or
6 matches
Mail list logo
