unity-panel-service crashed with signal 5 in g_type_create_instance()

[Stuart Langridge]

System hung while doing a dist-upgrade. After reboot, system came back up in "low graphics" mode. After completing the upgrade and rebooting again, many error dialogs were shown; this was one.

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: indicator-appmenu 13.01.0+13.10.20130812-0ubuntu1
ProcVersionSignature: Ubuntu 3.11.0-5.11-generic 3.11.0
Uname: Linux 3.11.0-5-generic x86_64
ApportVersion: 2.12.1-0ubuntu3
Architecture: amd64
CheckboxSubmission: 4d186c1dd89d3ba4cb89f5ee55713686
CheckboxSystem: bb422ca46d02494cdbc459927a98bc2f
Date: Mon Sep 9 22:51:21 2013
EcryptfsInUse: Yes
ExecutablePath: /usr/lib/unity/unity-panel-service
InstallationDate: Installed on 2011-12-11 (638 days ago)
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20111211)
MarkForUpload: True
ProcCmdline: /usr/lib/unity/unity-panel-service
ProcEnviron:
 PATH=(custom, user)
 LANGUAGE=en_GB:en
 XDG_RUNTIME_DIR=<set>
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
Signal: 5
SourcePackage: indicator-appmenu
StacktraceTop:
 ?? () from /usr/lib/x86_64-linux-gnu/libbamf3.so.2
 g_type_create_instance () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_object_newv () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_object_new () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: unity-panel-service crashed with signal 5 in g_type_create_instance()
UpgradeStatus: Upgraded to saucy on 2013-09-05 (4 days ago)
UserGroups: adm autopilot cdrom dip fuse libvirtd 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 #1201947, 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.