After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 794508 - GNOME Calendar crashes when I try to add my Google Calendar account
GNOME Calendar crashes when I try to add my Google Calendar account
Status: RESOLVED INCOMPLETE
Product: gnome-control-center
Classification: Core
Component: User Accounts
3.28.x
Other Linux
: Normal major
: ---
Assigned To: Control-Center Maintainers
Control-Center Maintainers
Depends on:
Blocks:
 
 
Reported: 2018-03-20 06:28 UTC by Alexandru Tenie
Modified: 2018-03-20 18:00 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Alexandru Tenie 2018-03-20 06:28:28 UTC
See: https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1756901?comments=all

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.

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.

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
Comment 1 Benjamin Berg 2018-03-20 08:46:03 UTC
This is most likely a gnome-calendar issue. Or a library supporting it, but not gnome-settings-daemon.

Moved to https://gitlab.gnome.org/GNOME/gnome-calendar/issues/264 for further investigation. Please subscribe yourself there.