Ubuntu
gnome-calendar package

gnome-calendar crashed with SIGSEGV in gtk_image_clear()

Bug #1759699 reported by Amr Ibrahim on 2018-03-28

218

This bug affects 50 people

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

Bug Description

Steps:

1. Start Calendar
2. Add a Google account
3. Notice that the newly-created Google account does not appear in Calendar
4. Close Calendar
5. It crashes

ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: gnome-calendar 3.28.0-1
ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
Uname: Linux 4.15.0-13-generic x86_64
ApportVersion: 2.20.9-0ubuntu1
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Wed Mar 28 23:56:13 2018
ExecutablePath: /usr/bin/gnome-calendar
InstallationDate: Installed on 2017-10-02 (177 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20170930)
ProcCmdline: /usr/bin/gnome-calendar --gapplication-service
SegvAnalysis:
Segfault happened at: 0x7fe0719fc517 <gtk_image_clear+7>: mov 0x28(%rdi),%rbp
PC (0x7fe0719fc517) 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-03-27 (1 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Tags:

Revision history for this message

Amr Ibrahim (amribrahim1987) wrote on 2018-03-28:

#1

CoreDump.gz Edit (5.7 MiB, application/x-gzip)
Dependencies.txt Edit (9.9 KiB, text/plain; charset="utf-8")
Disassembly.txt Edit (1.1 KiB, text/plain; charset="utf-8")
JournalErrors.txt Edit (6.0 KiB, text/plain; charset="utf-8")
ProcCpuinfoMinimal.txt Edit (992 bytes, text/plain; charset="utf-8")
ProcEnviron.txt Edit (314 bytes, text/plain; charset="utf-8")
ProcMaps.txt Edit (103.1 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 (11.4 KiB, text/plain; charset="utf-8")

information type:

Private → Public

Revision history for this message

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

#2

Stacktrace:
#0 0x00007fe0719fc517 in ?? ()
No symbol table info available.
#1 0x0000000000000000 in ?? ()
No symbol table info available.
StacktraceSource:
#0 0x00007fe0719fc517 in ?? ()
#1 0x0000000000000000 in ?? ()
StacktraceTop:
?? ()
?? ()

Revision history for this message

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

#3

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

tags:	added: apport-failed-retrace
tags:	removed: need-amd64-retrace

Revision history for this message

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

#4

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

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

Revision history for this message

Wayne Stark (w-stark) wrote on 2018-04-13:

#5

Calendar crashed on me without doing anything, straight after login.

Revision history for this message

vasilisc (vasilisc) wrote on 2018-06-15:

#6

gnome-calendar:
  Installed: 3.28.2-1
  Candidate: 3.28.2-1
  Version table:
*** 3.28.2-1 500
        500 http://archive.ubuntu.com/ubuntu cosmic/main amd64 Packages
        100 /var/lib/dpkg/status

Report a bug

This report contains Public information

Everyone can see this information.

You are

Subscribing...

Edit bug mail

Other bug subscribers

Remote bug watches

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