https://bugs.kde.org/show_bug.cgi?id=485205
--- Comment #4 from Paul Stansell <paulstans...@gmail.com> --- 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" -- You are receiving this mail because: You are watching all bug changes.
