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

[James Tait]

Sorry, I don't know what happened here. I was trying to do some hacking on Gwibber and then suddenly I was logged out.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: unity-services 5.4.0-0ubuntu2
ProcVersionSignature: Ubuntu 3.2.0-18.28-generic 3.2.9
Uname: Linux 3.2.0-18-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 1.94.1-0ubuntu1
Architecture: amd64
CheckboxSubmission: dd3689fa6394f60ec14dbe98d0bab891
CheckboxSystem: b633b4f40868d491c2ae5b50030ce6f3
CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
Date: Sat Mar 10 00:18:36 2012
EcryptfsInUse: Yes
ExecutablePath: /usr/lib/unity/unity-panel-service
InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100816.1)
ProcCmdline: /usr/lib/unity/unity-panel-service
SegvAnalysis:
 Segfault happened at: 0x7f31b9979ee5 <g_datalist_id_set_data_full+341>: mov 0x0(%r13),%esi
 PC (0x7f31b9979ee5) ok
 source "0x0(%r13)" (0xaaaaaaaaaaaaaaa8) not located in a known VMA region (needed readable region)!
 destination "%esi" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: unity
StacktraceTop:
 g_datalist_id_set_data_full () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_object_unref () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? ()
 g_object_unref () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: unity-panel-service crashed with SIGSEGV in g_datalist_id_set_data_full()
UpgradeStatus: Upgraded to precise on 2012-01-13 (56 days ago)
UserGroups: adm admin cdrom dialout disk libvirtd lpadmin plugdev sambashare vde2-net

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #928228, 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.