Hello Potet, or anyone else affected, Accepted gnome-calendar into disco-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gnome- calendar/3.32.2-1~ubuntu19.04.1 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-disco to verification-done-disco. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-disco. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calendar in Ubuntu. https://bugs.launchpad.net/bugs/1826400 Title: Event jumps to preceding date after edit Status in GNOME Calendar: Fix Released Status in gnome-calendar package in Ubuntu: Fix Released Status in gnome-calendar source package in Disco: Fix Committed 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://wiki.ubuntu.com/StableReleaseUpdates/GNOME [ 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 ProcVersionSignature: Ubuntu 5.0.0-11.12-generic 5.0.6 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) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-calendar/+bug/1826400/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
