gnome-calendar crashed with SIGSEGV in gcal_manager_refresh()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gnome-calendar (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
This occurred after I closed GNOME Calendar.
Happened while running Ubuntu GNOME 16.10 beta, Gnome 3.20 desktop environment.
ProblemType: Crash
DistroRelease: Ubuntu 16.10
Package: gnome-calendar 3.20.3-0ubuntu2
ProcVersionSign
Uname: Linux 4.4.0-9136-generic x86_64
ApportVersion: 2.20.3-0ubuntu7
Architecture: amd64
CurrentDesktop: GNOME
Date: Mon Sep 12 10:21:14 2016
ExecutablePath: /usr/bin/
InstallationDate: Installed on 2016-08-30 (13 days ago)
InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Alpha amd64 (20160824)
ProcCmdline: /usr/bin/
ProcEnviron:
SHELL=/bin/bash
XDG_RUNTIME_
PATH=(custom, user)
LANG=en_US.UTF-8
SegvAnalysis:
Segfault happened at: 0x55a514550978 <gcal_manager_
PC (0x55a514550978) ok
source "0x18(%rdi)" (0x00000018) not located in a known VMA region (needed readable region)!
destination "%rdi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-calendar
StacktraceTop:
gcal_manager_
?? ()
?? () from /lib/x86_
g_main_
?? () from /lib/x86_
Title: gnome-calendar crashed with SIGSEGV in gcal_manager_
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 #1561957, 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.