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

[Frank Bicknell]

completely out of the blue

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: unity-services 5.20.0-0ubuntu3
ProcVersionSignature: Ubuntu 3.2.0-67.101-generic 3.2.60
Uname: Linux 3.2.0-67-generic x86_64
NonfreeKernelModules: nvidia zfs zcommon znvpair zavl zunicode
ApportVersion: 2.0.1-0ubuntu17.6
Architecture: amd64
CheckboxSubmission: 48349af06a737bc39f5bd5104a6aec3f
CheckboxSystem: daed2f3d6643b4a84b4520a2427f8c2b
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: Sun Jul 20 15:14:05 2014
ExecutablePath: /usr/lib/unity/unity-panel-service
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120328)
MarkForUpload: True
ProcCmdline: /usr/lib/unity/unity-panel-service
SegvAnalysis:
 Segfault happened at: 0x4063bd: mov (%rbx),%rdx
 PC (0x004063bd) ok
 source "(%rbx)" (0x00000002) not located in a known VMA region (needed readable region)!
 destination "%rdx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: unity
StacktraceTop:
 ?? ()
 ?? () from /usr/lib/x86_64-linux-gnu/gtk-3.0/modules/libatk-bridge.so
 g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
Title: unity-panel-service crashed with SIGSEGV in g_main_context_dispatch()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip fuse lpadmin plugdev sambashare sudo vboxusers

[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 #869816, 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.