gnome-calendar crashed with SIGSEGV in gtk_image_clear()
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| gnome-calendar (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
Bug Description
Gnome Calender crash every time I open it on Uunbutu 18.04
It can't sycrhonise Google calendar
ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: gnome-calendar 3.28.0-1
ProcVersionSign
Uname: Linux 4.15.0-13-generic x86_64
ApportVersion: 2.20.9-0ubuntu2
Architecture: amd64
CrashCounter: 1
CurrentDesktop: Budgie:GNOME
Date: Sat Mar 31 11:21:12 2018
ExecutablePath: /usr/bin/
InstallationDate: Installed on 2018-03-29 (1 days ago)
InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180324)
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: 0x7f7e6ec6d667 <gtk_image_
PC (0x7f7e6ec6d667) ok
source "0x28(%rdi)" (0x00000028) not located in a known VMA region (needed readable region)!
destination "%rbp" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-calendar
StacktraceTop:
gtk_image_clear () at /usr/lib/
()
g_closure_invoke () at /usr/lib/
() at /usr/lib/
g_signal_
Title: gnome-calendar crashed with SIGSEGV in gtk_image_clear()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
| Jean-Francois Bourdeau (jfbourdeau) wrote | #1 |
| Apport retracing service (apport) wrote This bug is a duplicate | #2 |
| information type: | Private → Public |
| tags: | removed: need-amd64-retrace |
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 #1754202, 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.