GNOME Calendar crashes in remove_source when I try to add my Google Calendar account
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
GNOME Calendar |
Fix Released
|
Unknown
|
|||
gnome-calendar (Ubuntu) |
Fix Released
|
Medium
|
Unassigned |
Bug Description
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
ProcVersionSign
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/
InstallationDate: Installed on 2018-03-19 (0 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180319)
ProcCmdline: /usr/bin/
SegvAnalysis:
Segfault happened at: 0x7f3513ec4d12 <g_type_
PC (0x7f3513ec4d12) ok
source "(%rdi)" (0x2c6e616d656c
destination "%rbp" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: gnome-calendar
StacktraceTop:
g_type_
?? ()
g_closure_invoke () from /usr/lib/
?? () from /usr/lib/
g_signal_
Title: gnome-calendar crashed with SIGSEGV in g_type_
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
Changed in gnome-calendar (Ubuntu): | |
status: | Confirmed → Triaged |
summary: |
- GNOME Calendar crashes when I try to add my Google Calendar account + GNOME Calendar crashes in remove_source when I try to add my Google + Calendar account |
Changed in gnome-calendar: | |
status: | Unknown → Fix Released |
StacktraceTop: check_instance_ cast (type_instance= 0x56170bb6f930, iface_type= 94656966589920) at ../../. ./../gobject/ gtype.c: 4057 0x7f34dc066940, user_data= <optimized out>) at ../src/ gcal-source- dialog. c:1639 0x56170bc13700, return_value=0x0, n_param_values=2, param_values= 0x7ffe93ac6120, invocation_ hint=0x7ffe93ac 60a0) at ../../. ./../gobject/ gclosure. c:804 emit_unlocked_ R (node=node@ entry=0x56170ad ee2f0, detail= detail@ entry=0, instance= instance@ entry=0x56170ad e61c0, emission_ return= emission_ return@ entry=0x0, instance_ and_params= instance_ and_params@ entry=0x7ffe93a c6120) at ../../. ./../gobject/ gsignal. c:3635 emit_valist (instance= <optimized out>, signal_ id=<optimized out>, detail=<optimized out>, var_args= var_args@ entry=0x7ffe93a c62f0) at ../../. ./../gobject/ gsignal. c:3391
g_type_
remove_source (manager=<optimized out>, source=
g_closure_invoke (closure=
signal_
g_signal_