Microsoft has confirmed that Windows 11 Shell and every associated core feature and element are actually broken, and have been like this for many months.
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.
I don’t believe that is a KDE specific issue. I’ve seen it in most DE’s
It’s more of a mount/file system limitation. For whatever reason you have to explicitly tell the file system that if it can’t connect to something, to timeout.
Add a timeout to your mount rule and if it ends up being unavailable it’ll just timeout instead of freezing your file browser.
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.
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 don’t believe that is a KDE specific issue. I’ve seen it in most DE’s
It’s more of a mount/file system limitation. For whatever reason you have to explicitly tell the file system that if it can’t connect to something, to timeout.
Add a timeout to your mount rule and if it ends up being unavailable it’ll just timeout instead of freezing your file browser.