gnome-calendar crashed with SIGSEGV in gtk_image_clear()
| 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
ProcVersionSign
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/
InstallationDate: Installed on 2017-09-29 (197 days ago)
InstallationMedia: Ubuntu-Budgie 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
ProcCmdline: /usr/bin/
SegvAnalysis:
Segfault happened at: 0x7ff177853667 <gtk_image_
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/
?? ()
g_closure_invoke () from /usr/lib/
?? () from /usr/lib/
g_signal_
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
| Clemens Vermeulen (barefootwarrior) 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.