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

[Marcus]

.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: unity-services 4.16.0-0ubuntu2
ProcVersionSignature: Ubuntu 3.0.0-11.18-generic 3.0.4
Uname: Linux 3.0.0-11-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 1.23-0ubuntu1
Architecture: amd64
CompizPlugins: [core,bailer,detection,composite,opengl,compiztoolbox,decor,imgpng,unitymtgrabhandles,gnomecompat,vpswitch,resize,move,mousepoll,grid,snap,place,regex,animation,wall,fade,session,workarounds,scale,expo,ezoom,unityshell]
CrashCounter: 1
Date: Sun Sep 25 10:12:25 2011
EcryptfsInUse: Yes
ExecutablePath: /usr/lib/unity/unity-panel-service
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110426)
ProcCmdline: /usr/lib/unity/unity-panel-service
ProcEnviron:
 SHELL=/usr/bin/zsh
 PATH=(custom, no user)
 LANG=de_DE.UTF-8
SegvAnalysis:
 Segfault happened at: 0x7f3e6267bedc <__GI_getenv+156>: cmp 0x0(%rbp),%r12w
 PC (0x7f3e6267bedc) 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:
 __GI_getenv (name=0x7f3e6279c0f7 "NGUAGE") at getenv.c:90
 guess_category_value (category=5, categoryname=<optimized out>) at dcigettext.c:1359
 __dcigettext (domainname=0x7f3e62a6d540 "glib20", msgid1=0x7f3e63457f97 "Exit on close", msgid2=0x0, plural=0, n=0, category=5) at dcigettext.c:575
 ?? () 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
Title: unity-panel-service crashed with SIGSEGV in __GI_getenv()
UpgradeStatus: Upgraded to oneiric on 2011-09-07 (17 days ago)
UserGroups: adm admin cdrom dialout libvirtd 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 #858194, 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.