** Changed in: gnome-calendar (Ubuntu)
Status: Confirmed => Triaged
** Summary changed:
- 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
--
You received this bug notification beca
Sorry for the confusion, I was using the snap version.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-calendar in Ubuntu.
https://bugs.launchpad.net/bugs/1756901
Title:
GNOME Calendar crashes when I try to add my Google Calen
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.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-calendar in Ubuntu.
https://bugs.launchpad.net/
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gnome-calendar (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-calendar in Ubuntu.
https://bugs.launch
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.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-calendar in
Moved here: https://gitlab.gnome.org/GNOME/gnome-calendar/issues/264
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-calendar in Ubuntu.
https://bugs.launchpad.net/bugs/1756901
Title:
GNOME Calendar crashes when I try to add m
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
** Bug watch added: GNOME Bug Tracker #794508
https://bugzilla.gnome.org/show_bug.
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
** Information type cha