gnome-shell crashed with SIGSEGV in lookup_or_create_bucket()

[Joe Barnett]

getthing this after upgrade to precise, but shell is not actually crashing?

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: gnome-shell 3.2.2.1-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-18.28-generic 3.2.9
Uname: Linux 3.2.0-18-generic x86_64
ApportVersion: 1.94-0ubuntu1
Architecture: amd64
Date: Mon Mar 5 16:55:42 2012
ExecutablePath: /usr/bin/gnome-shell
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Release Candidate amd64 (20100419.1)
ProcCmdline: /usr/bin/gnome-shell
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x240d520: (bad)
 PC (0x0240d520) in non-executable VMA region: 0x01dfa000-0x02554000 rw-p [heap]
SegvReason: executing writable VMA [heap]
Signal: 11
SourcePackage: gnome-shell
StacktraceTop:
 ?? ()
 ?? () from /usr/lib/x86_64-linux-gnu/libp11-kit.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libp11-kit.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libp11-kit.so.0
 p11_kit_initialize_registered () from /usr/lib/x86_64-linux-gnu/libp11-kit.so.0
Title: gnome-shell crashed with SIGSEGV in p11_kit_initialize_registered()
UpgradeStatus: Upgraded to precise on 2012-03-06 (0 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare sudo vboxusers

[Apport retracing service (apport)]

StacktraceTop:
 ?? ()
 lookup_or_create_bucket (map=0x23fc790, key=0x7fe6a9282f00, create=0) at hashmap.c:109
 _p11_hash_get (map=<optimized out>, key=<optimized out>) at hashmap.c:139
 take_config_and_load_module_unlocked (config=0x7fffd51588e0, name=0x7fffd51588d8) at modules.c:412
 load_registered_modules_unlocked () at modules.c:462

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Jeremy Bícha (jbicha)]

Thank you for reporting this bug to Ubuntu. Ubuntu 12.04 LTS reached End of Life in April. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases

Please upgrade to Ubuntu 16.04 LTS and re-test. If the bug is still reproducible, increase the verbosity of the steps to recreate it so we can try again.

I apologize that we are not always to respond to bug reports promptly. Do feel free to report any other bugs you may find.