Hey, > I've uploaded the logfile to https://paste.debian.net/1116151/ . Link > is valid for 3 days. I created and then deleted an event using the > process described above: select a free time period on the agenda view, > right-click to create an event, put in a simple title, close and then > delete the event by right-clicking. Again, the event spanned the whole > day. As the comment at line 107 indicates, the next line repeated over > 3000 times, so I deleted those repetitions. the log file is not very helpful, as this is the Akonadi one. Can you crate the log file from korganizer? > My guess is that something's gone evil or broken in Akonadi. I'd be > happy to wipe the database and start from scratch, but I'm not quite > sure the right way to do that. I tried deleting the calendar folder > store in Akonadi and re-adding it, but that didn't help. Don't blame Akonadi, Akonadi don't even care about the content of an event. For Akonadi this is only data, that is sent from Korganizer. Akonadi don't even parse this data. That's why Akonadi don't even know that you created a full day event or a 5 min one. Your description is more like a bug inside Korganizer. What backend you use to store those events? a local ical file, on a server, using CalDav? As those backends have very different permission systems. hefee > > I'm very grateful for your help. > > > hefee > > > > On Mittwoch, 6. November 2019 08:22:53 CET Borden Rhodes wrote: > > > I know that there have been some major upgrades to the Qt, KDE and KDE > > > PIM packages in the past few weeks. > > > > > > One of these new "features" that I just discovered in Buster is that > > > all new events that I try to create in KOrg save as full-day events no > > > matter what I enter. When I try to open the event to edit it, I cannot > > > change the time fields. > > > > > > When I look at the underlying iCal file it produces (my Akonadi store > > > is an iCal folder), there is all of this strange, extraneous time zone > > > cruft that KOrg seems to be injecting into the event. > > > > > > Is this just a growing pain that'll auto-fix as Buster gets more KDE > > > updates or is this a bug that I need to start picking apart in a > > > remote hope that someone upstream will fix it?
Attachment:
signature.asc
Description: This is a digitally signed message part.