Bug 474403 - Freezing Issues with Network Mount - CIFS or NFS
Summary: Freezing Issues with Network Mount - CIFS or NFS
Status: RESOLVED FIXED
Alias: None
Product: dolphin
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: Dolphin Bug Assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-09-11 12:46 UTC by Tom Strausbaugh
Modified: 2024-11-12 18:31 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Tom Strausbaugh 2023-09-11 12:46:24 UTC
SUMMARY
***
NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols.
See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***


STEPS TO REPRODUCE
1.  Setup a Network Mount (CIFS or NFS) in /etc/fstab.
Example: 10.1.10.102:/mnt/volume /mnt/volume nfs4 x-systemd.automount, x-systemd-idle-timeout=20min,_netdev 0 0

2. Mount said network mount point.
 
3. Attempt to copy a large file (I used a 20GB file) to said moint point. It may also happen with a large amount of small files but I did not attempt that.

OBSERVED RESULT

The copy dialog will appear and start to copy. It will hit a random percentage and seems like it stops copying. The dialog window and the destination dolphin with will then go grey if an attempt is made to interact with one of them. You are unable to do anything until eventually the copy/move process is complete. You are also unable to open a new dolphin window and browse the network mount point until to copy is complete.

EXPECTED RESULT

I would expect I would be able to copy a file without dolphin hanging up/freezing. I would also expect to still be able to browse the network share without any issue except maybe a little slower since a copy is occurring and using most of the network bandwidth is likely being used. So the browsing may need to wait a few moments to intercept some bandwidth.

SOFTWARE/OS VERSIONS
Windows: N/A
macOS: N/A
Linux/KDE Plasma: 

Arch Linux

KDE Plasma Version: I believe it was 5.27.7 but I can confirm at a later time (It would be the latest version that Arch Linux provides in their repos)
KDE Frameworks Version: Unsure but will confirm at a later time. (It would be the latest version that Arch Linux provides in their repos)
Qt Version: Unsure but will confirm at a later time. (It would be the latest version that Arch Linux provides in their repos)

ADDITIONAL INFORMATION

One interesting thing I came across while doing some testing was that if I browse to the share using Dolphin's built-in faculties for Samba Shares (Going to the Network Section/Pane, then typing in a Samba network address smb://10.1.10.102). It works perfectly as expected. I am able to browse the share, copy a large (20GB) file, and continue to browse the share without any issues.
Comment 1 Tom Strausbaugh 2023-09-17 03:44:53 UTC
Here are the versions of KDE software that I did not know at the time of submitting the bug.

KDE Plasma Version: 5.27.8
KDE Frameworks Version: 5.110.0
Qt Version: 5.15.10
Linux Kernel Version: 6.5.3
Comment 2 TraceyC 2024-10-30 18:05:47 UTC
Thanks for the bug report. I'm sorry we haven't been able to get to it yet.
If this is still happening on your system, can you please let us know what version of Dolphin is installed? Thanks!
Comment 3 Tom Strausbaugh 2024-11-09 16:23:03 UTC
I apologize but I have since update KDE Plasma to version 6. I do not believe I have been running into this issue anymore since updating. I have copied many files from or to NFS shares without problems now. I think this is safe to be closed at this point. Thanks.
Comment 4 TraceyC 2024-11-12 18:31:29 UTC
(In reply to Tom Strausbaugh from comment #3)
> I apologize but I have since update KDE Plasma to version 6. I do not
> believe I have been running into this issue anymore since updating. I have
> copied many files from or to NFS shares without problems now. I think this
> is safe to be closed at this point. Thanks.

Hi Tom,

Thanks for the update! I'm closing this report out. If the problem comes back, please file a new bug since a lot of things have updated.