GNOME Calendar crashes in remove_source when I try to add my Google Calendar account

[Alexandru Tenie]

I clicked the following: Manage your calendars -> Calendar settings, which led me to the Settings program, the Online Accounts section, selected "Google account", entered my data. My data was successfully taken. GNOME Calendar did not load my calendar and crashed. Upon restarting GNOME Calendar/restarting Ubuntu, it did not load my calendar either. Clicking "Synchronise" did not fix the situation either.

Why do I think this is a security vulnerability? I am just a Computer Science student, but I imagine something might possibly come in the way so that personal data could be taken.

It happens if I run the vanilla gnome-session as well.

-Ubuntu Bionic Beaver (development branch), 18.04, on a fresh install.
-GNOME Calendar version: 3.28.0-1 (Version table: 3.28.0-1 500)
-What I expected to happen: load my Google Calendar data.
-What happened instead: crashed, didn't load my Google Calendar data, even if my Google account data is loaded my GNOME.

I hope Apport uploaded the debug information properly. If not, I can try to recreate the bug and upload the debug data, if necessary.

ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: gnome-calendar 3.28.0-1
ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
Uname: Linux 4.15.0-12-generic x86_64
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Mon Mar 19 16:40:14 2018
ExecutablePath: /usr/bin/gnome-calendar
InstallationDate: Installed on 2018-03-19 (0 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180319)
ProcCmdline: /usr/bin/gnome-calendar --gapplication-service
SegvAnalysis:
 Segfault happened at: 0x7f3513ec4d12 <g_type_check_instance_cast+34>: mov (%rdi),%rbp
 PC (0x7f3513ec4d12) ok
 source "(%rdi)" (0x2c6e616d656c6f63) not located in a known VMA region (needed readable region)!
 destination "%rbp" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: gnome-calendar
StacktraceTop:
 g_type_check_instance_cast () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.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 g_type_check_instance_cast()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

[Apport retracing service (apport)]

StacktraceTop:
 g_type_check_instance_cast (type_instance=0x56170bb6f930, iface_type=94656966589920) at ../../../../gobject/gtype.c:4057
 remove_source (manager=<optimized out>, source=0x7f34dc066940, user_data=<optimized out>) at ../src/gcal-source-dialog.c:1639
 g_closure_invoke (closure=0x56170bc13700, return_value=0x0, n_param_values=2, param_values=0x7ffe93ac6120, invocation_hint=0x7ffe93ac60a0) at ../../../../gobject/gclosure.c:804
 signal_emit_unlocked_R (node=node@entry=0x56170adee2f0, detail=detail@entry=0, instance=instance@entry=0x56170ade61c0, emission_return=emission_return@entry=0x0, instance_and_params=instance_and_params@entry=0x7ffe93ac6120) at ../../../../gobject/gsignal.c:3635
 g_signal_emit_valist (instance=<optimized out>, signal_id=<optimized out>, detail=<optimized out>, var_args=var_args@entry=0x7ffe93ac62f0) at ../../../../gobject/gsignal.c:3391

[Alexandru Tenie (atenie)]

Updated: This affects vanilla GNOME as well.

[Seth Arnold (seth-arnold)]

This line certainly looks suspicious:

source "(%rdi)" (0x2c6e616d656c6f63) not located in a known VMA

That hex represents the ascii string ",cameloc". Does this look familiar?

Have you filed a bug report upstream yet? If you have, could you paste the bug url here? Thanks

[Alexandru Tenie (atenie)]

Nope, doesn't look familiar. I have an AMD RX560, so there still could be some graphical errors that intervene, even if it's kernel version 4.15.

Filled one now: https://bugzilla.gnome.org/show_bug.cgi?id=794508

[Alexandru Tenie (atenie)]

Moved here: https://gitlab.gnome.org/GNOME/gnome-calendar/issues/264

[Alex (alexbennett)]

I tried to reproduce this bug in Bionic Daily, Calendar did not crash but after connecting to my google account and everything looking ok, no calendar events were shown.

[Launchpad Janitor (janitor)]

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

[fcole90 (fcole90)]

Hi, I have gnome-calendar 3.26.3 and I still experience this bug. Also, whenever I try to open it again it crashes after few seconds.

[fcole90 (fcole90)]

Sorry for the confusion, I was using the snap version.

[Sebastien Bacher (seb128)]

The issue is fixed in 19.10