gnome-calendar crashed with SIGSEGV in gtk_widget_queue_draw()

Bug #1722011 reported by Nathaniel W. Turner
This bug report is a duplicate of:  Edit Remove
10
This bug affects 1 person
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
ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
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/gnome-calendar
InstallationDate: Installed on 2014-08-21 (1143 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
ProcCmdline: /usr/bin/gnome-calendar --gapplication-service
SegvAnalysis:
 Segfault happened at: 0x7f3fe1068d0a <gtk_widget_queue_draw+42>: cmp %rax,(%rdx)
 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_queue_draw () 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
 g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: gnome-calendar crashed with SIGSEGV in gtk_widget_queue_draw()
UpgradeStatus: Upgraded to artful on 2017-10-07 (0 days ago)
UserGroups: adm cdrom dip libvirt libvirtd lpadmin lxd plugdev sambashare sudo

Revision history for this message
Nathaniel W. Turner (nturner) 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 #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.

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.
  • Duplicate of a private bug Remove

Other bug subscribers

Remote bug watches

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