| Summary: | Entries in "std.ics" are incomplete: The timezone in "DTSTART" is missing | ||
|---|---|---|---|
| Product: | [Applications] korganizer | Reporter: | Joerg Schiermeier <kde-bug> |
| Component: | general | Assignee: | kdepim bugs <kdepim-bugs> |
| Status: | CONFIRMED --- | ||
| Severity: | normal | CC: | dvratil, gjditchfield, kde-bugzilla |
| Priority: | NOR | ||
| Version: | 5.18.1 | ||
| Target Milestone: | --- | ||
| Platform: | Other | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: |
Event dialog
Enter a new event with KOrganizer. |
||
|
Description
Joerg Schiermeier
2022-01-20 18:55:33 UTC
I haven't been able to reproduce this with the newest versions of KOrganizer and Frameworks. How did you create the event? If you used the usual "New Event dialog", were either of the start date and end date set in the "floating" time zone? Created attachment 145781 [details]
Event dialog
(In reply to gjditchfield from comment #1) > How did you create the event? If you used the usual "New Event dialog", Suppose I want to create an event at the 25th of January, 2022, 1:30 P.M. (In Germany this is 13.30 o'clock) The view is set to the weekly calendar view. Then I will click right on the 25th close to 13.00 o'clock and will choose "Create a new event". I will fill the dialogue. When ready I will hit "OK". Now is done. > were either of the start date and end date set in the "floating" time zone? I will not touch the "time zone" buttons. Created attachment 145826 [details]
Enter a new event with KOrganizer.
This bug still exists in: KDE Plasma Version: 5.24.4 KDE Frameworks Version: 5.90.0 If you click "Zeitzonen >>", what time zones does it reveal? I suspect that the Start is "floating" (I don't know the translation) and Ende is "Europe/Berlin". If that is so, the upcoming release of KOrganizer 22.04 should fix the problem. For the sake of completeness, what time zone is selected in System Settings, Regional Settings > Date & Time? (In reply to gjditchfield from comment #6) > If you click "Zeitzonen >>", what time zones does it reveal? Europe/Berlin > I suspect that the Start is "floating" (I don't know the translation) > and Ende is "Europe/Berlin". No. Both are "Europe/Berlin". There is an untranslated item called "floating". But this item wasn't selected. > For the sake of completeness, what time zone is selected in > System Settings, Regional Settings > Date & Time? Europe/Berlin I don't know much about Devuan, but I tried to reproduce this in a Docker container based on Debian Bookworm. It contains KDE Frameworks Version: 5.90.0 Qt Version: 5.15.2 KOrganizer Version 5.19.3 (21.12.3) Does that match your system? I created an event, and its dates were recorded correctly: both DTSTART and DTEND were given TZID=Europe/Berlin. I do not have any good ideas. All I can suggest now is that you add a new ICS file as a calendar, create an event in it, and see if it is recorded correctly. (In reply to gjditchfield from comment #8) > Does that match your system? I'm sorry to ask this, but didn't you read my description in https://bugs.kde.org/show_bug.cgi?id=448846#c0? Let me answer, what I wrote there: > KDE Plasma Version: 5.23.5 > KDE Frameworks Version: 5.88.0 > Qt Version: 5.15.2 and > korganizer Version: 5.18.1 > I do not have any good ideas. All I can suggest now is that > you add a new ICS file as a calendar, create an event in it, > and see if it is recorded correctly. OK. I will do it as you described above. When I shall have some results, they will be published here. (In reply to Joerg Schiermeier from comment #9) > I'm sorry to ask this, but didn't you read my description in > https://bugs.kde.org/show_bug.cgi?id=448846#c0? > > Let me answer, what I wrote there: > > KDE Plasma Version: 5.23.5 > > KDE Frameworks Version: 5.88.0 > > Qt Version: 5.15.2 I apologize. Comment #5 mentioned KDE Frameworks Version: 5.90.0; I thought you had upgraded. > > korganizer Version: 5.18.1 Thank you. The KOrganizer version is key information. Still present in KOrganizer: v5.21.0 ...and it now messes around in the ICS-file! I can confirm this issue. Could you please check what version of libical do you have, just so we know it's not a regression/bug in libical? (In reply to Daniel Vrátil from comment #14) > Could you please check what version of libical do you have, just so we know > it's not a regression/bug in libical? This is my installed version of "libical" libical3:amd64: v3.0.16-1+b1 I hope it helps...! |