gnome-shell-calendar-server crashed with SIGSEGV in g_str_hash()

[Tim Lunn]

This crashes fairly often, looking at the stacktrace it seems to be related to ical alarms

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: gnome-shell 3.8.3-1ubuntu3.1~raring1 [origin: LP-PPA-gnome3-team-gnome3-staging]
ProcVersionSignature: Ubuntu 3.10.0-4.13-generic 3.10.1
Uname: Linux 3.10.0-3-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.11-0ubuntu1
Architecture: amd64
CrashCounter: 1
Date: Mon Jul 22 08:26:05 2013
DisplayManager: gdm
ExecutablePath: /usr/lib/gnome-shell/gnome-shell-calendar-server
ExecutableTimestamp: 1373828109
InstallationDate: Installed on 2012-09-23 (302 days ago)
InstallationMedia: Ubuntu GNOME Remix 12.10 "Quantal Quetzal" - Alpha amd64(20120922)
MarkForUpload: True
ProcCmdline: /usr/lib/gnome-shell/gnome-shell-calendar-server
ProcCwd: /
SegvAnalysis:
 Segfault happened at: 0x7f8dd599c700 <g_str_hash>: movsbl (%rdi),%edx
 PC (0x7f8dd599c700) ok
 source "(%rdi)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%edx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-shell
StacktraceTop:
 g_str_hash (v=0x0) at /build/buildd/glib2.0-2.37.3/./glib/ghash.c:1732
 g_hash_table_lookup_node (hash_return=<synthetic pointer>, key=0x0, hash_table=0x2175920) at /build/buildd/glib2.0-2.37.3/./glib/ghash.c:365
 g_hash_table_lookup (hash_table=0x2175920, key=key@entry=0x0) at /build/buildd/glib2.0-2.37.3/./glib/ghash.c:1076
 add_alarm (comp=comp@entry=0x2182220, alarm=alarm@entry=0x2184ef0, auid=auid@entry=0x0) at e-cal-component.c:906
 scan_alarm (alarm=0x2184ef0, comp=0x2182220) at e-cal-component.c:954
Title: gnome-shell-calendar-server crashed with SIGSEGV in g_str_hash()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo

[Jeremy Bícha (jbicha)]

Thank you for reporting this bug to Ubuntu. I apologize that we are not always to respond to bug reports promptly. Ubuntu 13.10 reached End of Life in 2014. 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.

Do feel free to report any other bugs you may find.