Version: 3.5 (using KDE KDE 3.5.1) Installed from: I Don't Know OS: Linux I just began using KOrganizer to do Journal entries and realized (after losing a very lengthy journal entry...) that KOrganizer does not save the entry after the initial apply. I'm using Suse SLED 10, and my Calendar type is Local Directory. It's easy to replicate: 1. Open KOrganizer 2. Go to journal view 3. Start a journal entry for any day without one already... the journal entry popup box will appear. 4. Enter anything into the journal box. 5. Click Apply At this point, a journal file will be created in your directory, and the journal will appear in the background KOrganizer Journal view. 6. Type more in the journal entry popop that you were already writing in. 7. Click apply. You will notice that the applied journal entry is applied to the background KOrganizer Journal view, but it is NOT applied to the file. 8. Click OK in the journal entry popup that you are already typing in. Still notice that the contents you typed in step 6 are still not applied to the file. 9. Exit KOrganizer. Any information you have entered beyond the initial Apply is now gone, even if you've hit OK. I also have autosave on for KOrganizer every 1 minute, and though it shows that it's saved every minute, it has not. If before exiting KOrganizer (right after step 8), you create a file or folder in the same directory as your Local Directory location, it will delete anything after the initial Apply in KOrganizer (it just reloads the file that hasn't saved anything after the initial apply). I think I put this bug at a normal severity level. Overall in KOrganizer I would consider it normal... but for people using the journal portion (I, for now, am only using the journal portion), this is a major bug. I thought hitting apply each time I finished a paragraph was assuring a save... but instead I lost all of my journal entry except a paragraph. Also, there is no File -> Save in my KOrganizer... should there be? As a new KOrganizer user, it's hard to tell when work is saved and when it isn't. There's also no confirmation when I exit if the work should be saved. It's a bit confusing. Thanks a lot for anyones time and help with this. Aside than this, I like KOrganizer more than any other Calendar program I've tried, so I also thank anyone who has worked on it. Thanks a lot. - Darin
I also apologize if this is a duplicate, and for the fact that some aspects are unspecified. I'm new to all of this, the bugzilla system and everything. Please let me know if you all need anymore information. I'm using Suse SLED 10 x86, and KOrganizer was part of the default KDE install... so I wasn't sure what to put under installed from (source or RPM). Anyway, thanks very much again, and please let me know if I can do anything more. - Darin
Hi Darin, I am not able to reproduce this problem in the KOrganizer that comes with KDE 3.5.4. Would it be possible for you to upgrade your KDE? Can anyone else reading this bug report reproduce the bug? I don't know what you mean when you say a "journal file is created for you in your directory". Do you mean that the journal is saved into your ~/.kde/share/apps/korganizer/std.ics file? Also, saves are just done for you automatically.
Reassigning all KOrganizer bug reports and wishes to the newly created korganizer-devel mailing list.
closing due to lack of response (over 2 years) and the fact that I couldn't reproduce when I tried back then.