It crashed while it was running in the background.
ProblemType: Crash
DistroRelease: Ubuntu 16.04
Package: gnome-calendar 3.20.2-0ubuntu0.1
ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
Uname: Linux 4.4.0-34-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CurrentDesktop: Unity
Date: Sun Sep 4 00:00:00 2016
ExecutablePath: /usr/bin/gnome-calendar
InstallationDate: Installed on 2016-04-26 (130 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
ProcCmdline: /usr/bin/gnome-calendar --gapplication-service
SegvAnalysis:
Segfault happened at: 0x4256a0 <gcal_manager_get_system_timezone>: mov 0x78(%rdi),%rax
PC (0x004256a0) ok
source "0x78(%rdi)" (0x00000078) not located in a known VMA region (needed readable region)!
destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-calendar
StacktraceTop:
gcal_manager_get_system_timezone ()
?? ()
?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
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
Title: gnome-calendar crashed with SIGSEGV in gcal_manager_get_system_timezone()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
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 #1554001, 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.