gnome-calendar crashed with SIGSEGV in gtk_stack_set_visible_child_name()

[Nizar Kerkeni]

crashed when editing preferences

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: gnome-calendar 3.26.0-1
ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10
Uname: Linux 4.12.0-13-generic x86_64
ApportVersion: 2.20.7-0ubuntu1
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sat Sep 16 12:13:39 2017
ExecutablePath: /usr/bin/gnome-calendar
InstallationDate: Installed on 2017-04-22 (147 days ago)
InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
ProcCmdline: /usr/bin/gnome-calendar --gapplication-service
SegvAnalysis:
 Segfault happened at: 0x7f7e39a85f57 <gtk_stack_set_visible_child_name+7>: mov 0x30(%rdi,%rax,1),%edx
 PC (0x7f7e39a85f57) ok
 source "0x30(%rdi,%rax,1)" (0xfffffffffffffe80) not located in a known VMA region (needed readable region)!
 destination "%edx" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: gnome-calendar
StacktraceTop:
 gtk_stack_set_visible_child_name () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 ?? ()
 ?? ()
 g_hash_table_foreach () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? ()
Title: gnome-calendar crashed with SIGSEGV in gtk_stack_set_visible_child_name()
UpgradeStatus: Upgraded to artful on 2017-09-03 (12 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

[Apport retracing service (apport)]

StacktraceTop:
 gtk_stack_set_visible_child_name (stack=0x0, name=name@entry=0x55da272db4a0 "no-events") at ././gtk/gtkstack.c:1839
 gcal_year_view_component_removed (subscriber=0x55da294c2280, client=<optimized out>, uid=<optimized out>, rid=<optimized out>) at ../src/views/gcal-year-view.c:1896
 cal_data_model_foreach_subscriber_in_range (data_model=0x7f7e10003640, client=0x7f7e0c0206b0, in_range_start=1495926000, in_range_end=1496012400, func=0x55da272d5890 <cal_data_model_remove_one_view_component_cb>, user_data=0x55da2938bad0) at ../contrib/evolution/e-cal-data-model.c:619
 g_hash_table_foreach (hash_table=0x55da297b4d80, func=func@entry=0x55da272d52a0 <cal_data_model_notify_remove_components_cb>, user_data=user_data@entry=0x7ffd3274dea0) at ../../../../glib/ghash.c:1614
 cal_data_model_remove_client_view (data_model=data_model@entry=0x7f7e10003640, client=0x7f7e0c0206b0) at ../contrib/evolution/e-cal-data-model.c:1698

[Jean-Baptiste Lallement (jibel)]

Thanks for your report. I cannot make it crash by just editing preferences. Do you have any step to reproduce this defect?

[Wolfgang (wt-lists)]

I got this crash when after upgrade from 17.04, my Google calendars where imported but as my Google Account is 2FA the normal password box does not work. I got several password prompts, one for each of the Google calendars I had subscribed, I typed in the password but the boxes prompting for the password re-appeared after some time (which is probably as I'm using 2FA). At some point the calendar crashed. Not sure if this is connected, but at least the behaviour is strange...

[Kyriakos Fytrakis (kakosf)]

Basically, it happened when I added a calendar from a web link. After the set up, in the synchronization process the application crashed.

[Kakurady Drakenar (kakurady)]

I've also had a crash in this function.

I rebooted to finish installing 17.04, my Google calendars showed up in Evolution but not GNOME Shell or GNOME Calendar. When I tried to add an event, GNOME calendar crashed.

The event was successfully added to Google Calendar.

After restarting GNOME Calendar, everything showed up fine.

Bug 1689894 might be a duplicate of this bug.

[Kakurady Drakenar (kakurady)]

(So after crashing, I wasn't able to reproduce the crash.)

[Launchpad Janitor (janitor)]

[Expired for gnome-calendar (Ubuntu) because there has been no activity for 60 days.]

[Kostadin Stoilov (kmstoilov)]

This bug is still present on up to date Ubuntu 18.04