unity-panel-service crashed with SIGSEGV in getenv()

[Jane Silber]

After update on 15 Sept (Oneiric beta), unity-panel-service crash reported, leaving system unusable and with no launcher, panel, etc. Could be a dupe of Bug #817691 , but I didn't get the same warning messages described there.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: unity-services 4.14.2-0ubuntu2
ProcVersionSignature: Ubuntu 3.0.0-11.18-generic 3.0.4
Uname: Linux 3.0.0-11-generic x86_64
ApportVersion: 1.23-0ubuntu1
Architecture: amd64
CompizPlugins: [core,bailer,detection,composite,opengl,compiztoolbox,decor,resize,vpswitch,mousepoll,grid,snap,imgpng,place,session,move,regex,gnomecompat,unitymtgrabhandles,wall,animation,workarounds,expo,fade,ezoom,scale,unityshell]
CrashCounter: 1
Date: Thu Sep 15 13:46:14 2011
ExecutablePath: /usr/lib/unity/unity-panel-service
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
ProcCmdline: /usr/lib/unity/unity-panel-service
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, no user)
 LANG=en_GB.UTF-8
SegvAnalysis:
 Segfault happened at: 0x7f234f88eedc <getenv+156>: cmp 0x0(%rbp),%r12w
 PC (0x7f234f88eedc) ok
 source "0x0(%rbp)" (0x00000110) not located in a known VMA region (needed readable region)!
 destination "%r12w" ok
 Stack memory exhausted (SP below stack segment)
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: unity
StacktraceTop:
 getenv () from /lib/x86_64-linux-gnu/libc.so.6
 ?? () from /lib/x86_64-linux-gnu/libc.so.6
 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 g_type_class_ref () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_object_new_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: unity-panel-service crashed with SIGSEGV in getenv()
UpgradeStatus: Upgraded to oneiric on 2011-09-07 (7 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #849396, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.