https://bugs.kde.org/show_bug.cgi?id=445065
Bug ID: 445065 Summary: Dolphin gets stuk when using Samba after the NAS falls asleep Product: dolphin Version: 21.08.3 Platform: Other OS: Linux Status: REPORTED Severity: grave Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: j...@van-spaandonk.nl CC: kfm-de...@kde.org Target Milestone: --- Created attachment 143273 --> https://bugs.kde.org/attachment.cgi?id=143273&action=edit system log showing a problem with dolphin - the kde file system SUMMARY I use a QNAP NAS wit a samba filesystem, the drives are mounted via fstab - see below. Sometimes, but not always, Dolphin gets stuck when writing or reading NAS files. This problem occurs much more in the last one or two months. Also I often get a 1 to 2 -second delay when I first click on a NAS directory in Dolphin. (This occurs mainly in the last month or so separate issue, not topic of this bug report). I realize that this situation difficult to reproduce for the typical developer working on a local filesystem on a laptop. Let me know what extra info I need to provide / what experiments to do to stabilize the network scenario for KDE. I gave the bug a high priority since it prevents the use of KDE in a professional environment with networked storage. STEPS TO REPRODUCE 1. Try to open or save a file on the NAS, mounted with smb, especially after it has fallen asleep 2. 3. OBSERVED RESULT Dolphin stuck, everything using the file system stuck, such as the upload dialog window for creating this bug report. If I open a konsole window then I can normally access the NAS. After a while the whole of KDE freezes and I I cannot shutdown the PC anymore because after a while nothing reacts anymore in KDE, the keyboard does not work anymore, only the mouse cursor still moves. EXPECTED RESULT 1. If the NAS is sleeping I expect a delay of up to 10 seconds for the NAS drives to spin up and the NAS, and thus KDE, to react again. 2. I expect a message from Dolphin that a network storage is not responding / Dolphin and KDE as a whole should never get stuck due to a network problem. (This has always always the main problem for me with KDE since I started using it on a daily basis some 20 years ago) SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION The last line shows how the relevant NAS directory is mounted # <file system> <mount point> <type> <options> <dump> <pass> # / was on /dev/sdc2 during installation UUID=440e0d66-6a8d-4c7d-b0e4-7db611d24385 / ext4 errors=remount-ro 0 1 # /boot/efi was on /dev/sdc1 during installation #UUID=C2C4-CCA8 /boot/efi vfat umask=0077 0 1 /swapfile none swap sw 0 0 # ssd data directory, for downloads, thunderbird email, dropbox UUID=d4f31c28-01ee-4252-bde7-671b459317fe /media/ssd_data ext4 rw 0 2 # QNAP TS219P+ //192.168.1.2/data /media/nas_data cifs user=xxxx,password=xxxx,rw,user,nosuid,uid=1000,gid=100,_netdev,vers=1.0 0 0 -- You are receiving this mail because: You are watching all bug changes.