Bug 232086 - kmail unusable/broken in enterprise environment $HOME on NFS during kmail was used same user on other client pc in the past hour
Summary: kmail unusable/broken in enterprise environment $HOME on NFS during kmail was...
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kmail
Classification: Applications
Component: general (show other bugs)
Version: 1.13.1
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks: 332624
  Show dependency treegraph
 
Reported: 2010-03-25 09:34 UTC by Juergen Sauer
Modified: 2015-04-12 10:20 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Juergen Sauer 2010-03-25 09:34:09 UTC
Version:           1.13.1 (using 4.4.1 (KDE 4.4.1), Kubuntu packages)
Compiler:          cc
OS:                Linux (i686) release 2.6.31-20-generic

According to my tests here kmail is broken and complete not usable.

This scenario is critical here.

$HOME resides on NFS Server.
if kmail was used on an user jojo i.e. on "pc2" at 8:30h and is closed at 8:45 on "pc2", it is not possible to start kmail on any other clients in the local network for that user within the next hours.

Also kmail refuses to starts for that user again, if moved back to that pc2 and closed the senseless attemts to use kmail on pc11 i.e.

(except pc2 is shut down all kde services, kdm etc and all *akonadi* processes are killed, also the sockets etc. are delete manually).

it seems to me, using akonadi makes it impossible to use kmail/kontact/kdepim in such professional environments.

used system: kubuntu 9.10 + ppa resources as mentioned on www.kde.org for ubuntu.
Comment 1 Martin Steigerwald 2014-03-26 11:04:47 UTC
Meta Bug 332624 - NFS support
Comment 2 Laurent Montel 2015-04-12 10:20:15 UTC
Thank you for taking the time to file a bug report.

KMail2 was released in 2011, and the entire code base went through significant changes. We are currently in the process of porting to Qt5 and KF5. It is unlikely that these bugs are still valid in KMail2.

We welcome you to try out KMail 2 with the KDE 4.14 release and give your feedback.