| Summary: | Most recent calendar entries deleted when reloading the file where they are supposed to be saved | ||
|---|---|---|---|
| Product: | [Applications] korganizer | Reporter: | Paul Stansell <paulstansell> |
| Component: | general | Assignee: | kdepim bugs <kdepim-bugs> |
| Status: | REPORTED --- | ||
| Severity: | normal | CC: | dvratil |
| Priority: | NOR | ||
| Version: | 5.22.3 | ||
| Target Milestone: | --- | ||
| Platform: | Other | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: | Korganizer output log file. | ||
|
Description
Paul Stansell
2024-04-07 22:12:21 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.
(just changing status) Created attachment 168396 [details]
Korganizer output log file.
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"
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 :) 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. 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! I'm ready provide any additional information that is required. |