Event jumps to preceding date after edit
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
GNOME Calendar |
Fix Released
|
Unknown
|
|||
gnome-calendar (Ubuntu) |
Fix Released
|
High
|
Iain Lane | ||
Disco |
Fix Released
|
High
|
Iain Lane |
Bug Description
[ Description ]
Upstream release 3.32.2
NEWS:
Major changes in 3.32.2:
* Fix timezone handling of all day events (Florian Latifi)
Major changes in 3.32.1:
* Fix release date field in AppData
* Updated translations
[ QA ]
Test the calendar works. Test that integration with the rest of the system works (which happens via e-d-s). Check that Google account syncing works.
You do *not* have to QA the original bug (preserved below), under the terms of the micro release exception:
https:/
[ Regression potential ]
If this is really bad it could break the calendar application itself completely, but shouldn't break any parts of the wider system since all integration is via other components.
[ Original report ]
Full-day events jump a date back if edited and saved, even when no information about date or time is changed. Tested in local and Google calendars, happens in both.
To reproduce:
1. Create a full-day event (say on May 5)
2. Click on the event to open event editor
3. Keep the date and time unchanged (full day, May 5)
4. Press "Finish"
5. The event is now registered as a full-day event on the previous date, in this case May 4.
Tested on several events in different months, the result is always the same. I reproduced the bug in both month and week view.
ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: gnome-calendar 3.32.0-1
ProcVersionSign
Uname: Linux 5.0.0-11-generic x86_64
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Apr 25 14:17:07 2019
InstallationDate: Installed on 2018-05-09 (350 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
SourcePackage: gnome-calendar
UpgradeStatus: Upgraded to disco on 2019-04-03 (21 days ago)
Changed in gnome-calendar: | |
status: | Unknown → New |
Changed in gnome-calendar (Ubuntu Disco): | |
status: | New → In Progress |
importance: | Undecided → Medium |
importance: | Medium → High |
assignee: | nobody → Iain Lane (laney) |
Changed in gnome-calendar (Ubuntu): | |
assignee: | nobody → Iain Lane (laney) |
status: | Triaged → In Progress |
Changed in gnome-calendar: | |
status: | New → Fix Released |
Changed in gnome-calendar (Ubuntu): | |
status: | In Progress → Fix Committed |
Thank you for your bug report, that's an issue in Disco indeed (doesn't happen in 18.04), I've reported it upstream /gitlab. gnome.org/ GNOME/gnome- calendar/ issues/ 384
https:/