[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#448961: marked as done (mesa-utils: Segmentation fault of glxinfo)

Your message dated Mon, 31 Mar 2008 22:21:16 +0200
with message-id <20080331202114.GA22118@patate.is-a-geek.org>
and subject line Re: Bug#448961: mesa-utils: Segmentation fault of glxinfo
has caused the Debian Bug report #448961,
regarding mesa-utils: Segmentation fault of glxinfo
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 owner@bugs.debian.org
immediately.)


-- 
448961: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=448961
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: mesa-utils
Version: 6.3.2-2.1
Severity: normal

supaplex@armada:~$ glxgears
Error: couldn't get an RGB, Double-buffered visual
supaplex@armada:~$ glxinfo
name of display: :0.0
Error: couldn't find RGB GLX visual

   visual  x  bf lv rg d st colorbuffer ax dp st accumbuffer  ms  cav
 id dep cl sp sz l  ci b ro  r  g  b  a bf th cl  r  g  b  a ns b eat
----------------------------------------------------------------------
Segmentation fault
supaplex@armada:~$ gdb glxinfo
GNU gdb 6.4.90-debian
Copyright (C) 2006 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "i486-linux-gnu"...(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".

(gdb) run
Starting program: /usr/bin/glxinfo
Failed to read a valid object file image from memory.
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
name of display: :0.0
Error: couldn't find RGB GLX visual

   visual  x  bf lv rg d st colorbuffer ax dp st accumbuffer  ms  cav
 id dep cl sp sz l  ci b ro  r  g  b  a bf th cl  r  g  b  a ns b eat
----------------------------------------------------------------------

Program received signal SIGSEGV, Segmentation fault.
0xb7cc2dee in strstr () from /lib/tls/i686/cmov/libc.so.6
(gdb) The program is running.  Exit anyway? (y or n) y
supaplex@armada:~$


-- System Information:
Debian Release: 4.0
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-5-vserver-686
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)

Versions of packages mesa-utils depends on:
ii  freeglut3              2.4.0-5           OpenGL Utility Toolkit
ii  libc6                  2.3.6.ds1-13etch2 GNU C Library: Shared libraries
ii  libgl1-mesa-glx [libgl 6.5.1-0.6         A free implementation of the OpenG
ii  libglu1-mesa [libglu1] 6.5.1-0.6         The OpenGL utility library (GLU)
ii  libx11-6               2:1.0.3-7         X11 client-side library

mesa-utils recommends no packages.

-- no debconf information

--- End Message ---
--- Begin Message --- 
On Fri, Nov  2, 2007 at 21:06:11 +0100, Brice Goglin wrote:

> Are you using the nvidia binary driver? with Xinerama? There are
> multiple nvidia related crashes like this one in Google. If so,
> can you upgrade to the latest nvidia and see whether it helps?
> 
No reply since November, closing this bug.

Cheers,
Julien

--- End Message ---
Reply to: