gnome-calendar crashed with SIGSEGV in gdk_rgba_to_string()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gnome-calendar (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
I installed the gnome-calendar package and have Google accounts syncing. I didn't take any particular action to cause the crash.
ProblemType: Crash
DistroRelease: Ubuntu 19.10
Package: gnome-calendar 3.34.1-1
ProcVersionSign
Uname: Linux 5.3.0-13-generic x86_64
NonfreeKernelMo
ApportVersion: 2.20.11-0ubuntu7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Tue Oct 8 13:13:50 2019
ExecutablePath: /usr/bin/
InstallationDate: Installed on 2019-10-08 (0 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20190926.1)
ProcCmdline: /usr/bin/
ProcEnviron:
SHELL=/bin/bash
XDG_RUNTIME_
PATH=(custom, no user)
LANG=en_US.UTF-8
SegvAnalysis:
Segfault happened at: 0x7f7213d038bd <gdk_rgba_
PC (0x7f7213d038bd) ok
source "0x18(%rdi)" (0x00000018) not located in a known VMA region (needed readable region)!
destination "%xmm0" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-calendar
StacktraceTop:
gdk_rgba_to_string () from /lib/x86_
?? ()
g_closure_invoke () from /lib/x86_
?? () from /lib/x86_
g_signal_
Title: gnome-calendar crashed with SIGSEGV in gdk_rgba_
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
separator:
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 #1846292, 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.