gnome-calendar crashed with SIGSEGV in GCAL_IS_MANAGER()

[Florian W.]

I was trying to click the "Hinzufügen" (add) button in the calendar settings dialog when this crash happened (at least I think it was the crash, the window closed itself).

Can't reproduce now.

I added my nextcloud instance in gnome settings and kept calendar sync enabled. Maybe the crash is related to the fact that I changed my calendar's name in the nextcloud online interface?

- Just upgraded to 17.10 today
- gnome-calendar is 3.26.2-1

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: gnome-calendar 3.26.2-1
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Oct 19 23:42:45 2017
ExecutablePath: /usr/bin/gnome-calendar
InstallationDate: Installed on 2013-03-10 (1684 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
ProcCmdline: /usr/bin/gnome-calendar --gapplication-service
SegvAnalysis:
 Segfault happened at: 0x5638ea94e1e6 <gcal_manager_get_default_source+22>: cmp (%rdx),%rax
 PC (0x5638ea94e1e6) ok
 source "(%rdx)" (0x13dfbaae5f) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: gnome-calendar
StacktraceTop:
 gcal_manager_get_default_source ()
 ?? ()
 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 gcal_manager_get_default_source()
UpgradeStatus: Upgraded to artful on 2017-10-19 (0 days ago)
UserGroups: adm cdrom dip kvm libvirtd lpadmin plugdev sambashare sudo wireshark

[Apport retracing service (apport)]

StacktraceTop:
 GCAL_IS_MANAGER (ptr=0x5638ecc236a0) at ../src/gcal-manager.h:34
 gcal_manager_get_default_source (self=0x5638ecc236a0) at ../src/gcal-manager.c:1213
 update_default_calendar_row (self=0x5638ecfa61d0) at ../src/gcal-quick-add-popover.c:487
 g_closure_invoke (closure=0x5638ed38e2b0, return_value=0x0, n_param_values=2, param_values=0x7ffd3d2a0e80, invocation_hint=0x7ffd3d2a0e00) at ../../../../gobject/gclosure.c:804
 signal_emit_unlocked_R (node=node@entry=0x5638eca0d140, detail=detail@entry=130, instance=instance@entry=0x5638eca1a940, emission_return=emission_return@entry=0x0, instance_and_params=instance_and_params@entry=0x7ffd3d2a0e80) at ../../../../gobject/gsignal.c:3635

[Launchpad Janitor (janitor)]

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

[Sebastien Bacher (seb128)]

Error report https://errors.ubuntu.com/problem/9e7f70933b33680ad8469ef7d0568eaeea7d1e04

[Sebastien Bacher (seb128)]

Upstreamed to https://gitlab.gnome.org/GNOME/gnome-calendar/issues/416

[Launchpad Janitor (janitor)]

This bug was fixed in the package gnome-calendar - 3.34.1-1

---------------
gnome-calendar (3.34.1-1) unstable; urgency=medium

  * New upstream release:
    - Fix various crashers (lp: #1725005)

 -- Sebastien Bacher <email address hidden> Mon, 07 Oct 2019 09:37:38 +0200