Your message dated Wed, 07 Jan 2009 15:02:57 +0100
with message-id <1231336977.2338.10.ca...@radis.liafa.jussieu.fr>
and subject line Re: Bug#495483: Another instance of the DoSwapInterval segfault
has caused the Debian Bug report #495483,
regarding xorg: Google Earth crashes X server
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
495483: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=495483
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: xorg
Version: 1:7.3+15
Severity: normal


Starting google-earth (v4.3.7284.3916, downloaded today) displays a splash 
screen and then crashes X.

Graphics card is: 05:00.0 VGA compatible controller: nVidia Corporation NV44 
[GeForce 6200 LE] (rev a1)

It seems that something wanted to create a backtrace as the word "Backtrace:" 
is the last thing
to be found in /var/log/Xorg.0.log, but that attempt seems to have failed.

I'm willing to investigate further if I get a little guidance.

Kind regards,

Thiemo Nagel

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

Kernel: Linux 2.6.25-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages xorg depends on:
ii  gnome-terminal [x-termi 2.22.3-2         The GNOME 2 terminal emulator appl
ii  konsole [x-terminal-emu 4:3.5.9.dfsg.1-5 X terminal emulator for KDE
ii  libgl1-mesa-glx [libgl1 7.0.3-5          A free implementation of the OpenG
ii  libglu1-mesa            7.0.3-5          The OpenGL utility library (GLU)
ii  x11-apps                7.3+3            X applications
ii  x11-session-utils       7.3+1            X session utilities
ii  x11-utils               7.3+2            X11 utilities
ii  x11-xfs-utils           7.3+1            X font server utilities
ii  x11-xkb-utils           7.4+1            X11 XKB utilities
ii  x11-xserver-utils       7.3+4            X server utilities
ii  xauth                   1:1.0.3-2        X authentication utility
ii  xfonts-100dpi           1:1.0.0-4        100 dpi fonts for X
ii  xfonts-75dpi            1:1.0.0-4        75 dpi fonts for X
ii  xfonts-base             1:1.0.0-5        standard fonts for X
ii  xfonts-scalable         1:1.0.0-6        scalable fonts for X
ii  xfonts-utils            1:7.4+1          X Window System font utility progr
ii  xinit                   1.0.9-2          X server initialisation tool
ii  xkb-data                1.3-2            X Keyboard Extension (XKB) configu
ii  xserver-xorg            1:7.3+15         the X.Org X server
ii  xterm [x-terminal-emula 235-1            X terminal emulator

Versions of packages xorg recommends:
ii  xorg-docs                     1:1.4-2    Miscellaneous documentation for th

xorg suggests no packages.

-- no debconf information



--- End Message ---
--- Begin Message ---
Version: 2:1.4.99.902-1

tag 495483 patch upstream fixed-upstream
kthxbye

On Wed, 2009-01-07 at 13:58 +0100, Hugo Herbelin wrote:
> Hi,
> 
> After further browsing the code, it seems that the problem was in fact
> that the function swapInterval called by DoSwapInterval was not
> initialised. The faulty function is __glXMesaScreenProbe in
> glglxcore.c which initialises all __GLXscreen fields but the
> swapInterval field. It seems to me that __glXMesaScreenProbe should at
> minima set swapInterval to NULL.
> 
> Indeed, after recompilation with the patch below, the gnome
> screensaver does not crash any longer. I would guess this will address
> also the following bug reports:
> 
> https://bugs.launchpad.net/bugs/115609
> http://bugs.debian.org/500887
> 
Thanks for the analysis!
Looks like this is fixed upstream by commit
d7db6dd1a15393e9a30acfe87f7651ca1c9a0d75.  We should probably get that
patch in lenny.

Cheers,
Julien


--- End Message ---

Reply via email to