gnome-calendar crashed with SIGSEGV in gtk_image_clear()

Bug #1764030 reported by Clemens Vermeulen
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gnome-calendar (Ubuntu)
New
Undecided
Unassigned

Bug Description

On Quit

ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: gnome-calendar 3.28.1-1ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
Uname: Linux 4.15.0-15-generic x86_64
ApportVersion: 2.20.9-0ubuntu4
Architecture: amd64
CurrentDesktop: Budgie:GNOME
Date: Sun Apr 15 11:06:09 2018
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/gnome-calendar
InstallationDate: Installed on 2017-09-29 (197 days ago)
InstallationMedia: Ubuntu-Budgie 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
ProcCmdline: /usr/bin/gnome-calendar --gapplication-service
SegvAnalysis:
 Segfault happened at: 0x7ff177853667 <gtk_image_clear+7>: mov 0x28(%rdi),%rbp
 PC (0x7ff177853667) 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/x86_64-linux-gnu/libgtk-3.so.0
 ?? ()
 g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: gnome-calendar crashed with SIGSEGV in gtk_image_clear()
UpgradeStatus: Upgraded to bionic on 2018-04-14 (0 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
Clemens Vermeulen (barefootwarrior) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

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.

information type: Private → Public
tags: removed: need-amd64-retrace
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.