Vivaldi Calender setting event one day earlier
-
@eggert Thanks - one more data point, most of the time now even with always local time, Android side shows the event two hours too early. Points maybe to time zone issues as Helsinki tz is two hours off GMT.
-
I had this time shift problem in the early days of mail / calendar - module.
Now, therefore, after reading this post, I tried it out to see if it will display correctly for me.
No, it won't. At least not for a full day event. I have a full day event set to Dec 24, 2022. On the smartphone and in the webmail - Vivaldi - calendar it shows up as an event on Dec 23, so 1 day early.
I am using the latest version of Vivaldi stable, 5.6.2867.50. However, the bug also exists in the latest Vivaldi snapshot, 5.7.2887.3.
-
I also see the problem mentioned by @JyrkiKuoppala in the latest version - 5.6.2867.58 (Stable channel) (64-bit).
Steps to Reproduce:
- Add a CalDAV calendar to Vivaldi.
- Create an event in the above CalDAV calendar for 16h00 choosing a specific timezone - e.g. Asia/Calcutta (UTC+0530).
- Wait for the refresh interval, or manually refresh the calendar.
- After successful refresh, the event jumps ahead 05h30 hours, i.e. the event time is now 21h30 instead of 16h00.
I do not see this behaviour if I originate the event using Thunderbird with the same CalDAV calendar.
-
For the record, I think I have the same issue. When I add a full day Task to my Google Tasks, the same task shows up in Vivaldi a day earlier. I'm in Mountain Time GMT-7.
My understanding from this thread is the problem is recognized and yet to be addressed by an update? -
@nschloss
Hi, there are a lot of calendar fixes in the last few snapshots, may you check this one:Vivaldi 5.7 is around the corner, maybe in a week or so.
Cheers, mib
-
Thanks for this update
I'm now running 5.7.2914.3 (Official Build) (Pending update 5.7.2921.29) (64-bit) .
Tested the process again but still getting the same results - a full day Task added in Google is showing up a day earlier in Vivaldi. Maybe v5.7 will have the fix - fingers crossed! -
@nschloss
May I ask, did you install 5.7 snapshot over a 5.6 install?
If yes, you cant go back to a 5.6 version.
If you want get back to the stable version the best time is after the release of 5.7, it´s mostly a bit "newer" than the latest snapshot.Cheers, mib
-
Yes, I guess I did as I was at the latest current release version before. But I'm confused by your subsequent comments. Did I mess up installing the 5.7 snapshot over the 5.6 version? How do I go back to the v5.6 at this point? Sorry I'm not totally in tune with the process
-
@nschloss
You can install a newer version over an older but downgrade is not recommended.
The main reason is 5.6 use Chromium 108 but 5.7 use 110.
I would simply wait for the next 5.7 stable and install it over your actual install, it´t not far away, maybe a week or so.
If you want to test a snapshot use the standalone install, this is independent of a regular install.https://vivaldi.com/blog/snapshot-vs-stable/
https://help.vivaldi.com/desktop/install-update/standalone-version-of-vivaldi/
Cheers, mib
-
@nschloss @mib2berlin @eggert Tested with 5.7.2921.53 (Stable channel) stable (Ubuntu Linux), Helsinki TZ. I think there's improvement, but still at least one issue:
-
entry made with laptop full day entry for tomorrow with default tz shows up correctly on mobile - though apparently Vivaldi converts this to "always local" which might explain the difference between this and the local tz event
-
entry made on laptop for Saturday with "always local" setting shows up correctly on mobile (I think there was a two hour mismatch for this earlier)
-
however, still a bug: an entry made for today for 18.00 from Vivaldi on laptop with default tz setting (Helsinki) is shown on yesterday at 23.00
So, based on this test, assuming it's consistent behaviour (not 100% sure it's been earlier), a working workaround now is to remember to always set the option to use always local time
-
-
@JyrkiKuoppala All day events should always be "Local time" since they should always start at midnight on the given day for wherever you are in the world. This is a requirement for things to work correctly, I guess it would be sensible for us to hide the timezone for all day events since it is just a distraction in that case.
In case of a normal timed event, "always local" (or floating time event as the standard calls it) creates an event which will show up on the same local time in users calendar whatever the timezone is, that is it will show up on different absolute time based on where in the world you are. This is not really a common thing for users to want, since events tend to be something that happens at a specific point in time which can be different local time based on your location. If all your events are just local and not viewed from a different timezone then there is no difference.
Regarding your error can you give more detail please. You create a normal event with timezone set to Helsinki, does it have any recurrence, reminders or other properties set? Where does it show on 23:00 yesterday, mobile device after syncing through server? Timezone of that device is also Helsinki? What server are you using? Does the server have some kind of UI you can use to check if the event is correct there? Does the event preserve other properties, most noticably, is it the same length even if on wrong time?
Sorry if you already answered some of these questions. I read through the post, but lost track a bit, plus it is easier to have the details in one place. Thanks in advance for your help, it is most appreciated.
-
@eggert Tests have been for just a simple event, no recurrence. Reminder 30 minutes before. Synced to Android via davx5 from f-droid store. Timezone of device is also Helsinki.
What do you mean with server? davx5 connects to Vivaldi's calendar server at calendar.vivaldi.net
"Where does it show on 23:00 yesterday, mobile device after syncing through server? "
on Android mobile, both Etar calendar app and Google calendar app.
The event does not have length / duration on mobile, it's 23.00-23.00
-
@eggert said in Vivaldi Calender setting event one day earlier:
In case of a normal timed event, "always local" (or floating time event as the standard calls it) creates an event which will show up on the same local time in users calendar whatever the timezone is, that is it will show up on different absolute time based on where in the world you are. This is not really a common thing for users to want, since events tend to be something that happens at a specific point in time which can be different local time based on your location. If all your events are just local and not viewed from a different timezone then there is no difference.
Yes, I don't require that functionality (always local) - though not in other time zones often, so it doesn't bother me either. Just decided to try if it works as a workaround and it does is why I'm mentioning it. Forget if it was something someone else suggested or if I just decided to try the options which are available to see if they can be used for a workaround.
-
@eggert One more data point - event added from mobile with default time zone (Helsinki) is synced just fine to Vivald on laptop, so the bug is only from Vivaldi calendar server to mobile.
-
@JyrkiKuoppala @eggert any update on the matter?
-
@JyrkiKuoppala Unfortunately I have not been able to spend a lot of time on this and no real progress made. It is not forgotten though.
-
I have this same problem. Reproduce:
- I have calendar set up using vivaldi.net as the source.
- I can see the event correctly on both Android calendar (synced with davX5), Vivaldi calendar app, and webmail.vivaldi.net
- I open an event. I see the timezone is listed as "America/New_York"
- I change the time of an event in the Vivaldi calendar app.
- In webmail.vivaldi.net it updates correctly, but in the Android calendar app, it moves the event to 19 hours earlier.
- I modify the event in Vivaldi calendar, and this time set the timezone to "Always local time"
- The event shows correctly in the Android Calendar app.
-
@JyrkiKuoppala said in Vivaldi Calender setting event one day earlier:
@eggert Thanks - one more data point, most of the time now even with always local time, Android side shows the event two hours too early. Points maybe to time zone issues as Helsinki tz is two hours off GMT.
@eggert This phenomena continues with current snapshot. If I create a test item for 2023/03/11 and click task, start & end date line up as expected (no time, same date). If, however, I click on "Reminder" the end date instantly changes to the day BEFORE the start date. Having said that, the calendar displays the item correctly.
-
@janrif
Hi, does the fix was mentioned in the change logs?
If an internal fix is ready the sopranos and other developer test this, then snapshot, then stable.Cheers, mib
-
@mib2berlin said in Vivaldi Calender setting event one day earlier:
@janrif
Hi, does the fix was mentioned in the change logs?
If an internal fix is ready the sopranos and other developer test this, then snapshot, then stable.Cheers, mib
@mib2berlin This issue is not addressed in current change log but some work has been done on it. Since @JyrkiKuoppala refers to it and @eggert is following the thread, I thought what I had to offer might be useful information bc it demonstrates some progress has been made.