glxinfo crashed with SIGSEGV while switch back from guest user.

[Michael Fearon]

What I did:

Selected Guest user from the Fast User Switch Applet.
Then switched back to my actual log in account, again using the Fast Switch Applet.

What I expected to happen:

Nothing. I expected to be able to continue with my work without any issues.

What actually happened:

Apport offered to report a bug.
There was no obvious adverse affects, and I was able to continue with my work.

ProblemType: Crash
Architecture: i386
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/bin/glxinfo
NonfreeKernelModules: nvidia
Package: mesa-utils 7.3-1ubuntu4
ProcCmdline: /usr/bin/glxinfo
ProcEnviron:
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
ProcVersion: Linux version 2.6.28-11-generic (buildd@palmer) (gcc version 4.3.3 (Ubuntu 4.3.3-5ubuntu4) ) #39-Ubuntu SMP Thu Apr 2 03:00:35 UTC 2009
Signal: 11
SourcePackage: mesa
Stacktrace: #0 0xb740af97 in ?? () from /usr/lib/libGLcore.so.1
StacktraceTop: ?? () from /usr/lib/libGLcore.so.1
ThreadStacktrace:
 .
 Thread 1 (process 4168):
 #0 0xb740af97 in ?? () from /usr/lib/libGLcore.so.1
Title: glxinfo crashed with SIGSEGV
Uname: Linux 2.6.28-11-generic i686
UserGroups:

[lspci]
00:00.0 RAM memory [0500]: nVidia Corporation C51 Host Bridge [10de:02f5] (rev a2)
     Subsystem: Giga-byte Technology Device [1458:5000]
02:00.0 VGA compatible controller [0300]: nVidia Corporation G72 [GeForce 7300 LE] [10de:01d1] (rev a1)

[Michael Fearon (michaelfearon)]

A little bit more information to help reproduce the bug.

The bug only seems to appear on the initial switch to the guest user. In other words when the 'guest session' is selected from the Fast User Switch Applet, not guest as I initially stated.

[Apport retracing service (apport)]

StacktraceTop:?? () from /usr/lib/libGLcore.so.1

[Bryce Harrington (bryce)]

Yes, this is probably because only one session supports GL hardware acceleration at a time, and that probably triggers a bug somewhere inside the -nvidia driver.

[Bryce Harrington (bryce)]

I've posted a new version of the -nvidia driver to our xorg-edgers PPA,
would you mind testing it either on Jaunty or Karmic and see if it
resolves this bug?

Get nvidia-graphics-drivers-180 - 185.18.14 here:

  https://edge.launchpad.net/~xorg-edgers/+archive/ppa

[Bryce Harrington (bryce)]

We're closing this bug since it is has been some time with no response from the original reporter. However, if the issue still exists please feel free to reopen with the requested information. Also, if you could, please test against the latest development version of Ubuntu, since this confirms the bug is one we may be able to pass upstream for help.