gnome-calendar crashed with SIGSEGV in gtk_image_clear()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gnome-calendar (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
shortly after the virtual machine started. host arch linux. gues ubuntu budgie 18.04
ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: gnome-calendar 3.27.90-1build1
ProcVersionSign
Uname: Linux 4.15.0-10-generic x86_64
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
CurrentDesktop: Budgie:GNOME
Date: Sat Mar 10 20:02:54 2018
ExecutablePath: /usr/bin/
InstallationDate: Installed on 2018-03-09 (1 days ago)
InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180307.1)
JournalErrors:
-- Logs begin at Fri 2018-03-09 19:52:42 CET, end at Sun 2018-03-11 10:22:52 CET. --
mar 11 10:21:03 username-VirtualBox systemd[1]: Failed to start vboxadd-
mar 11 10:21:15 username-VirtualBox spice-vdagent[
mar 11 10:21:16 username-VirtualBox pulseaudio[1727]: [pulseaudio] pid.c: Daemon already running.
mar 11 10:21:41 username-VirtualBox pulseaudio[1662]: [pulseaudio] bluez5-util.c: GetManagedObjects() failed: org.freedesktop
ProcCmdline: /usr/bin/
SegvAnalysis:
Segfault happened at: 0x7f6472db4517 <gtk_image_
PC (0x7f6472db4517) 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 () from /usr/lib/
?? ()
g_closure_invoke () from /usr/lib/
?? () from /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
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.