GNU bug report logs -
#78015
GNOME calendar doesn't save reminders
Previous Next
To reply to this bug, email your comments to 78015 AT debbugs.gnu.org.
There is no need to reopen the bug first.
Toggle the display of automated, internal messages from the tracker.
Report forwarded
to
liliana.prikler <at> gmail.com, maxim.cournoyer <at> gmail.com, noelopez <at> free.fr, vivien <at> planete-kraus.eu, bug-guix <at> gnu.org
:
bug#78015
; Package
guix
.
(Wed, 23 Apr 2025 15:36:06 GMT)
Full text and
rfc822 format available.
Acknowledgement sent
to
Maxim Cournoyer <maxim.cournoyer <at> gmail.com>
:
New bug report received and forwarded. Copy sent to
liliana.prikler <at> gmail.com, maxim.cournoyer <at> gmail.com, noelopez <at> free.fr, vivien <at> planete-kraus.eu, bug-guix <at> gnu.org
.
(Wed, 23 Apr 2025 15:36:06 GMT)
Full text and
rfc822 format available.
Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):
Hi,
There appears to be an issue with our GNOME calendar (the one accessible
from the top clock): reminders added to a calendar event are not saved
when pressing 'Save' after editing the event. They are silently
dropped!
--
Thanks,
Maxim
Information forwarded
to
bug-guix <at> gnu.org
:
bug#78015
; Package
guix
.
(Wed, 23 Apr 2025 17:00:05 GMT)
Full text and
rfc822 format available.
Message #8 received at 78015 <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
Maxim Cournoyer <maxim.cournoyer <at> gmail.com> writes:
> Hi,
>
> There appears to be an issue with our GNOME calendar (the one accessible
> from the top clock): reminders added to a calendar event are not saved
> when pressing 'Save' after editing the event. They are silently
> dropped!
>
Can reproduce!
The dbus logs have the errors:
tail /home/noe/.local/state/shepherd/dbus.log
2025-04-23 18:48:54 (gnome-calendar:3577): e-data-server-CRITICAL **: 18:48:54.398: e_source_registry_ref_builtin_calendar: assertion 'source != NULL' failed
2025-04-23 18:48:54 (gnome-calendar:3577): e-data-server-CRITICAL **: 18:48:54.398: e_source_registry_ref_default_calendar: assertion 'E_IS_SOURCE (source)' failed
2025-04-23 18:48:54 (gnome-calendar:3577): e-data-server-CRITICAL **: 18:48:54.398: e_source_hash: assertion 'E_IS_SOURCE (source)' failed
2025-04-23 18:48:54 (gnome-calendar:3577): e-data-server-CRITICAL **: 18:48:54.751: e_source_registry_ref_builtin_calendar: assertion 'source != NULL' failed
2025-04-23 18:48:54 (gnome-calendar:3577): e-data-server-CRITICAL **: 18:48:54.751: e_source_registry_ref_default_calendar: assertion 'E_IS_SOURCE (source)' failed
2025-04-23 18:48:54 (gnome-calendar:3577): e-data-server-CRITICAL **: 18:48:54.751: e_source_hash: assertion 'E_IS_SOURCE (source)' failed
2025-04-23 18:48:54 (gnome-calendar:3577): GcalCalendar-CRITICAL **: 18:48:54.768: gcal_calendar_get_name: assertion 'GCAL_IS_CALENDAR (self)' failed
2025-04-23 18:48:54 (gnome-calendar:3577): GcalCalendar-CRITICAL **: 18:48:54.768: gcal_calendar_is_read_only: assertion 'GCAL_IS_CALENDAR (self)' failed
2025-04-23 18:49:05 (gnome-calendar:3577): GcalCalendar-CRITICAL **: 18:49:05.267: gcal_calendar_is_read_only: assertion 'GCAL_IS_CALENDAR (self)' failed
2025-04-23 18:49:05 (gnome-calendar:3577): GcalCalendar-CRITICAL **: 18:49:05.267: gcal_calendar_get_client: assertion 'GCAL_IS_CALENDAR (self)' failed
2025-04-23 18:49:05 (gnome-calendar:3577): libecal-CRITICAL **: 18:49:05.267: e_cal_client_create_object: assertion 'E_IS_CAL_CLIENT (client)' failed
2025-04-23 18:49:15 (gnome-calendar:3577): e-data-server-CRITICAL **: 18:49:15.097: e_source_registry_ref_builtin_calendar: assertion 'source != NULL' failed
2025-04-23 18:49:15 (gnome-calendar:3577): e-data-server-CRITICAL **: 18:49:15.097: e_source_registry_ref_default_calendar: assertion 'E_IS_SOURCE (source)' failed
2025-04-23 18:49:15 (gnome-calendar:3577): e-data-server-CRITICAL **: 18:49:15.097: e_source_hash: assertion 'E_IS_SOURCE (source)' failed
2025-04-23 18:49:15 (gnome-calendar:3577): GcalCalendar-CRITICAL **: 18:49:15.111: gcal_calendar_get_name: assertion 'GCAL_IS_CALENDAR (self)' failed
2025-04-23 18:49:15 (gnome-calendar:3577): GcalCalendar-CRITICAL **: 18:49:15.111: gcal_calendar_is_read_only: assertion 'GCAL_IS_CALENDAR (self)' failed
2025-04-23 18:49:18 (gnome-calendar:3577): GcalCalendar-CRITICAL **: 18:49:18.739: gcal_calendar_is_read_only: assertion 'GCAL_IS_CALENDAR (self)' failed
2025-04-23 18:49:18 (gnome-calendar:3577): GcalCalendar-CRITICAL **: 18:49:18.739: gcal_calendar_get_client: assertion 'GCAL_IS_CALENDAR (self)' failed
2025-04-23 18:49:18 (gnome-calendar:3577): libecal-CRITICAL **: 18:49:18.739: e_cal_client_create_object: assertion 'E_IS_CAL_CLIENT (client)' failed
2025-04-23 18:49:27 (gnome-calendar:3577): e-data-server-CRITICAL **: 18:49:27.493: e_source_registry_ref_builtin_calendar: assertion 'source != NULL'
2025-04-23 18:49:27 (gnome-calendar:3577): e-data-server-CRITICAL **: 18:49:27.493: e_source_registry_ref_default_calendar: assertion 'E_IS_SOURCE (source)' failed
2025-04-23 18:49:27 (gnome-calendar:3577): e-data-server-CRITICAL **: 18:49:27.493: e_source_hash: assertion 'E_IS_SOURCE (source)' failed
This hints that we have no calendar to save the events to, and indeed
when clicking on calendar on the top left it seems we have a nothing
calendar selected.
Clicking on manage agendas there is also an empty list. Adding an agenda
does not work with these logs:
2025-04-23 18:53:28 (gnome-calendar:3577): GcalManager-WARNING **: 18:53:28.506: Error saving source: The name org.gnome.evolution.dataserver.Sources5 was not provided by any .service files
2025-04-23 18:53:33 (gnome-calendar:3577): GcalManager-WARNING **: 18:53:33.761: Error saving source: The name org.gnome.evolution.dataserver.Sources5 was not provided by any .service files
So, this might be our root issue? Can you reproduce the same errors?
[signature.asc (application/pgp-signature, inline)]
Information forwarded
to
bug-guix <at> gnu.org
:
bug#78015
; Package
guix
.
(Wed, 23 Apr 2025 18:35:05 GMT)
Full text and
rfc822 format available.
Message #11 received at 78015 <at> debbugs.gnu.org (full text, mbox):
Am Mittwoch, dem 23.04.2025 um 18:59 +0200 schrieb Noé Lopez:
> Can reproduce!
>
> […]
> This hints that we have no calendar to save the events to, and indeed
> when clicking on calendar on the top left it seems we have a nothing
> calendar selected.
>
> Clicking on manage agendas there is also an empty list. Adding an
> agenda does not work with these logs:
> […]
>
> So, this might be our root issue? Can you reproduce the same errors?
To my knowledge, none of this should be happening.
$ guix show gnome
name: gnome
version: 46.10
outputs:
+ out: alles
systems: x86_64-linux
dependencies: […]
+ evolution-data-server <at> 3.54.3 […]
$ ls $(guix build evolution-data-server)/share/dbus-1/services/
org.gnome.evolution.dataserver.AddressBook10.service
org.gnome.evolution.dataserver.Sources5.service
org.gnome.evolution.dataserver.Calendar8.service
org.gnome.evolution.dataserver.UserPrompter0.service
These services should be copied over to the system profile as well.
Now everything has the guix-daemon:guix-daemon permissions on my
machine, because I'm using an unprivileged daemon shortly after the
switch and maybe these permissions mean something – I still have to
confirm the actual issue.
On my machine, using Gnome Calendar to add event reminders, I get
(gnome-calendar:13557): Gtk-WARNING **: 20:30:41.555: actionhelper:
action event-editor-dialog.select-calendar can't be activated due to
parameter type mismatch (parameter type s, target type NULL)
whereas alarm notifications in Evolution work as expected.
Cheers
Reply sent
to
Maxim Cournoyer <maxim.cournoyer <at> gmail.com>
:
You have taken responsibility.
(Thu, 24 Apr 2025 01:50:02 GMT)
Full text and
rfc822 format available.
Notification sent
to
Maxim Cournoyer <maxim.cournoyer <at> gmail.com>
:
bug acknowledged by developer.
(Thu, 24 Apr 2025 01:50:03 GMT)
Full text and
rfc822 format available.
Message #16 received at 78015-done <at> debbugs.gnu.org (full text, mbox):
Hi,
I found out this was a known upstream issue resolved in release 47.0 of
gnome-calendar, so I've updated to it and tested: it now works as
expected! I've updated it in commit 3c8427ca415, which
evolution-data-server updated in the previous commit for good measures.
Closing! Thanks for your co-investigations.
--
Thanks,
Maxim
This bug report was last modified today.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.