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 268611 - Alarm for all-day event triggers at 0:00 UTC not local time
Alarm for all-day event triggers at 0:00 UTC not local time
Status: RESOLVED DUPLICATE of bug 558366
Product: evolution
Classification: Applications
Component: Calendar
2.0.x (obsolete)
Other All
: Normal normal
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
: 324554 (view as bug list)
Depends on:
Blocks: 327508 327510
 
 
Reported: 2004-10-21 01:07 UTC by Federico Mena Quintero
Modified: 2013-09-10 14:04 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Federico Mena Quintero 2004-10-21 01:07:28 UTC
Description of Problem:
If you create an all-day event with a relative alarm (e.g. the stock
'notify me 30 minutes before the start'), the alarm triggers at 00:00 UTC
minus 30 minutes, not at 00:00 local time minus 30 minutes.  I had an
all-day event with a -30 minute alarm, and the notification popped up at
17:30 my time; I'm 6 hours behind UTC.

Steps to reproduce the problem:
1. Create an all-day event
2. Set up an alarm for it
3. Wait

Actual Results:
The reminder shows up at 00:00 UTC minus the reminder offset.

Expected Results:
The reminder should show up at 00:00 local time minus the reminder offset.

How often does this happen? 
I just noticed it this once.

Additional Information:
This is evolution-2.0.1-1.3 as it comes with NLD.  This is related to bug
258748.
Comment 1 Rodrigo Moya 2004-12-02 10:21:48 UTC
it only happened once? Could you attach the event for which you got
the alarm at wrong time?
Comment 2 C Shilpa 2005-04-06 07:54:51 UTC
Replicable in 2.2.1
Comment 3 André Klapper 2005-05-15 22:48:58 UTC
very related to bug 304278
Comment 4 André Klapper 2005-05-17 11:28:39 UTC
sigh... also perhaps also related to bug 266845
Comment 5 Chenthill P 2006-01-12 20:55:03 UTC
*** Bug 324554 has been marked as a duplicate of this bug. ***
Comment 6 Milan Crha 2009-07-22 14:51:35 UTC
This had been fixed by patch in bug #558366, thus marking this one as a duplicate.

*** This bug has been marked as a duplicate of 558366 ***