Bug#295300: gdm: Same error when entering sleep (echo "mem" > /sys/power/state)

2007-07-19 Thread Brice Goglin
reassign 295300 xserver-xorg-core forcemerge 389576 295300 thank you > Backtrace: > 0: /usr/bin/X(xf86SigHandler+0x81) [0x80c8591] > 1: /lib/libc.so.6 [0xb7df2218] > 2: /usr/lib/xorg/modules/extensions//libGLcore.so(XMesaResizeBuffers+0x29) > [0xaf970179] > 3: /usr/lib/xorg/modules/extensions//

Processed: Re: Bug#295300: gdm: Same error when entering sleep (echo "mem" > /sys/power/state)

2007-07-19 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]: > reassign 295300 xserver-xorg-core Bug#295300: X server crash when triggering software suspend Bug reassigned from package `xserver-xorg-video-intel' to `xserver-xorg-core'. > forcemerge 389576 295300 Bug#389576: xserver-xorg-core: crash in XMesaResizeB

Bug#295300: gdm: Same error when entering sleep (echo "mem" > /sys/power/state)

2007-07-17 Thread Julien Cristau
On Mon, Jul 16, 2007 at 18:13:39 -0400, Jamie McClelland wrote: > When I put my system to sleep. It causes gdm to restart and causes the bash > script that puts the system to sleep to freeze, hence the computer does not go > to sleep, but presents a new gdm login. > What do you do exactly to put

Processed: Re: Bug#295300: gdm: Same error when entering sleep (echo "mem" > /sys/power/state)

2007-07-17 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]: > submitter 295300 [EMAIL PROTECTED] Bug#295300: gdm: gdm_slave_xioerror_handler|: Fatal X error - Restarting :0 Changed Bug submitter from Michel Verdier <[EMAIL PROTECTED]> to [EMAIL PROTECTED] > reassign 295300 xserver-xorg-video-intel Bug#295300: gd

Re: Bug#295300: gdm: Same error when entering sleep (echo "mem" > /sys/power/state)

2007-07-17 Thread Josselin Mouette
submitter 295300 [EMAIL PROTECTED] reassign 295300 xserver-xorg-video-intel retitle 295300 X server crash when triggering software suspend thanks Le mardi 17 juillet 2007 à 10:25 -0400, Jamie McClelland a écrit : > > This is most likely another issue in the X server; this has nothing to > > do wit