https://bugs.kde.org/show_bug.cgi?id=379994
--- Comment #5 from Dennis Knorr <[email protected]> --- For complete documentation i add a few backtraces created at the akademy. The serversetup was done on debian 9 stretch stable with > apt install samba samba-client and configured for homes it is configured like it is described in https://wiki.debian.org/SambaServerSimple The client was a KDE Neon Developer Edition. Installation is: > apt install samba-client cifs-utils Then beware uids/gids and name and groups should be the same. This is not ultimate necessary, but you could run into strange issues while running diagnostics. Then i mount the share. > sudo mount -t cifs > -osoft,username=benutzer01,uid=1000,gid=1000,file_mode=0660,dir_mode=0770,password=Benutzer_01 > //192.168.122.150/benutzer01 /mnt/benutzer01/eins/ umounting can be done via "umount /mnt/benutzer01/eins" Then there are two options. 1. Create a symlink on Desktop to the mountpoint 2. Create a symlink in ~/shares/folder to the mountpoint Then i kill smbd and nmbd process on the server with kill -9 with a command like: ps aux | egrep -i "smbd|nmbd" | awk '{ print $2 }' | tr '\n' ' ' | xargs -IX sudo kill -9 X though this version is not working 100% properly and i hard to copy the pids and kill again. restart is done via systemctl restart smbd nmbd With the first option, the desktop freezes though there are short periodic updates. You can see that, if you activate the seconds on your desktop clock With the second option, desktop does not freeze, only if you open a file dialog in kate for example. Warning: 1. I did NOT test any more Applications at the moment 2. There's a fairly good chance, that System behaviour changes a little bit if the network device vanishes instead of killing the server. But this is more hard to test. 3. Another Test could be that the symlink is not linking to the mountpoint but to a directory or data WITHIN the mountpoint. -- You are receiving this mail because: You are watching all bug changes.
