Desktop client uses UTC and not the timezone set in my operating system nor the settings from Nextcloud
How to use GitHub
- Please use the 👍 reaction to show that you are affected by the same issue.
- Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
- Subscribe to receive notifications on status change and new comments.
Steps to reproduce
- Try to schedule a meeting within the a talk room with the desktop client
- The time you chose will be stored in UTC on the Nextcloud server and the dialog let me chose 0-12h am/pm while my locals on the operating system and on Nextcloud are set to Germany and 24h-format.
Expected behaviour
reuse the locals and timezone either from my Nextcloud settings or from the operating system. For most people they should be the same
Actual behaviour
It uses UTC and 12h-format
Talk Desktop Client Version 1.2.3 (flatpak on Linux)
Can you add some screenshots as to where things are wrong? It works fine here:
this is how it looks like when I book a appointment with the desktop client:
Interestingly the "next meeting" in the chat room looks correct afterwards:
When I than go to the calendar you see as well that it is set to 12:00 - 13:00 UTC:
In my profile, locales are set to "German" and language to "English (US)". Locales in the calendar app are set to "Automatic (Europe/Berlin)"
By the way, i just heard that Oliver stumbled over the exact same issue today with the Mac desktop client.
Nextcloud Talk sends a notification of meeting with UTC time, instead of my personal settings timezone. Is this related?
Ah, sorry, I totally forgot about this issue. I'll have a look
@ShGKme , I think it is that problem: https://github.com/nextcloud/calendar/issues/5031#issuecomment-3307262700