this post was submitted on 21 Nov 2025
745 points (97.5% liked)

Technology

76945 readers
3694 users here now

This is a most excellent place for technology news and articles.

Our Rules

  1. Follow the lemmy.world rules.
  2. Only tech related news or articles.
  3. Be excellent to each other!
  4. Mod approved content bots can post up to 10 articles per day.
  5. Threads asking for personal tech support may be deleted.
  6. Politics threads may be removed.
  7. No memes allowed as posts, OK to post as comments.
  8. Only approved bots from the list below, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
  9. Check for duplicates before posting, duplicates may be removed
  10. Accounts 7 days and younger will have their posts automatically removed.

Approved Bots

founded 2 years ago
MODERATORS
L3s@lemmy.world
enu@lemmy.world
technopagan@lemmy.world
L4s@lemmy.world
L3s@hackingne.ws
L4s@hackingne.ws
745
Microsoft finally admits almost all major Windows 11 core features are broken (www.neowin.net)
submitted 22 hours ago by mech@feddit.org to c/technology@lemmy.world
177 comments fedilink hide all child comments
you are viewing a single comment's thread
view the rest of the comments
[–] NoXPhasma@lemmy.world 3 points 7 hours ago* (last edited 7 hours ago) (3 children)

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.

[–] WhyJiffie@sh.itjust.works 3 points 7 hours ago (1 children)

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.

[–] NoXPhasma@lemmy.world 1 points 7 hours ago (1 children)

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.

[–] WhyJiffie@sh.itjust.works 1 points 24 minutes ago

not an isolated one, but an issue in all of these you mentioned too. this is a common design mistake devs make if they don't use the network share functions or slow storage, because they don't notice there is a problem and how severe it is

[–] lemmus@szmer.info 2 points 7 hours ago

I ain't got no problems using SFTP and SMB

[–] Trainguyrom@reddthat.com 1 points 2 hours ago

Even windows does that if the network drive is unavailable, it'll spend about 30 seconds trying to reach it before giving up. And if you accidentally try to query that network location again you get to wait another 30 seconds before you can do anything related to files