For what it’s worth, my KDE file browser would freeze up when I had a WebDav network drive to a server that went offline, not exactly elegant either, just opening my home folder and randomly after a second or two …… all software can bug in bad ways.
The big different is that, depending on how knowledgeable you are, you can either report the bug, you can diagnose it (check the logs, trace and profile the calls), dig in the code, patch it or try a patch someone developed for the bug, or simply ignore it and use a different file browser. That freedom is priceless.
With Windows you’re stuck waiting for the next upgrade that may or may not break something else and brings new and exciting AI and telemetry shoved into it.
That is definitely an annoyance. But the cause is not your file browser or KDE. The webdav has been mounted to the system and when an application tries to use it, it runs into a timeout. You can’t even unmount it, since that requires the system to talk to the network drive.
This is also not limited to webdav, it happens with all kinds of network drives. This is something that needs to be addressed at the core level of Linux. But I have no expertise, so no real clue where exactly.
this is a file browser or KDE issues, as file system operations shouldn’t happen on the UI thread. if it weren’t happening on the UI thread then it would keep working.
The same behavior happens for me in a different file browser (Nemo) and a different Desktop (Cinnamon). So I’m pretty confident, it is no isolated KDE issue.
For what it’s worth, my KDE file browser would freeze up when I had a WebDav network drive to a server that went offline, not exactly elegant either, just opening my home folder and randomly after a second or two …… all software can bug in bad ways.
True, I’ve experienced that bug.
The big different is that, depending on how knowledgeable you are, you can either report the bug, you can diagnose it (check the logs, trace and profile the calls), dig in the code, patch it or try a patch someone developed for the bug, or simply ignore it and use a different file browser. That freedom is priceless.
With Windows you’re stuck waiting for the next upgrade that may or may not break something else and brings new and exciting AI and telemetry shoved into it.
The main difference is KDE doesn’t make disgusting money off it, and if someone cares enough they can actually submit a fix
That’s the reason I put up with a lot of FOSS issues: “I’m not paying you for this, so it’s still a better price/result ratio than paid services”
That is definitely an annoyance. But the cause is not your file browser or KDE. The webdav has been mounted to the system and when an application tries to use it, it runs into a timeout. You can’t even unmount it, since that requires the system to talk to the network drive.
This is also not limited to webdav, it happens with all kinds of network drives. This is something that needs to be addressed at the core level of Linux. But I have no expertise, so no real clue where exactly.
I ain’t got no problems using SFTP and SMB
this is a file browser or KDE issues, as file system operations shouldn’t happen on the UI thread. if it weren’t happening on the UI thread then it would keep working.
The same behavior happens for me in a different file browser (Nemo) and a different Desktop (Cinnamon). So I’m pretty confident, it is no isolated KDE issue.