# Calendar Timezone Bug #36192

**URL:** <https://help.nextcloud.com/t/calendar-timezone-bug-36192/167212>\
**Category:** ℹ️ Support\
**Tags:** github\_issue\_exists, calendar-app, nc26\
**Created:** [July 30, 2023, 7:05pm UTC](https://help.nextcloud.com/t/calendar-timezone-bug-36192/167212 "2023-07-30T19:05:30Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![hjkfsa](https://help.nextcloud.com/letter_avatar/hjkfsa/32/5_5575768a8748004e209b776fc1b2916d.png) [@hjkfsa](https://help.nextcloud.com/u/hjkfsa)\
**Post date:** [July 30, 2023, 7:05pm UTC](https://help.nextcloud.com/t/calendar-timezone-bug-36192/167212/1 "2023-07-30T19:05:30Z")

</div>

I am writing about a timezone drift for all day events notes in bug #36192 on GitHub at [https://github.com/nextcloud/server/pull/36192](https://github.com/nextcloud/server/pull/36192)

I’m just an end user, not a dev but running NC 26.0.3. The time zone drift for all day event reminders still occurs for me. Doesn’t matter if I use the personal calendar that is automatically created or a new calendar that I create. My time zone is set correctly in the nc calendar app settings app. Is this expected still?

Apologies, as I do not understand the jargon on GitHub used by devs.

If not yet fixed in the most current NC, would a bug bounty help get it done? This is essential to my workflow and happy to support development with money, since I can’t code.

---

<div class="post-metadata">

**Author:** ![tflidd](https://help.nextcloud.com/letter_avatar/tflidd/32/5_5575768a8748004e209b776fc1b2916d.png) [@tflidd](https://help.nextcloud.com/u/tflidd)\
**Post date:** [July 31, 2023, 8:27am UTC](https://help.nextcloud.com/t/calendar-timezone-bug-36192/167212/2 "2023-07-31T08:27:47Z")

</div>

The old problem that you are referring to was resolved, a fix was build an merged into the code. It should be in the NC 26 version already, and you shouldn’t see this exact issue any more.

So if you still see this issue, you can open a new bug report. I’d use the latest version (26.0.4) to avoid that this perhaps new bug was already solved. When you open a bug report, it asks you to fill out a template.

Perhaps some others can confirm that they see this bug. For myself, I didn’t get into the details to know how to reproduce it.

---

<div class="post-metadata">

**Author:** ![j-ed](https://help.nextcloud.com/user_avatar/help.nextcloud.com/j-ed/32/7281_2.png) [@j-ed](https://help.nextcloud.com/u/j-ed)\
**Post date:** [July 31, 2023, 10:21am UTC](https://help.nextcloud.com/t/calendar-timezone-bug-36192/167212/3 "2023-07-31T10:21:31Z")

</div>

I just ran some tests and it seems that TZ information is indeed still missing in all day events NC 26.0.4 and Calendar app v4.4.3.

---

<div class="post-metadata">

**Author:** ![hjkfsa](https://help.nextcloud.com/letter_avatar/hjkfsa/32/5_5575768a8748004e209b776fc1b2916d.png) [@hjkfsa](https://help.nextcloud.com/u/hjkfsa)\
**Post date:** [July 31, 2023, 2:37pm UTC](https://help.nextcloud.com/t/calendar-timezone-bug-36192/167212/4 "2023-07-31T14:37:14Z")

</div>

How to report this to get it fixed?

---

<div class="post-metadata">

**Author:** ![j-ed](https://help.nextcloud.com/user_avatar/help.nextcloud.com/j-ed/32/7281_2.png) [@j-ed](https://help.nextcloud.com/u/j-ed)\
**Post date:** [July 31, 2023, 4:06pm UTC](https://help.nextcloud.com/t/calendar-timezone-bug-36192/167212/5 "2023-07-31T16:06:40Z")

</div>

It has already been reported, see

> <https://github.com/nextcloud/server/issues/39640>
>
> \### ⚠️ This issue respects the following points: ⚠️
> 
> \- \[X\] This is a \*\*bug\*\*, no…t a question or a configuration/webserver/proxy issue.
> \- \[X\] This issue is \*\*not\*\* already reported on \[Github\](https://github.com/nextcloud/server/issues?q=is%3Aopen+is%3Aissue+label%3Abug) OR \[Nextcloud Community Forum\](https://help.nextcloud.com/) \_(I've searched it)\_.
> \- \[X\] Nextcloud Server \*\*is\*\* up to date. See \[Maintenance and Release Schedule\](https://github.com/nextcloud/server/wiki/Maintenance-and-Release-Schedule) for supported versions.
> \- \[X\] I agree to follow Nextcloud's \[Code of Conduct\](https://nextcloud.com/contribute/code-of-conduct/).
> 
> \### Bug description
> 
> The merged fix for timezone drift for all day event reminders described in bug #36192 is not working properly in NC26.0.4. See https://github.com/nextcloud/server/pull/36192
> 
> At least one other user on the nextcloud forum is describing the same. See https://help.nextcloud.com/t/calendar-timezone-bug-36192/167212
> 
> Calendar is still using server time (generally UTC) instead of calendar time zone.
> 
> \### Steps to reproduce
> 
> 1. create all day event on calendar
> 2. schedule email reminder
> 3. save event with reminders
> 
> 
> \### Expected behavior
> 
> Reminder should arrive as scheduled in users selected time zone. instead reminder is arriving based on server time zone, which is generally UTC. In other words, if reminder should arrive at 9am New York City time (America/NewYork) the day before an all day event, it arrives at 5am New York City time (America/NewYork), because New York is 4 hours later than UTC.
> 
> \### Installation method
> 
> Community Web installer on a VPS or web space
> 
> \### Nextcloud Server version
> 
> 26
> 
> \### Operating system
> 
> Debian/Ubuntu
> 
> \### PHP engine version
> 
> PHP 8.1
> 
> \### Web server
> 
> Apache (supported)
> 
> \### Database engine version
> 
> MariaDB
> 
> \### Is this bug present after an update or on a fresh install?
> 
> Fresh Nextcloud Server install
> 
> \### Are you using the Nextcloud Server Encryption module?
> 
> Encryption is Disabled
> 
> \### What user-backends are you using?
> 
> \- \[\] Default user-backend \_(database)\_
> \- \[\] LDAP/ Active Directory
> \- \[\] SSO - SAML
> \- \[\] Other
> 
> \### Configuration report
> 
> \`\`\`shell
> i dont know how to do this
> \`\`\`
> 
> 
> \### List of activated Apps
> 
> \`\`\`shell
> not sure how to do this
> \`\`\`
> 
> 
> \### Nextcloud Signing status
> 
> \`\`\`shell
> not sure how to do this
> \`\`\`
> 
> 
> \### Nextcloud Logs
> 
> \`\`\`shell
> not sure how to do this
> \`\`\`
> 
> 
> \### Additional info
> 
> none

---

<div class="post-metadata">

**Author:** ![hjkfsa](https://help.nextcloud.com/letter_avatar/hjkfsa/32/5_5575768a8748004e209b776fc1b2916d.png) [@hjkfsa](https://help.nextcloud.com/u/hjkfsa)\
**Post date:** [July 31, 2023, 4:18pm UTC](https://help.nextcloud.com/t/calendar-timezone-bug-36192/167212/6 "2023-07-31T16:18:32Z")

</div>

Thanks…I made that bug report

---

<div class="post-metadata">

**Author:** ![wwe](https://help.nextcloud.com/user_avatar/help.nextcloud.com/wwe/32/72963_2.png) [@wwe](https://help.nextcloud.com/u/wwe)\
**Post date:** [December 14, 2024, 12:50pm UTC](https://help.nextcloud.com/t/calendar-timezone-bug-36192/167212/7 "2024-12-14T12:50:38Z")

</div>


