gnome-shell crashed with SIGSEGV in __fork()

[Thomas]

gnome-shell crashed... had to logout and login again

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: gnome-shell 3.2.2.1-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-17.26-generic-pae 3.2.6
Uname: Linux 3.2.0-17-generic-pae i686
NonfreeKernelModules: nvidia
ApportVersion: 1.92-0ubuntu1
Architecture: i386
CrashCounter: 1
Date: Wed Feb 22 13:15:08 2012
ExecutablePath: /usr/bin/gnome-shell
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha i386 (20120201.1)
ProcCmdline: /usr/bin/gnome-shell
ProcEnviron:
 PATH=(custom, user)
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0xb5437ea3 <_nv022tls+19>: mov %eax,0xc(%edx)
 PC (0xb5437ea3) ok
 source "%eax" ok
 destination "0xc(%edx)" (0x0000000c) not located in a known VMA region (needed writable region)!
 Stack memory exhausted (SP below stack segment)
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: gnome-shell
StacktraceTop:
 _nv022tls () from /usr/lib/nvidia-current/tls/libnvidia-tls.so.295.20
 ?? () from /usr/lib/nvidia-current/libGL.so.1
 fork () from /lib/i386-linux-gnu/libpthread.so.0
 ?? () from /usr/lib/i386-linux-gnu/libpulse.so.0
 ?? () from /usr/lib/i386-linux-gnu/libpulse.so.0
Title: gnome-shell crashed with SIGSEGV in _nv022tls()
UpgradeStatus: Upgraded to precise on 2012-02-11 (11 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

[Apport retracing service (apport)]

StacktraceTop:
 ?? ()
 __fork () at ../nptl/sysdeps/unix/sysv/linux/pt-fork.c:26
 context_autospawn (c=0xb6ac14a0) at pulse/context.c:674
 try_next_connection (c=0xacd00b90) at pulse/context.c:816
 pa_context_connect (c=0xacd00b90, server=<optimized out>, flags=PA_CONTEXT_NOFAIL, api=0x0) at pulse/context.c:1010

[Thomas (t.c)]

nvidia bug?

[Jeremy Bícha (jbicha)]

Thank you for reporting this bug to Ubuntu. Ubuntu 12.04 LTS reached End of Life in April. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases

Please upgrade to Ubuntu 16.04 LTS and re-test. If the bug is still reproducible, increase the verbosity of the steps to recreate it so we can try again.

I apologize that we are not always to respond to bug reports promptly. Do feel free to report any other bugs you may find.