SVN commit 513455 by osterfeld: Lock archive to avoid metakit archive corruption due to multiple write access. Usually Akregator being a KUniqueApplication avoids multiple Akregator instances accessing the archive, but there seem to be some cases where KUniqueApp is not safe enough (right after update, multiple KDE sessions, when using --nofork option). So we lock the archive like KMail does: if locking fails, show an error message to the user, giving him the possibility to either continue without archive, or to force access. As this is a severe bug (multiple write access can corrupt archives, which can make Akregator crash at startup), I think making use of the message unfreeze is justified. CCBUG: 116482 CCMAIL: