Ubuntu
gnome-calendar package

gnome-calendar crashed with SIGSEGV in gtk_image_reset()

Bug #1754202 reported by Andrei on 2018-03-08

406

This bug affects 65 people

Affects		Status	Importance	Assigned to	Milestone
	gnome-calendar (Ubuntu)	Confirmed	Medium	Unassigned

Bug Description

closed

ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: gnome-calendar 3.27.90-1build1
ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
Uname: Linux 4.15.0-10-generic x86_64
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME
Date: Thu Mar 8 02:33:36 2018
ExecutablePath: /usr/bin/gnome-calendar
InstallationDate: Installed on 2018-02-03 (32 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180119)
ProcCmdline: /usr/bin/gnome-calendar --gapplication-service
SegvAnalysis:
Segfault happened at: 0x7fd5d5622517 <gtk_image_clear+7>: mov 0x28(%rdi),%rbp
PC (0x7fd5d5622517) 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: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Tags:

Revision history for this message

Andrei (ghandrei) wrote on 2018-03-08:

#1

Dependencies.txt Edit (10.5 KiB, text/plain; charset="utf-8")
Disassembly.txt Edit (1.1 KiB, text/plain; charset="utf-8")
JournalErrors.txt Edit (1.6 KiB, text/plain; charset="utf-8")
ProcCpuinfoMinimal.txt Edit (830 bytes, text/plain; charset="utf-8")
ProcEnviron.txt Edit (308 bytes, text/plain; charset="utf-8")
ProcMaps.txt Edit (107.8 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (1.3 KiB, text/plain; charset="utf-8")
Registers.txt Edit (778 bytes, text/plain; charset="utf-8")
Stacktrace.txt Edit (1.9 KiB, text/plain; charset="utf-8")
ThreadStacktrace.txt Edit (12.7 KiB, text/plain; charset="utf-8")

Revision history for this message

Apport retracing service (apport) wrote on 2018-03-08:

#2

StacktraceTop:
gtk_image_reset (image=0x0) at ../../../../gtk/gtkimage.c:1864
gtk_image_clear (image=0x0) at ../../../../gtk/gtkimage.c:1909
update_weather (self=0x556c508283c0) at ../src/views/gcal-year-view.c:2113
g_closure_invoke (closure=0x556c50937b50, return_value=0x0, n_param_values=1, param_values=0x7fffdcadaf40, invocation_hint=0x7fffdcadaec0) at ../../../../gobject/gclosure.c:804
signal_emit_unlocked_R (node=node@entry=0x556c5045f960, detail=detail@entry=0, instance=instance@entry=0x556c50518040, emission_return=emission_return@entry=0x0, instance_and_params=instance_and_params@entry=0x7fffdcadaf40) at ../../../../gobject/gsignal.c:3635

Revision history for this message

Apport retracing service (apport) wrote on 2018-03-08: Stacktrace.txt

#3

Stacktrace.txt Edit (7.9 KiB, text/plain)

Revision history for this message

Apport retracing service (apport) wrote on 2018-03-08: StacktraceSource.txt

#4

StacktraceSource.txt Edit (4.9 KiB, text/plain)

Revision history for this message

Apport retracing service (apport) wrote on 2018-03-08: ThreadStacktrace.txt

#5

ThreadStacktrace.txt Edit (26.0 KiB, text/plain)

Changed in gnome-calendar (Ubuntu):
importance:	Undecided → Medium
summary:	- gnome-calendar crashed with SIGSEGV in gtk_image_clear() + gnome-calendar crashed with SIGSEGV in gtk_image_reset()
tags:	removed: need-amd64-retrace

Revision history for this message

Launchpad Janitor (janitor) wrote on 2018-03-09:

#6

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in gnome-calendar (Ubuntu):
status:	New → Confirmed

Apport retracing service (apport) on 2018-03-13

tags:

added: bugpattern-needed

Sebastien Bacher (seb128) on 2018-03-13

information type:

Private → Public

Report a bug

This report contains Public information

Everyone can see this information.

Duplicates of this bug

You are

Subscribing...

Edit bug mail

Other bug subscribers

Remote bug watches

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