Hi Ulf, first of all, given our subscriptions succeeded, let's keep the discussion here and only here, please, which will automatically avoid HTML as well ;-) Am Dienstag, 16. Juli 2019, 15:39:08 CEST schrieb ulfbart@gmx.net:

Gesendet: Dienstag, 16. Juli 2019 um 13:07 Uhr; Von: "Hans-Peter Jansen"

...

Am Montag, 15. Juli 2019, 09:58:32 CEST schrieb ub22@xxxxxxx:

Server (NFS 4 Server which is sharing /home config via YaST): |- Client1 (/home mounted via & user via NIS)

...

Using a similar setup here.

FYI: I'm using {open,}SUSE since > 20 years as well in both, commercial and private, settings.

Yes, allways done by YasT: 1. Install NIS Client with Automount enabled

This is the automount fstab pattern, that I use now: server:/path /net/server/path nfs noauto,x-systemd.automount,x-systemd.device- timeout=10,timeo=14 0 0

On the most Clients KDE Plasma Crashes many times after login

...

Plasma runs fine here.

Depends on the user. I switched to an newer user and the Problem seams to be not available on it. I've only trouble to forward some settings like the kwallet which was encrypted with a key which seams to be on the new user in kleopatra and also in kwallet5 not visible.

If kwallet5 finds a plain kwallet4 config, it tries to convert the wallet to the new format with an assistant asking for both credentials. You need to remove the damaged kwallet5 settings beforehand. You can export/import kwallets manually as well. I've had cases with very old KDE{3,4} configs, which had some trouble as well. I tend to start with a new config then, and recover selective configs (e.g. firefox bookmarks and passwords). kmail config should be started anew.

...

A general note:

A NFS homed KDE is sub-optimal, when it comes to (heavy uses of) akonadi et.al. Thus, I'm using a different scheme for power users: I place /home on a local ssd, and symlink everything interesting from my shared server home.

akonadi on this user don't work, due to a mail account which can't be changed since years, so kmail crashes before I can open it.

Given, you get the basics behave again, you can reanimate akonadi with: rm -rf /home/$USER/.local/share/akonadi and start over again. You need to adjust the folders for all email identities in this case.

But anyway, this looks crazy, so I expect that temporary files should be used on local /tmp which is on my side always on a fast SSD

No, akonadi stores its databases in the path above. Use a symlink to relocate that one onto your local ssd.

...

server:/home /home/nfs nfs nfsvers=4,x-systemd.requires=nfs-mountd.service,x-

systemd.requires=/home 0 0

If kmail is still too slow, switch to postgresql for akonadi.

I will doublecheck this later on. So in the moment I don't use kmail anymore

I cannot confirm your experience. I'm using TW and KDE including kmail successfully in NFS shared environments, but manage users with ldap, not yp. Most data is hosted by NFS, including VBox VMs(!), and all is working well. Server: openSUSE 15.0, Clients: TW. All smooth. Cheers, Pete -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org