GNOME Bugzilla – Bug 615835
Alarm not working for authenticated calendars
Last modified: 2010-11-22 18:56:07 UTC
OS: opensuse 11.2 Evolution: 2.30.0.1 from opensuse genome factory repo Calendar: google calendar backed Since 2.29.9 alarm has stopped working. Evolution doesn't show any notification of events/meeting and hence sometimes I forget the event/meeting. It is still present in 2.30. Steps to reproduce: 1. Create event in google calendar with alarm to popup message before 10-15 mins. Actual result: Alarm not working Expected result: Alarm notification should popup.
The alarm daemon is now launched at session startup. Evolution doesn't launch it itself.
So if I'm using kde desktop, I have to add the daemon in startup?
I started evolution-alarm-notify manually from shell but still alarm notifications don't work and I get following messages in shell. ** Message: secret service operation failed: The name org.freedesktop.secrets was not provided by any .service files ** Message: secret service operation failed: The name org.freedesktop.secrets was not provided by any .service files e-data-server-ui-Message: Key file does not have group 'Passwords-MyAccount'
(In reply to comment #3) > ** Message: secret service operation failed: The name org.freedesktop.secrets > was not provided by any .service files I believe gnome-keyring recently added a D-Bus service that complies with the freedesktop "secrets" spec. But perhaps KDE offers an equivalent service in a different package? And yeah, I guess you would need to add the alarm daemon to KDE startup. The complaint we were trying to fix was that the daemon doesn't run until the first time you start Evolution in a desktop session.
I started both gnome-keyring-daemon and evolution-alarm-notify but its not working. e-data-server-ui-Message: Unable to find password(s) in keyring (Keyring reports: No matching results) e-data-server-ui-Message: Key file does not have group 'Passwords-MyAccount'
Is it correct that you are not saving password for your google calendar and you reenter it every Evolution's start? It is sort of known limitation of the evolution-alarm-notify daemon that it doesn't ask for passwords, thus it cannot open your authenticated calendar on its start, which means it cannot notify you about alarms in this calendar. Might that be the second change from the times before 2.29.91?
I do save passwords for calendar.
*** Bug 618435 has been marked as a duplicate of this bug. ***
Created attachment 171708 [details] [review] evo patch for evolution; OK, I got it finally. The alarm notify process was using wrong password component name, fixing the name everything works as expected (calendars with saved passwords are used for notifications). I also fixed couple other minor issues with the notification dialog, when I was in it.
Created commit f7ac9ca in evo master (2.91.1+) Created commit 9720f48 in evo gnome-2-32 (2.32.1+)
I looked at commit 9720f48. Compared to gnome-2-30, it has alarm-notify.ui portions that conflict and apparently require gtk 2.12. It's only the .ui file that does conflict though. The rest of the patch applies. ~sigh~ It would sure be nice if gnome-2-30 were being maintained at least for some reasonable overlap of the release of gnome-2-32. Not everyone is able to jump from 2.30 to 2.32 the moment it's released. It's not at all untypical in software development to maintain current and current-1 for the entire duration of current. But even just a few months (say, 3 perhaps -- half the life-cycle of current) would be nice.
It's kept up to the distro maintainers to decide which patches backport and which not, and how long they will support respective version. The upstream follows some schedule. Note it's harder these days, with all the changes towards gnome3 and gtk3 to backport changes (of course, this patch is not part of this group) :) Maybe you noticed that there used to be a .3 stable release (like 2.28.3) in the past, but about a year ago the release-team decided to not do .3 releases, because most distributions didn't pick it anyway, so the release-team kept decision on the upstream maintainers whether they will or will not do the .3 release. Evolution still does .3 releases, somehow.
*** Bug 634396 has been marked as a duplicate of this bug. ***