Bug 448846 - Entries in "std.ics" are incomplete: The timezone in "DTSTART" is missing
Summary: Entries in "std.ics" are incomplete: The timezone in "DTSTART" is missing
Status: CONFIRMED
Alias: None
Product: korganizer
Classification: Applications
Component: general (show other bugs)
Version: 5.18.1
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-01-20 18:55 UTC by Joerg Schiermeier
Modified: 2023-08-27 19:02 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
Event dialog (78.23 KB, image/png)
2022-01-22 23:48 UTC, Joerg Schiermeier
Details
Enter a new event with KOrganizer. (77.02 KB, image/png)
2022-01-24 00:06 UTC, Joerg Schiermeier
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Joerg Schiermeier 2022-01-20 18:55:33 UTC
First:
I use the file "std.ics" from "$HOME/.local/share/korganzier" to control my public calendar on my website.

Than:
Last week I discover that this stopped working because the stored "DTSTART" and "DTEND" have different data formats. This changed when I updated the plasma/KDE last week. Before it was working flawlessly for a lot of years.

Look at this, please:

--- [from std.ics ]---
BEGIN:VEVENT
DTSTAMP:20220120T182757Z
CREATED:20220120T182757Z
UID:b635d4a1-51dc-4a8b-b2b6-cf9b3c62078f
LAST-MODIFIED:20220120T182757Z
DESCRIPTION:Beginn: 8.00 Uhr\nEnde: 18.00 Uhr
SUMMARY:Testtermin
LOCATION:Lübbecke
CATEGORIES:privat
DTSTART:20220131T080000
DTEND;TZID=Europe/Berlin:20220131T180000
TRANSP:OPAQUE
END:VEVENT
---///---

"DTEND" has the timezone included, "DTSTART" does not.
This difference is new. I guess it's a regression.


SOFTWARE/OS VERSIONS
Operating System: Devuan GNU/Linux 5
KDE Plasma Version: 5.23.5
KDE Frameworks Version: 5.88.0
Qt Version: 5.15.2
Kernel Version: 5.15.0-2-amd64 (64-bit)
Graphics Platform: X11
Processors: 16 × AMD Ryzen 7 2700X Eight-Core Processor
Memory: 62.8 GiB of RAM
Graphics Processor: NVIDIA GeForce GTX 1660/PCIe/SSE2
Comment 1 gjditchfield 2022-01-22 23:00:44 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?
Comment 2 Joerg Schiermeier 2022-01-22 23:48:26 UTC
Created attachment 145781 [details]
Event dialog
Comment 3 Joerg Schiermeier 2022-01-23 23:57:45 UTC
(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.
Comment 4 Joerg Schiermeier 2022-01-24 00:06:30 UTC
Created attachment 145826 [details]
Enter a new event with KOrganizer.
Comment 5 Joerg Schiermeier 2022-04-16 20:10:08 UTC
This bug still exists in:

KDE Plasma Version: 5.24.4
KDE Frameworks Version: 5.90.0
Comment 6 gjditchfield 2022-04-17 03:25:26 UTC
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?
Comment 7 Joerg Schiermeier 2022-04-17 16:16:59 UTC
(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
Comment 8 gjditchfield 2022-04-21 03:10:50 UTC
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.
Comment 9 Joerg Schiermeier 2022-04-21 12:27:47 UTC
(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.
Comment 10 gjditchfield 2022-04-21 16:20:50 UTC
(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.
Comment 11 Joerg Schiermeier 2022-10-21 19:21:06 UTC
Still present in KOrganizer: v5.21.0
Comment 12 Joerg Schiermeier 2022-10-21 19:21:41 UTC
...and it now messes around in the ICS-file!
Comment 13 sourcemaker 2023-01-21 21:32:04 UTC
I can confirm this issue.
Comment 14 Daniel Vrátil 2023-08-22 06:19:07 UTC
Could you please check what version of libical do you have, just so we know it's not a regression/bug in libical?
Comment 15 Joerg Schiermeier 2023-08-27 19:02:14 UTC
(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...!