Bug 485205 - Most recent calendar entries deleted when reloading the file where they are supposed to be saved
Summary: Most recent calendar entries deleted when reloading the file where they are s...
Status: REPORTED
Alias: None
Product: korganizer
Classification: Applications
Component: general (show other bugs)
Version: 5.22.3
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-04-07 22:12 UTC by Paul Stansell
Modified: 2024-05-09 19:35 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
Korganizer output log file. (221.25 KB, text/plain)
2024-04-11 15:33 UTC, Paul Stansell
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Paul Stansell 2024-04-07 22:12:21 UTC
SUMMARY

Most recent calendar entries deleted (about 15 hours worth) when reloading the file where they are supposed to be saved.


STEPS TO REPRODUCE
1. Right click on the name of the calendar in the bottom left pane.
2. Click "calendar properties".
3. Observer the file name where the calendar is supposed to be saved.
4. Click "okay" (or maybe it was "apply").
5. Observe the calendar reloading with the all the recent entries absent.

OBSERVED RESULT

Most recent calendar entries are deleted.


EXPECTED RESULT

No loss of recent entries.


SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Debian Bookworm 6.6.20+rpt-rpi-v8 (64-bit)
(available in About System)
KDE Plasma Version: 5.27.5
KDE Frameworks Version: 5.103.0
Qt Version: 5.15.8

ADDITIONAL INFORMATION

I want to backup the .ics file where my calendar entries are saved.  According the "calendar properties" they are saved in a .ics file in a subdirectory of my home directory which I backup.  However, it seems that the changes are not being saved regularly to that file.  I made numerous changes, but the time stamp of the file didn't change.  I exited korganizer and still the time stamp of the .ics file didn't change.  I restarted korganizer and all the most recent additions where there, but still the ics file was too old to be saving those recent additions.  Then did what I described in "STEPS TO REPRODUCE" and it seems that the old ics file was reloaded and  I lost all the recent changes that I'd made (which was about 15 hours worth). 

Where are the changes being saved, if not in the file in the "File Name" box in the "calendar properties"?  I'd like to know so that I can back up my calendar files.  I'd like to be able to force any changes I make to a calendar to be written to a named ics file that I can backup (without having to export that file as an ics file because I backup many times a day).
Comment 1 Daniel Vrátil 2024-04-10 19:41:08 UTC
Hmm, this is weird, any changes should be written into the iCal file immediately. I suspect there might be some deeper problem with your Akonadi (also considering your other bug report).

Could you please run the following commands in terminal and create one or two new events in KOrganizer?

    akonadictl stop
    QT_LOGGING_RULES="*=true;qt.*=false" korganizer &> log.txt

Once done, please attach the log.txt file here (double-check the log for any personal data before uploading it) so we can try to better understand what might be wrong.
Comment 2 Daniel Vrátil 2024-04-10 19:45:40 UTC
(just changing status)
Comment 3 Paul Stansell 2024-04-11 15:33:38 UTC
Created attachment 168396 [details]
Korganizer output log file.
Comment 4 Paul Stansell 2024-04-11 15:37:00 UTC
Hello Danial,

Thanks for helping with this.

Since I was already running korganizer from the command line, I noticed that when I choose "File > Quit" it didn't actually stop korganizer running, it just closed the window.  And when I started it again, by clicking on the icon that I have on my panel, it opened the a korganizer window for the program that I originally started at the command in a console.

This helps me understand why I could previously "quit" korganizer without it updating my .ics file with the new events, yet those new events were present when I restarted the korganizer.  It implies that korganizer wasn't actually stopping, it was still running in the background, and caching the new events somewhere that wasn't in the .ics file.  This explains why, when I reloaded the .ics the new events were lost (because the ics file was not up-to-date).

Anyway, to start korganizer, I did the following:

> killall korganizer
> akonadictl stop
> QT_LOGGING_RULES="*=true;qt.*=false" korganizer &> log.txt

I've uploaded the log.txt file.  These are the lines I got when I try, but fail, to paste an event:

"Invalid parent collection"
org.kde.pim.akonadiserver: Error while handling command CreateItem on connection korganizer-3257944331 (0x55bd6ce520)
kf.notifications: Calling notify on "Sound"
kf.notifications: Calling notify on "Taskbar"
org.kde.pim.korganizer: Incidence not added, job reported error:  "Invalid parent collection"
Comment 5 Daniel Vrátil 2024-04-15 06:30:52 UTC
Thanks for the debug log. I regret to say that I can't see anything else in the logs that would help narrow down the problem.

Btw I just noticed: 
Linux/KDE Plasma: Debian Bookworm 6.6.20+rpt-rpi-v8 (64-bit)

You are running on aarch64 RPI? I wonder whether there could be some ARM-specific issue,  I think this is the first time I actually hear from someone running KOrganizer and Akonadi on Arm :)
Comment 6 Paul Stansell 2024-04-15 18:29:09 UTC
I'm running on a Raspberry Pi 4B with 4GB of RAM.  From my experience to date, it seems to work pretty well, apart from this problem that's stopped me from using korganizer.  If you can think of any other tests I could run, I'd be happy to try them as it's easy for me to clone the SD card and experiment with different settings or run different tests.
Comment 7 Bug Janitor Service 2024-04-30 03:45:54 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 8 Paul Stansell 2024-04-30 07:35:46 UTC
I'm ready provide any additional information that is required.