Bug 117700

Summary: Hundreds of errormessages when filesystem becomes unavailable
Product: [Applications] korganizer Reporter: Chris Huebsch <kde>
Component: generalAssignee: kdepim bugs <kdepim-bugs>
Status: RESOLVED UNMAINTAINED    
Severity: normal    
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Debian stable   
OS: Linux   
Latest Commit: Version Fixed In:
Attachments: This is the way my desktop looks every morning

Description Chris Huebsch 2005-12-05 08:46:46 UTC 
Version:            (using KDE KDE 3.4.0KDE 1.2)
Installed from:    I Don't KnowDebian stable Packages

We use Openafs (see www.openafs.org) as a distributed filesystem. AFS requires the local cache manager to hold a token for the user in order to be able to write into the filesystem. For security reasons the token exprires after 8 hours.

After this happens, Korganizer starts to popup messages saying, that the calendar cannot be saved. This message is repeated very often. This morning I stopped counting at 300 (!!!) and killed korganizier with xkill. This is not acceptable.

Why can't korganizer look if there is already such a messagebox open?

An option would be, closing korganizer every evening and reopen it every morning. But this is not the way of usability I knew from my paperbased organizer.
Comment 1 Chris Huebsch 2005-12-05 08:47:54 UTC 
Created attachment 13773 [details]
This is the way my desktop looks every morning
Comment 2 Reinhold Kainhofer 2006-11-02 19:15:23 UTC 
Reassigning all KOrganizer bug reports and wishes to the newly created 
korganizer-devel mailing list.
Comment 3 Denis Kurz 2016-09-24 18:46:51 UTC 
This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present?

If noone confirms this bug for a Framework-based version of korganizer (version 5.0 or later, as part of KDE Applications 15.08 or later), it gets closed in about three months.
Comment 4 Denis Kurz 2017-01-07 22:06:06 UTC 
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.