gnome-calendar crashed with SIGSEGV in gcal_manager_get_source()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gnome-calendar (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
N/A
ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: gnome-calendar 3.26.3-1
ProcVersionSign
Uname: Linux 4.13.0-32-generic x86_64
NonfreeKernelMo
ApportVersion: 2.20.8-0ubuntu8
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Feb 8 20:28:53 2018
ExecutablePath: /usr/bin/
InstallationDate: Installed on 2018-02-08 (0 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180207)
ProcCmdline: /usr/bin/
ProcEnviron:
XDG_RUNTIME_
SHELL=/bin/bash
LANGUAGE=en_CA:en
PATH=(custom, no user)
LANG=en_CA.UTF-8
SegvAnalysis:
Segfault happened at: 0x557bbca77026 <gcal_manager_
PC (0x557bbca77026) ok
source "(%rbx)" (0x00000450) not located in a known VMA region (needed readable region)!
destination "%rdx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-calendar
StacktraceTop:
gcal_manager_
?? ()
ffi_call_unix64 () from /usr/lib/
ffi_call () from /usr/lib/
g_cclosure_
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 #1723569, 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.