Saving a new entry, edited the date and time. Synced successfully to my online calendar but crashed in the process.
ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: gnome-calendar 3.28.0-1
ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
Uname: Linux 4.15.0-13-generic x86_64
ApportVersion: 2.20.9-0ubuntu4
Architecture: amd64
CrashCounter: 1
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr 13 09:43:01 2018
ExecutablePath: /usr/bin/gnome-calendar
InstallationDate: Installed on 2017-07-18 (269 days ago)
InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
ProcCmdline: /usr/bin/gnome-calendar --gapplication-service
ProcEnviron:
XDG_RUNTIME_DIR=<set>
SHELL=/usr/bin/zsh
PATH=(custom, no user)
LANG=en_US.UTF-8
SegvAnalysis:
Segfault happened at: 0x55e0696ba1c6 <gcal_manager_get_default_source+22>: cmp (%rdx),%rax
PC (0x55e0696ba1c6) ok
source "(%rdx)" (0x9d946c700) not located in a known VMA region (needed readable region)!
destination "%rax" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: gnome-calendar
StacktraceTop:
gcal_manager_get_default_source ()
()
g_closure_invoke () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
() at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
g_signal_emit_valist () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: gnome-calendar crashed with SIGSEGV in gcal_manager_get_default_source()
UpgradeStatus: Upgraded to bionic on 2018-04-05 (7 days ago)
UserGroups: adm cdrom dip docker 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 #1725005, 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.