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 719739 - Flood of notifications for ancient events when adding a new calendar account via GOA
Flood of notifications for ancient events when adding a new calendar account ...
Status: RESOLVED INCOMPLETE
Product: evolution-data-server
Classification: Platform
Component: Calendar
3.10.x (obsolete)
Other Linux
: Normal normal
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2013-12-03 01:30 UTC by Adam Williamson
Modified: 2019-02-25 16:14 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Adam Williamson 2013-12-03 01:30:21 UTC 
I'm really not sure whose fault this is, so guessing at Shell as a first shot.

When I set up my Owncloud account in Online Accounts (via g-i-s or the control center, doesn't matter), I get a flood of notifications for events that passed months ago. I think a notification is generated for every single event in the calendar with an alarm set from the year dot, which seems silly. It should probably only pop up notifications for ones from the current time forward, or at most, maybe for the last 24 hours or so...but certainly not stuff that happened weeks ago :)
Comment 1 Milan Crha 2014-02-11 16:21:41 UTC 
Thanks for a bug report. I guess you face bug #710683, which may show only repeating events, even if they ended months ago. Could it be it?
Comment 2 Adam Williamson 2014-02-11 16:41:08 UTC 
Well, I just set up my OwnCloud account on a new system yesterday and got a few notifications for recent one-time events. But I'm not sure if it's as many as before. Definitely some that happened weeks ago, though, and there'd be no reason to show a notification for.

I'll try and find a few mins to check in a VM later.
Comment 3 Milan Crha 2014-02-11 17:56:09 UTC 
There didn't change anything significant in the time checking of the last notification for a calendar for a long time, the last time for 3.6.0, where was ensured that the change of the last notification time is actually saved as well. The newly created calendars use as its base time for notifications the last time when a notification was shown, regardless of the calendar, which might make sure that the notifications you get for the newly created calendar will be for time no sooner than for a notification you've got the last time. (I'm sorry if I sound silly, and being hard to decipher what I want to tell.)
Comment 4 André Klapper 2019-02-25 06:42:50 UTC 
(In reply to Adam Williamson from comment #2)
> I'll try and find a few mins to check in a VM later.

Closing this bug report as no further information has been provided. Please feel free to reopen this bug report if you can provide the information that was asked for in a previous comment and if this still happens in a recent supported version. Thanks!
Comment 5 Adam Williamson 2019-02-25 16:14:44 UTC 
Sorry, it seems I never did find those minutes =)