glxinfo crashed with SIGSEGV in __libc_start_main()

StacktraceTop:main (argc=0, argv=0xbffa6a54) at glxinfo.c:971

I'm experiencing this on a Samsung Q45 laptop with intel GMA945 chipset. Intrepid
with all updates installed.

Marking as confirmed, occurs for me when trying to enable compiz on a 2nd gen macbook so I guess this doesn't just affect nvidia.

I have this with intel GMA950.

Same issue with Intel 4500MHD.

I am having Intel GMA950 and having the same problem.

I turned on compiz with Compiz simple effects and then after the restart this bug came by.

I am with a Intel 945GM* and the system is updated as of today.

R.

Graphic card nvidia 8600 GT
architecture x86_64

I got the same crash when starting the computer for the first time since upgrading from Hardy to Intrepid. It happened when I tried to enable Compiz desktop effects (medium level). Because of this enabling desktop effects doesn't seem to work.

Distro: Intrepid
GFX card: Ati Radeon 9600
Driver: ati

Same for me
Distro: Intrepid
00:02.0 VGA compatible controller: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (rev 03)

I don't know if this is relevant but I installed Kubuntu Alpha 5 fresh and this worked fine. When I went to dist-upgrade it wanted to install mesa-utils as a dependency of compiz-wrapper, which coincides with the time I started having this problem before.

+1
Distro: Intrepid
00:02.0 VGA compatible controller: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (rev 0c)
00:02.1 Display controller: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (rev 0c)

was Just looking to change my theme from the default aftyer this mornings partial-upgrade Sep 11,08 and got this glxinfo error.

lspci:
00:02.0 VGA compatible controller: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (rev 03)
00:02.1 Display controller: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (rev 03)

Same crash on Interpid when trying to enable desktop effects.

00:02.0 VGA compatible controller: Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller (rev 03)

I hope it'll be helpfull
I install mesa-utils-dbgsym
I take this file

and this

Crashed on me

crash on Interpid x86-64 after trying to reload compiz desktop effects.

Bug appears on:
Intrepid x86-64
Nvidia 8600gts

For me it'sfix with tips in:
https://bugs.launchpad.net/ubuntu/+source/mesa-utils/+bug/269405

duplicate of 269405 ?

ld

ld:

They look like separate bugs to me. This one crashes with a SEGV, the other is just GLX missing.

I had the problem (glxinfo crashed, couldn't get any 3d app to run). I have an intel 945 graphics, and the nvidia driver was installed (I saw it being installed during an upgrade a few weeks ago). I followed ld's link, removed nvidia, ran dexconf and all came back to normal.

ld:
You're right. Fixed it for me too!
I removed xserver-xorg-video-nv.
Installed envyng-core.
In text mode: envyng -t
and with that install any nvidia driver (I have an nvidia card), it didn't matter if it was the correct one)
then with envyng -t
restart the x-server.
After that ubuntu was able to find the right hardware and install the correct nvidia driver. (Before it didn't do that, I had to do it manually).
Now everything works again.
@Jacob: yeah they're different, but the same fix worked for me.

Maybe the problem occures with xserver-xorg-video-nv

Happens to me everytime I login to gnome, and it falls back to metacity.

01:00.0 VGA compatible controller: ATI Technologies Inc Radeon Mobility M7 LW [Radeon Mobility 7500]

Fixed for me with:

1) removed nvidia-*,
2) ran dexconf and all came back to normal

ctrl+alt+backspace

But I do not have nvidia? I have ATI Radeon graphics.

LB

Antono Vasiljev wrote:
> Fixed for me with:
>
> 1) removed nvidia-*,
> 2) ran dexconf and all came back to normal
>
> ctrl+alt+backspace
>
>

--
Lynn Bradford

"Right is right, even if everyone is against it; wrong is wrong, even if everyone is for it." Wm. Penn

I just experienced this crash..

Motherboard FIC AU31 (Nvidia NForce2 Chipset), Athlon XP 2400+, 1Gb Ram, ATI Radeon 9200SE, 64Mb

On Sun, 2008-09-21 at 01:35 +0000, Dawg wrote:
> But I do not have nvidia? I have ATI Radeon graphics.

I have Intel. But it's solved my problem. Koz nvidia kernel module was a
problem for all of us...

> LB
>
> Antono Vasiljev wrote:
> > Fixed for me with:
> >
> > 1) removed nvidia-*,
> > 2) ran dexconf and all came back to normal
> >
> > ctrl+alt+backspace
> >
> >
>
> --
> Lynn Bradford
>
> "Right is right, even if everyone is against it; wrong is wrong, even
> if everyone is for it." Wm. Penn
>

Hmm...OK. Bear with me: I'm a newbie, so how do I go about all of
this? What commands do I use?

LB

Antono Vasiljev wrote:
> On Sun, 2008-09-21 at 01:35 +0000, Dawg wrote:
>
>> But I do not have nvidia? I have ATI Radeon graphics.
>>
>
> I have Intel. But it's solved my problem. Koz nvidia kernel module was a
> problem for all of us...
>
>
>> LB
>>
>> Antono Vasiljev wrote:
>>
>>> Fixed for me with:
>>>
>>> 1) removed nvidia-*,
>>> 2) ran dexconf and all came back to normal
>>>
>>> ctrl+alt+backspace
>>>
>>>
>>>
>> --
>> Lynn Bradford
>>
>> "Right is right, even if everyone is against it; wrong is wrong, even
>> if everyone is for it." Wm. Penn
>>
>>
>
>

--
Lynn Bradford

"Right is right, even if everyone is against it; wrong is wrong, even if everyone is for it." Wm. Penn

Solved for me using EnvyNG (http://albertomilone.com/nvidia_scripts1.html): Install with
sudo apt-get install envyng-gtk
or
sudo apt-get install envyng-qt

On Mon, 2008-09-22 at 23:26 +0000, Dawg wrote:
> Hmm...OK. Bear with me: I'm a newbie, so how do I go about all of
> this? What commands do I use?

run synaptic package manager
ctrl+f nvidia<enter>
mark all nvidia packages for deletion
alt+f2
type: sudo dexconf
and chekbox run in terminal

that's all :)

> LB
>
> Antono Vasiljev wrote:
> > On Sun, 2008-09-21 at 01:35 +0000, Dawg wrote:
> >
> >> But I do not have nvidia? I have ATI Radeon graphics.
> >>
> >
> > I have Intel. But it's solved my problem. Koz nvidia kernel module was a
> > problem for all of us...
> >
> >
> >> LB
> >>
> >> Antono Vasiljev wrote:
> >>
> >>> Fixed for me with:
> >>>
> >>> 1) removed nvidia-*,
> >>> 2) ran dexconf and all came back to normal
> >>>
> >>> ctrl+alt+backspace
> >>>
> >>>
> >>>
> >> --
> >> Lynn Bradford
> >>
> >> "Right is right, even if everyone is against it; wrong is wrong, even
> >> if everyone is for it." Wm. Penn
> >>
> >>
> >
> >
>
> --
> Lynn Bradford
>
> "Right is right, even if everyone is against it; wrong is wrong, even
> if everyone is for it." Wm. Penn
>

ATI hd3200,fglrx can,t work

acer aspire one with 8 gig ssd, also have 16 gig and 32 gig sd cards in it, Ubuntu installed to 32 gig patriot axporter flash drive as a persistant live

и чо?

This should be fixed in karmic now. Proposed debdiff to backport the fix included in mesa 7.4.1 to jaunty is attached. debdiff was made against the current 7.4-0ubuntu3.1.

Original commit where the fix was made:
http://cgit.freedesktop.org/mesa/mesa/commit/?h=mesa_7_4_branch&id=d2f67910629d7f9b00ba127f2e869f02a72306d2

Some more info on the fix:
http://www.nabble.com/-PATCH--glx:-fix-NULL-pointer-dereference-in-glXGetFBConfigs-if-GLX-is-not-loaded.-td23009317.html

PPA containing the full package incase anyone wishes to test it out, please report your findings here if you do.
https://edge.launchpad.net/~sarvatt/+archive/bugs

Updated debdiff containing the appropriate bug closing statements in the changelog.

mesa (7.4-0ubuntu3.2) jaunty-proposed; urgency=low

  * Add 107_glxinfo_segfault.patch. Adds a null pointer check in
    glXGetFBConfigs(), which fixes segfaults in glxinfo most commonly
    seen when nvidia binary drivers are present. (LP: #256021, #257600)

 -- Robert Hooker (Sarvatt) <email address hidden> Wed, 24 Jun 2009 21:40:45 -0400

Fix for this is in karmic, we'll focus on the SRU for jaunty...

I've reviewed the patch and sponsored the upload to jaunty. I agree this looks like an important SRU given the huge number of dupe bugs, and especially given how trivial the fix is give it my +1 for inclusion in Jaunty.

Accepted mesa into jaunty-proposed, the package will build now and be available in a few hours. Please test and give feedback here. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you in advance!

It's been a couple months since this was put into -proposed... probably time to move it to -updates so we can proceed with other mesa fixes. This is a pretty clearly correct null pointer deref patch that really doesn't need so much testing.

This bug was fixed in the package mesa - 7.4-0ubuntu3.2

---------------
mesa (7.4-0ubuntu3.2) jaunty-proposed; urgency=low

  * Add 107_glxinfo_segfault.patch. Adds a null pointer check in
    glXGetFBConfigs(), which fixes segfaults in glxinfo most commonly
    seen when nvidia binary drivers are present. (LP: #256021, #257600)

 -- Robert Hooker (Sarvatt) <email address hidden> Wed, 24 Jun 2009 21:40:45 -0400

I seem to have encountered this in Lucid beta 1. Is it supposed to be fixed for Lucid?

This doesn't affect me if I remove the NVidia drivers (I use Intel graphics, so I don't need them.)

Why did you have the nvidia drivers installed, then? Barring a bug in jockey, these drivers should not have been automatically installed for you.

I have Intel also and nvidia packages get automatically installed for me as
well

On Sat, Mar 20, 2010 at 11:08 PM, Steve Langasek <
<email address hidden>> wrote:

> Why did you have the nvidia drivers installed, then? Barring a bug in
> jockey, these drivers should not have been automatically installed for
> you.
>
> --
> glxinfo crashed with SIGSEGV in __libc_start_main()
> https://bugs.launchpad.net/bugs/256021
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in “mesa” package in Ubuntu: Fix Released
> Status in “mesa” source package in Jaunty: Fix Released
> Status in “mesa” source package in Karmic: Fix Released
>
> Bug description:
> [Impact]
>
> Fixes segmentation faults in glXGetFBConfigs() that happen frequently when
> the nvidia binary drivers are present on the system (even if they are not in
> use) by adding a null pointer check. While the SEGV seems innocuous since it
> only happens with glxinfo, quite a few essential programs such as compiz use
> glxinfo to detect GL capabilities and this causes problems. This is fixed in
> Karmic which as of this time has mesa 7.4.1, but the issue still stands in
> jaunty's 7.4.
>
> [Symptoms]
> Segfaults in glxinfo. glxinfo reporting Xlib: extension "GLX" missing on
> display.
>
> [Patch]
> http://launchpadlibrarian.net/28340399/mesa_7.4-0ubuntu3.2.debdiff
>
> [Test Case]
> In an affected system (such as one with nvidia drivers loaded)
> 1. Run glxinfo
> 2. Errors with a segfault
> 3. Attempt to start compiz
> 4. Fails to start because it can't run glxinfo
>
> [Regression Potential]
> Essentially none. It simply adds a null pointer check right before
> dereferencing it.
> This fix has been tested in Karmic as well as upstream for some time, and
> was included in the 7.4.1 bugfix release.
>
> UPDATE:Oct 8 2008. installed daily updates ( 2.6.27-6-generic ) and still
> getting this same glxinfo error on boot
>
>
> ------------------------------------------------------------------------------------------------------------------------------------
>
> I was running PlayOnLinux and tried to install 3d acceleration from there
> when glxinfo crashed.
>
> Description: Ubuntu intrepid (development branch)
> Release: 8.10
>
> mesa version : 7.1~rc3-1ubuntu2 (intrepid)
>
> ProblemType: Crash
> Architecture: i386
> DistroRelease: Ubuntu 8.10
> ExecutablePath: /usr/bin/glxinfo
> NonfreeKernelModules: nvidia
> Package: mesa-utils 7.1~rc3-1ubuntu2
> ProcAttrCurrent: unconfined
> ProcCmdline: glxinfo
> ProcEnviron:
> SHELL=/bin/bash
>
> PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
> LANG=en_US.UTF-8
> Signal: 11
> SourcePackage: mesa
> Stacktrace:
> #0 0x0804ad66 in ?? ()
> #1 0xb7d66685 in __libc_start_main () from /lib/tls/i686/cmov/libc.so.6
> #2 0x08048e81 in ?? ()
> StacktraceTop:
> ?? ()
> __libc_start_main () from /lib/tls/i686/cmov/libc.so.6
> ?? ()
> ThreadStacktrace:
> .
> Thread 1 (process 7142):
> #0 0x0804ad66 in ?? ()
> #1 0xb7d66685 in __libc_start_main () from /lib/tls/i686/cmov/libc.so.6
> #2 0x08048e81 in ?? ()
> Title: glxinfo crashed with SIGSEGV in __libc_start_main()...

Installed how? Are you being presented with a dialogue about restricted drivers being available for your hardware?

If so, please file a bug report against the jockey package.

I believe it was yesterday morning, or maybe this morning I did a aptitude
upgrade and 2 or 3 nvidia packages were installed. I don't have any nvidia
hardware, they do not seem to cause any problems for me but I removed them
after installing.

On Sat, Mar 20, 2010 at 11:38 PM, Steve Langasek <
<email address hidden>> wrote:

> Installed how? Are you being presented with a dialogue about restricted
> drivers being available for your hardware?
>
> If so, please file a bug report against the jockey package.
>
> --
> glxinfo crashed with SIGSEGV in __libc_start_main()
> https://bugs.launchpad.net/bugs/256021
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in “mesa” package in Ubuntu: Fix Released
> Status in “mesa” source package in Jaunty: Fix Released
> Status in “mesa” source package in Karmic: Fix Released
>
> Bug description:
> [Impact]
>
> Fixes segmentation faults in glXGetFBConfigs() that happen frequently when
> the nvidia binary drivers are present on the system (even if they are not in
> use) by adding a null pointer check. While the SEGV seems innocuous since it
> only happens with glxinfo, quite a few essential programs such as compiz use
> glxinfo to detect GL capabilities and this causes problems. This is fixed in
> Karmic which as of this time has mesa 7.4.1, but the issue still stands in
> jaunty's 7.4.
>
> [Symptoms]
> Segfaults in glxinfo. glxinfo reporting Xlib: extension "GLX" missing on
> display.
>
> [Patch]
> http://launchpadlibrarian.net/28340399/mesa_7.4-0ubuntu3.2.debdiff
>
> [Test Case]
> In an affected system (such as one with nvidia drivers loaded)
> 1. Run glxinfo
> 2. Errors with a segfault
> 3. Attempt to start compiz
> 4. Fails to start because it can't run glxinfo
>
> [Regression Potential]
> Essentially none. It simply adds a null pointer check right before
> dereferencing it.
> This fix has been tested in Karmic as well as upstream for some time, and
> was included in the 7.4.1 bugfix release.
>
> UPDATE:Oct 8 2008. installed daily updates ( 2.6.27-6-generic ) and still
> getting this same glxinfo error on boot
>
>
> ------------------------------------------------------------------------------------------------------------------------------------
>
> I was running PlayOnLinux and tried to install 3d acceleration from there
> when glxinfo crashed.
>
> Description: Ubuntu intrepid (development branch)
> Release: 8.10
>
> mesa version : 7.1~rc3-1ubuntu2 (intrepid)
>
> ProblemType: Crash
> Architecture: i386
> DistroRelease: Ubuntu 8.10
> ExecutablePath: /usr/bin/glxinfo
> NonfreeKernelModules: nvidia
> Package: mesa-utils 7.1~rc3-1ubuntu2
> ProcAttrCurrent: unconfined
> ProcCmdline: glxinfo
> ProcEnviron:
> SHELL=/bin/bash
>
> PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
> LANG=en_US.UTF-8
> Signal: 11
> SourcePackage: mesa
> Stacktrace:
> #0 0x0804ad66 in ?? ()
> #1 0xb7d66685 in __libc_start_main () from /lib/tls/i686/cmov/libc.so.6
> #2 0x08048e81 in ?? ()
> StacktraceTop:
> ?? ()
> __libc_start_main () from /lib/tls/i686/cmov/libc.so.6
> ?? ()
> ThreadStacktrace:
> .
> Thread 1 (process 7142...

jockey pulls in nvidia-common, nvidia-185-modaliases, nvidia-173-modaliases, and nvidia-96-modaliases; none of these packages contain the nvidia drivers.

Steve, those were the packages but my point is that I don't have any nvidia
hardware. I may have high jacked this thread though and branched off to a
subject that was not the original one.

Sorry if I did.

On Sun, Mar 21, 2010 at 12:14 AM, Steve Langasek <
<email address hidden>> wrote:

> jockey pulls in nvidia-common, nvidia-185-modaliases,
> nvidia-173-modaliases, and nvidia-96-modaliases; none of these packages
> contain the nvidia drivers.
>
> --
> glxinfo crashed with SIGSEGV in __libc_start_main()
> https://bugs.launchpad.net/bugs/256021
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in “mesa” package in Ubuntu: Fix Released
> Status in “mesa” source package in Jaunty: Fix Released
> Status in “mesa” source package in Karmic: Fix Released
>
> Bug description:
> [Impact]
>
> Fixes segmentation faults in glXGetFBConfigs() that happen frequently when
> the nvidia binary drivers are present on the system (even if they are not in
> use) by adding a null pointer check. While the SEGV seems innocuous since it
> only happens with glxinfo, quite a few essential programs such as compiz use
> glxinfo to detect GL capabilities and this causes problems. This is fixed in
> Karmic which as of this time has mesa 7.4.1, but the issue still stands in
> jaunty's 7.4.
>
> [Symptoms]
> Segfaults in glxinfo. glxinfo reporting Xlib: extension "GLX" missing on
> display.
>
> [Patch]
> http://launchpadlibrarian.net/28340399/mesa_7.4-0ubuntu3.2.debdiff
>
> [Test Case]
> In an affected system (such as one with nvidia drivers loaded)
> 1. Run glxinfo
> 2. Errors with a segfault
> 3. Attempt to start compiz
> 4. Fails to start because it can't run glxinfo
>
> [Regression Potential]
> Essentially none. It simply adds a null pointer check right before
> dereferencing it.
> This fix has been tested in Karmic as well as upstream for some time, and
> was included in the 7.4.1 bugfix release.
>
> UPDATE:Oct 8 2008. installed daily updates ( 2.6.27-6-generic ) and still
> getting this same glxinfo error on boot
>
>
> ------------------------------------------------------------------------------------------------------------------------------------
>
> I was running PlayOnLinux and tried to install 3d acceleration from there
> when glxinfo crashed.
>
> Description: Ubuntu intrepid (development branch)
> Release: 8.10
>
> mesa version : 7.1~rc3-1ubuntu2 (intrepid)
>
> ProblemType: Crash
> Architecture: i386
> DistroRelease: Ubuntu 8.10
> ExecutablePath: /usr/bin/glxinfo
> NonfreeKernelModules: nvidia
> Package: mesa-utils 7.1~rc3-1ubuntu2
> ProcAttrCurrent: unconfined
> ProcCmdline: glxinfo
> ProcEnviron:
> SHELL=/bin/bash
>
> PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
> LANG=en_US.UTF-8
> Signal: 11
> SourcePackage: mesa
> Stacktrace:
> #0 0x0804ad66 in ?? ()
> #1 0xb7d66685 in __libc_start_main () from /lib/tls/i686/cmov/libc.so.6
> #2 0x08048e81 in ?? ()
> StacktraceTop:
> ?? ()
> __libc_start_main () from /lib/tls/i686/cmov/libc.so.6
> ?? ()
> ThreadStacktrace:
> .
> Thread 1 (process 7142):
> #0 0x0804ad66 in ?? ()
> #1 0xb7d66685 in __libc_sta...

Why did you have the nvidia drivers installed, then? Barring a bug in jockey, these drivers should not have been automatically installed for you.

Steve, this is explained by my apt logs, which indicate that this affects people upgrading from karmic to lucid who have libmyth installed. The latest package versions and dependencies should have removed this problem.

Here's where I get the nvidia driver:

/var/log/dist-upgrade/apt.log: Installing nvidia-current as Depends of nvidia-185-libvdpau

These are from karmic
/var/log/dist-upgrade/20091031-0847/apt.log:Installing nvidia-185-libvdpau as dep of libmyth-0.22-0
/var/log/dist-upgrade/20091031-0933/apt.log:Installing nvidia-185-libvdpau as dep of libmyth-0.22-0

This is from karmic-lucid upgrade.
/var/log/dist-upgrade/20100319-0647/apt.log:Installing nvidia-185-libvdpau as dep of libmyth-0.22-0

Currently libmyth is at 0.3-2 and depends on libvdpau1-0.3-2 which replaces nvidia-185-libvdpau, so this shouldn't cause further problems.