Bug#496889: gnome-games: sol causes(?) X-server crash and lockup

2008-10-19 Thread Julian Gilbey
On Sun, Sep 21, 2008 at 12:48:42AM +0100, Julian Gilbey wrote:
 Yay!  I managed to catch it!  I installed a local /usr/local/bin/X,
 [...]
 Below is gdb running a backtrace on the core file.  I've saved the
 core in case it's still relevant.

Happened again.  Here's the gdb logs.

euclid:/etc/X11# gdb /usr/bin/Xorg core.crash2
GNU gdb 6.8-debian
Copyright (C) 2008 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type show copying
and show warranty for details.
This GDB was configured as i486-linux-gnu...

warning: Can't read pathname for load map: Input/output error.
Reading symbols from /lib/i686/cmov/libdl.so.2...done.
Loaded symbols for /lib/i686/cmov/libdl.so.2
Reading symbols from /usr/lib/libXfont.so.1...done.
Loaded symbols for /usr/lib/libXfont.so.1
Reading symbols from /usr/lib/libXau.so.6...done.
Loaded symbols for /usr/lib/libXau.so.6
Reading symbols from /usr/lib/libfontenc.so.1...done.
Loaded symbols for /usr/lib/libfontenc.so.1
Reading symbols from /usr/lib/libpixman-1.so.0...done.
Loaded symbols for /usr/lib/libpixman-1.so.0
Reading symbols from /usr/lib/libhal.so.1...done.
Loaded symbols for /usr/lib/libhal.so.1
Reading symbols from /usr/lib/libdbus-1.so.3...done.
Loaded symbols for /usr/lib/libdbus-1.so.3
Reading symbols from /usr/lib/libXdmcp.so.6...done.
Loaded symbols for /usr/lib/libXdmcp.so.6
Reading symbols from /lib/i686/cmov/libm.so.6...done.
Loaded symbols for /lib/i686/cmov/libm.so.6
Reading symbols from /lib/i686/cmov/librt.so.1...done.
Loaded symbols for /lib/i686/cmov/librt.so.1
Reading symbols from /lib/libgcc_s.so.1...done.
Loaded symbols for /lib/libgcc_s.so.1
Reading symbols from /lib/i686/cmov/libc.so.6...done.
Loaded symbols for /lib/i686/cmov/libc.so.6
Reading symbols from /lib/ld-linux.so.2...done.
Loaded symbols for /lib/ld-linux.so.2
Reading symbols from /usr/lib/libfreetype.so.6...done.
Loaded symbols for /usr/lib/libfreetype.so.6
Reading symbols from /usr/lib/libz.so.1...done.
Loaded symbols for /usr/lib/libz.so.1
Reading symbols from /lib/i686/cmov/libpthread.so.0...done.
Loaded symbols for /lib/i686/cmov/libpthread.so.0
Reading symbols from /usr/lib/xorg/modules/libpcidata.so...Reading symbols from 
/usr/lib/debug/usr/lib/xorg/modules/libpcidata.so...done.
done.
Loaded symbols for /usr/lib/xorg/modules//libpcidata.so
Reading symbols from /usr/lib/xorg/modules/extensions/libextmod.so...Reading 
symbols from /usr/lib/debug/usr/lib/xorg/modules/extensions/libextmod.so...done.
done.
Loaded symbols for /usr/lib/xorg/modules/extensions//libextmod.so
Reading symbols from /usr/lib/xorg/modules/extensions/libdbe.so...Reading 
symbols from /usr/lib/debug/usr/lib/xorg/modules/extensions/libdbe.so...done.
done.
Loaded symbols for /usr/lib/xorg/modules/extensions//libdbe.so
Reading symbols from /usr/lib/xorg/modules/extensions/libglx.so...Reading 
symbols from /usr/lib/debug/usr/lib/xorg/modules/extensions/libglx.so...done.
done.
Loaded symbols for /usr/lib/xorg/modules/extensions//libglx.so
Reading symbols from /usr/lib/xorg/modules/fonts/libfreetype.so...Reading 
symbols from /usr/lib/debug/usr/lib/xorg/modules/fonts/libfreetype.so...done.
done.
Loaded symbols for /usr/lib/xorg/modules//fonts/libfreetype.so
Reading symbols from /usr/lib/xorg/modules/extensions/librecord.so...Reading 
symbols from /usr/lib/debug/usr/lib/xorg/modules/extensions/librecord.so...done.
done.
Loaded symbols for /usr/lib/xorg/modules/extensions//librecord.so
Reading symbols from /usr/lib/xorg/modules/extensions/libdri.so...Reading 
symbols from /usr/lib/debug/usr/lib/xorg/modules/extensions/libdri.so...done.
done.
Loaded symbols for /usr/lib/xorg/modules/extensions//libdri.so
Reading symbols from /usr/lib/libdrm.so.2...done.
Loaded symbols for /usr/lib/libdrm.so.2
Reading symbols from /usr/lib/xorg/modules/drivers/intel_drv.so...Reading 
symbols from /usr/lib/debug/usr/lib/xorg/modules/drivers/intel_drv.so...done.
done.
Loaded symbols for /usr/lib/xorg/modules/drivers//intel_drv.so
Reading symbols from /usr/lib/xorg/modules/input/mouse_drv.so...done.
Loaded symbols for /usr/lib/xorg/modules/input//mouse_drv.so
Reading symbols from /usr/lib/xorg/modules/input/kbd_drv.so...done.
Loaded symbols for /usr/lib/xorg/modules/input//kbd_drv.so
Reading symbols from /usr/lib/xorg/modules/libint10.so...Reading symbols from 
/usr/lib/debug/usr/lib/xorg/modules/libint10.so...done.
done.
Loaded symbols for /usr/lib/xorg/modules//libint10.so
Reading symbols from /usr/lib/xorg/modules/libvbe.so...Reading symbols from 
/usr/lib/debug/usr/lib/xorg/modules/libvbe.so...done.
done.
Loaded symbols for /usr/lib/xorg/modules//libvbe.so
Reading symbols from /usr/lib/xorg/modules/libvgahw.so...Reading symbols from 
/usr/lib/debug/usr/lib/xorg/modules/libvgahw.so...done.
done.
Loaded symbols for /usr/lib/xorg/modules//libvgahw.so
Reading symbols 

Bug#496889: gnome-games: sol causes(?) X-server crash and lockup

2008-09-20 Thread Julian Gilbey
On Fri, Aug 29, 2008 at 06:55:56PM +0200, Brice Goglin wrote:
  So all I have is the core dump of the locked up server from when it
  tried restarting.
 [...]
 Yes, we need a backtrace of the crash. You can get one by:
 1) looking at the end of Xorg.0.log (or Xorg.0.log.old if X already
 restarted)
 2) running gdb on your core
 3) attaching gdb to a running X from another machine through ssh before
 the crash occurs.
 
 The best would be 2) or 3) after installing xserver-xorg-core-dbg.

Yay!  I managed to catch it!  I installed a local /usr/local/bin/X,
calling it from /etc/gdm/gdm.conf, which calls X with -core and
rotates the core files using logrotate before starting X.  gdm tried
restarting X three times (hence three later core files, which only
have X failing to start because of the lockup), but I got the core
file where it crashed!

Below is gdb running a backtrace on the core file.  I've saved the
core in case it's still relevant.

Hopefully this will be of some help in tracking down this elusive
bug.

   Julian

euclid:~# gdb /usr/bin/Xorg /tmp/core.3
GNU gdb 6.8-debian
Copyright (C) 2008 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type show copying
and show warranty for details.
This GDB was configured as i486-linux-gnu...

warning: Can't read pathname for load map: Input/output error.
Reading symbols from /lib/i686/cmov/libdl.so.2...done.
Loaded symbols for /lib/i686/cmov/libdl.so.2
Reading symbols from /usr/lib/libXfont.so.1...done.
Loaded symbols for /usr/lib/libXfont.so.1
Reading symbols from /usr/lib/libXau.so.6...done.
Loaded symbols for /usr/lib/libXau.so.6
Reading symbols from /usr/lib/libfontenc.so.1...done.
Loaded symbols for /usr/lib/libfontenc.so.1
Reading symbols from /usr/lib/libpixman-1.so.0...done.
Loaded symbols for /usr/lib/libpixman-1.so.0
Reading symbols from /usr/lib/libhal.so.1...done.
Loaded symbols for /usr/lib/libhal.so.1
Reading symbols from /usr/lib/libdbus-1.so.3...done.
Loaded symbols for /usr/lib/libdbus-1.so.3
Reading symbols from /usr/lib/libXdmcp.so.6...done.
Loaded symbols for /usr/lib/libXdmcp.so.6
Reading symbols from /lib/i686/cmov/libm.so.6...done.
Loaded symbols for /lib/i686/cmov/libm.so.6
Reading symbols from /lib/i686/cmov/librt.so.1...done.
Loaded symbols for /lib/i686/cmov/librt.so.1
Reading symbols from /lib/libgcc_s.so.1...done.
Loaded symbols for /lib/libgcc_s.so.1
Reading symbols from /lib/i686/cmov/libc.so.6...done.
Loaded symbols for /lib/i686/cmov/libc.so.6
Reading symbols from /lib/ld-linux.so.2...done.
Loaded symbols for /lib/ld-linux.so.2
Reading symbols from /usr/lib/libfreetype.so.6...done.
Loaded symbols for /usr/lib/libfreetype.so.6
Reading symbols from /usr/lib/libz.so.1...done.
Loaded symbols for /usr/lib/libz.so.1
Reading symbols from /lib/i686/cmov/libpthread.so.0...done.
Loaded symbols for /lib/i686/cmov/libpthread.so.0
Reading symbols from /usr/lib/xorg/modules/libpcidata.so...Reading symbols from 
/usr/lib/debug/usr/lib/xorg/modules/libpcidata.so...done.
done.
Loaded symbols for /usr/lib/xorg/modules//libpcidata.so
Reading symbols from /usr/lib/xorg/modules/extensions/libextmod.so...Reading 
symbols from /usr/lib/debug/usr/lib/xorg/modules/extensions/libextmod.so...done.
done.
Loaded symbols for /usr/lib/xorg/modules/extensions//libextmod.so
Reading symbols from /usr/lib/xorg/modules/extensions/libdbe.so...Reading 
symbols from /usr/lib/debug/usr/lib/xorg/modules/extensions/libdbe.so...done.
done.
Loaded symbols for /usr/lib/xorg/modules/extensions//libdbe.so
Reading symbols from /usr/lib/xorg/modules/extensions/libglx.so...Reading 
symbols from /usr/lib/debug/usr/lib/xorg/modules/extensions/libglx.so...done.
done.
Loaded symbols for /usr/lib/xorg/modules/extensions//libglx.so
Reading symbols from /usr/lib/xorg/modules/fonts/libfreetype.so...Reading 
symbols from /usr/lib/debug/usr/lib/xorg/modules/fonts/libfreetype.so...done.
done.
Loaded symbols for /usr/lib/xorg/modules//fonts/libfreetype.so
Reading symbols from /usr/lib/xorg/modules/extensions/librecord.so...Reading 
symbols from /usr/lib/debug/usr/lib/xorg/modules/extensions/librecord.so...done.
done.
Loaded symbols for /usr/lib/xorg/modules/extensions//librecord.so
Reading symbols from /usr/lib/xorg/modules/extensions/libdri.so...Reading 
symbols from /usr/lib/debug/usr/lib/xorg/modules/extensions/libdri.so...done.
done.
Loaded symbols for /usr/lib/xorg/modules/extensions//libdri.so
Reading symbols from /usr/lib/libdrm.so.2...done.
Loaded symbols for /usr/lib/libdrm.so.2
Reading symbols from /usr/lib/xorg/modules/drivers/intel_drv.so...Reading 
symbols from /usr/lib/debug/usr/lib/xorg/modules/drivers/intel_drv.so...done.
done.
Loaded symbols for /usr/lib/xorg/modules/drivers//intel_drv.so
Reading symbols from /usr/lib/xorg/modules/input/mouse_drv.so...done.
Loaded symbols for 

Bug#496889: gnome-games: sol causes(?) X-server crash and lockup

2008-08-31 Thread Julian Gilbey
On Fri, Aug 29, 2008 at 06:55:56PM +0200, Brice Goglin wrote:
 Josselin Mouette wrote:
  Darn, darn, darn.  It crashed again, but gdm then tried restarting the
  X server.
 
  So all I have is the core dump of the locked up server from when it
  tried restarting.
  
 
  Such a dump should be useful to track down the bug. I’m reassigning the
  bug to X so that they can ask you the information they need.

 
 Yes, we need a backtrace of the crash. You can get one by:
 1) looking at the end of Xorg.0.log (or Xorg.0.log.old if X already
 restarted)
 2) running gdb on your core
 3) attaching gdb to a running X from another machine through ssh before
 the crash occurs.
 
 The best would be 2) or 3) after installing xserver-xorg-core-dbg.

The problem is that gdm tries restarting X at least twice after the
crash, after both of which X failed to start because it was locked
up.  So the original crash info and core file have been overwritten.
Oops.  I've just written a wrapper round X to rotate the core files
before running X, so hopefully the next time there is a crash, I'll be
able to pass on this information.

   Julian



--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#496889: gnome-games: sol causes(?) X-server crash and lockup

2008-08-31 Thread Brice Goglin
Julian Gilbey wrote:
 The problem is that gdm tries restarting X at least twice after the
 crash, after both of which X failed to start because it was locked
 up.  So the original crash info and core file have been overwritten.
 Oops.  I've just written a wrapper round X to rotate the core files
 before running X, so hopefully the next time there is a crash, I'll be
 able to pass on this information.
   

Or just start X with 'startx' from a VT console after disabling gdm.

Brice




-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#496889: gnome-games: sol causes(?) X-server crash and lockup

2008-08-29 Thread Josselin Mouette
reassign 496889 xserver-xorg-core
thanks

Le vendredi 29 août 2008 à 01:11 +0100, Julian Gilbey a écrit :
 On Thu, Aug 28, 2008 at 12:30:02PM +0200, Josselin Mouette wrote:
  Le jeudi 28 août 2008 à 10:46 +0100, Julian Gilbey a écrit :
   I have had a few X server crashes recently, and following the crash,
   the X server then reports that it can't restart as there is a lockup.
   The only way of restarting X then seems to be to reboot the machine,
   which is a little extreme.
   
   The only common factor among all of these is that I was playing
   aisleriot at the time.  I have no idea at all whether this is
   causitive or coincidental, and also no clue how to test this.
  
  A X server crash is a bug in the X server, whatever is the application
  that causes it.
  
  What would be interesting is the X server log in /var/log/Xorg.0.log*
  after the crash, or, even better, a stack trace of the X server with
  debugging symbols installed.
 
 Darn, darn, darn.  It crashed again, but gdm then tried restarting the
 X server.
 
 So all I have is the core dump of the locked up server from when it
 tried restarting.

Such a dump should be useful to track down the bug. I’m reassigning the
bug to X so that they can ask you the information they need.

Cheers,
-- 
 .''`.
: :' :  We are debian.org. Lower your prices, surrender your code.
`. `'   We will add your hardware and software distinctiveness to
  `-our own. Resistance is futile.


signature.asc
Description: Ceci est une partie de message	numériquement signée


Bug#496889: gnome-games: sol causes(?) X-server crash and lockup

2008-08-29 Thread Brice Goglin
Josselin Mouette wrote:
 Darn, darn, darn.  It crashed again, but gdm then tried restarting the
 X server.

 So all I have is the core dump of the locked up server from when it
 tried restarting.
 

 Such a dump should be useful to track down the bug. I’m reassigning the
 bug to X so that they can ask you the information they need.
   

Yes, we need a backtrace of the crash. You can get one by:
1) looking at the end of Xorg.0.log (or Xorg.0.log.old if X already
restarted)
2) running gdb on your core
3) attaching gdb to a running X from another machine through ssh before
the crash occurs.

The best would be 2) or 3) after installing xserver-xorg-core-dbg.

Brice




--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#496889: gnome-games: sol causes(?) X-server crash and lockup

2008-08-28 Thread Julian Gilbey
Package: gnome-games
Version: 1:2.22.3-1
Severity: important

[If I were able to confirm that sol really does cause lockups, then
this would be Severity: grave]

I have had a few X server crashes recently, and following the crash,
the X server then reports that it can't restart as there is a lockup.
The only way of restarting X then seems to be to reboot the machine,
which is a little extreme.

The only common factor among all of these is that I was playing
aisleriot at the time.  I have no idea at all whether this is
causitive or coincidental, and also no clue how to test this.

Bemused,

   Julian

-- System Information:
Debian Release: lenny/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)

Kernel: Linux 2.6.25-2-686 (SMP w/1 CPU core)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages gnome-games depends on:
ii  gnome-games-data1:2.22.3-1   data files for the GNOME games
ii  gnuchess5.07-4.1 Plays a game of chess, either agai
ii  guile-1.8-libs  1.8.4+1-2Main Guile libraries
ii  libatk1.0-0 1.22.0-1 The ATK accessibility toolkit
ii  libc6   2.7-13   GNU C Library: Shared libraries
ii  libcairo2   1.6.4-6  The Cairo 2D vector graphics libra
ii  libgcc1 1:4.3.1-2GCC support library
ii  libgconf2-4 2.22.0-1 GNOME configuration database syste
ii  libggz2 0.0.14.1-1   GGZ Gaming Zone: common utilities 
ii  libggzcore9 0.0.14.1-1   GGZ Gaming Zone: core client front
ii  libggzmod4  0.0.14.1-1   GGZ Gaming Zone: game frontend lib
ii  libglib2.0-02.16.4-2 The GLib library of C routines
ii  libgnome2-0 2.20.1.1-1   The GNOME 2 library - runtime file
ii  libgnomeui-02.20.1.1-1   The GNOME 2 libraries (User Interf
ii  libgnomevfs2-0  1:2.22.0-4   GNOME Virtual File System (runtime
ii  libgstreamer0.10-0  0.10.19-3Core GStreamer libraries and eleme
ii  libgtk2.0-0 2.12.11-3The GTK+ graphical user interface 
ii  libpango1.0-0   1.20.5-1 Layout and rendering of internatio
ii  librsvg2-2  2.22.2-2 SAX-based renderer library for SVG
ii  librsvg2-common 2.22.2-2 SAX-based renderer library for SVG
ii  libstdc++6  4.3.1-2  The GNU Standard C++ Library v3
ii  libx11-62:1.1.4-2X11 client-side library
ii  libxml2 2.6.32.dfsg-2+lenny1 GNOME XML library
ii  python  2.5.2-2  An interactive high-level object-o
ii  python-gnome2   2.22.0-1 Python bindings for the GNOME desk
ii  python-gnome2-deskt 2.22.0-2 Python bindings for the GNOME desk
ii  python-gtk2 2.12.1-6 Python bindings for the GTK+ widge
ii  zlib1g  1:1.2.3.3.dfsg-12compression library - runtime

Versions of packages gnome-games recommends:
ii  gnome-games-extra-data2.22.0-1   games for the GNOME desktop (extra
ii  python-gtkglext1  1.1.0-3.1  GtkGLext python bindings
ii  python-opengl 3.0.0~b3-1 Python bindings to OpenGL

Versions of packages gnome-games suggests:
pn  gnome-hearts  none (no description available)

-- no debconf information



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#496889: gnome-games: sol causes(?) X-server crash and lockup

2008-08-28 Thread Josselin Mouette
Le jeudi 28 août 2008 à 10:46 +0100, Julian Gilbey a écrit :
 Package: gnome-games
 Version: 1:2.22.3-1
 Severity: important
 
 [If I were able to confirm that sol really does cause lockups, then
 this would be Severity: grave]
 
 I have had a few X server crashes recently, and following the crash,
 the X server then reports that it can't restart as there is a lockup.
 The only way of restarting X then seems to be to reboot the machine,
 which is a little extreme.
 
 The only common factor among all of these is that I was playing
 aisleriot at the time.  I have no idea at all whether this is
 causitive or coincidental, and also no clue how to test this.

A X server crash is a bug in the X server, whatever is the application
that causes it.

What would be interesting is the X server log in /var/log/Xorg.0.log*
after the crash, or, even better, a stack trace of the X server with
debugging symbols installed.

Cheers,
-- 
 .''`.
: :' :  We are debian.org. Lower your prices, surrender your code.
`. `'   We will add your hardware and software distinctiveness to
  `-our own. Resistance is futile.


signature.asc
Description: Ceci est une partie de message	numériquement signée


Bug#496889: gnome-games: sol causes(?) X-server crash and lockup

2008-08-28 Thread Julian Gilbey
On Thu, Aug 28, 2008 at 12:30:02PM +0200, Josselin Mouette wrote:
 Le jeudi 28 août 2008 à 10:46 +0100, Julian Gilbey a écrit :
  Package: gnome-games
  Version: 1:2.22.3-1
  Severity: important
  
  [If I were able to confirm that sol really does cause lockups, then
  this would be Severity: grave]
  
  I have had a few X server crashes recently, and following the crash,
  the X server then reports that it can't restart as there is a lockup.
  The only way of restarting X then seems to be to reboot the machine,
  which is a little extreme.
  
  The only common factor among all of these is that I was playing
  aisleriot at the time.  I have no idea at all whether this is
  causitive or coincidental, and also no clue how to test this.
 
 A X server crash is a bug in the X server, whatever is the application
 that causes it.
 
 What would be interesting is the X server log in /var/log/Xorg.0.log*
 after the crash, or, even better, a stack trace of the X server with
 debugging symbols installed.

Darn, darn, darn.  It crashed again, but gdm then tried restarting the
X server.

So all I have is the core dump of the locked up server from when it
tried restarting.

   Julian



--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]