gnome-calendar crashed with SIGSEGV in gtk_widget_queue_draw()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gnome-calendar (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
n/a
ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: gnome-calendar 3.26.2-1
ProcVersionSign
Uname: Linux 4.13.0-12-generic x86_64
ApportVersion: 2.20.7-0ubuntu2
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sat Oct 7 18:12:00 2017
ExecutablePath: /usr/bin/
InstallationDate: Installed on 2014-08-21 (1143 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
ProcCmdline: /usr/bin/
SegvAnalysis:
Segfault happened at: 0x7f3fe1068d0a <gtk_widget_
PC (0x7f3fe1068d0a) ok
source "%rax" ok
destination "(%rdx)" (0x400000000a) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: gnome-calendar
StacktraceTop:
gtk_widget_
g_closure_invoke () from /usr/lib/
?? () from /usr/lib/
g_signal_
g_signal_emit () from /usr/lib/
Title: gnome-calendar crashed with SIGSEGV in gtk_widget_
UpgradeStatus: Upgraded to artful on 2017-10-07 (0 days ago)
UserGroups: adm cdrom dip libvirt libvirtd lpadmin lxd 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 #1702473, 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.