Hi Am 15.07.19 um 10:40 schrieb Markus Feilner:
I also think it's about networking issues. Maybe some caches or tmp directories hold bad / wrong information, that has happened here several times over the last years.
i use also kde and have (between 3 to 5 pc's) home's with nfs shared. i know when one system is shut down kde could be stuck on a other system. if this system was never (in this session) booted before the other was started, this will not happen. only solution i found, if stuck, restart the other system again. then shut down the before stuck system, shut down the other, restart the stuck system without the other. there are nfs parameters to avoid this but its long time in past i played with this parameters (opensuse 11.4) here is what i actual use in auto.mnt (tumbleweed 5.1.7-1-defaul) (and this work for me, except shutting down one system i have touched from another once during work and shut down later - then kde will stuck): system1home -fstype=nfs,nfsvers=3,retrans=1,retry=0,soft,intr,tcp system1:/home . . . . if i remember correct if retrans is set to 0 then it will not stuck, but be careful, maybe you lose data. -- www.becherer.de -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org