this post was submitted on 06 Jun 2026
75 points (98.7% liked)
Open Source
47489 readers
17 users here now
All about open source! Feel free to ask questions, and share news, and interesting stuff!
Useful Links
- Open Source Initiative
- Free Software Foundation
- Electronic Frontier Foundation
- Software Freedom Conservancy
- It's FOSS
- Android FOSS Apps Megathread
Rules
- Posts must be relevant to the open source ideology
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
- !libre_culture@lemmy.ml
- !libre_software@lemmy.ml
- !libre_hardware@lemmy.ml
- !linux@lemmy.ml
- !technology@lemmy.ml
Community icon from opensource.org, but we are not affiliated with them.
founded 6 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Is this because of the LTT Linux challenge?
Can't be, since it's labeled as a Windows bug and the Linux challenge is obviously not on Windows.
Oh you're right, I didn't read it carefully enough.
Well, it could be in the sense, that when they looked at the code to fix the issue in Linux, they realized how to fix it in Windows. So it could be indirectly responsible.
Also very unlikely, as (unmounted) network shares are accessed very differently from Windows and from Linux.
But maybe the right developer was working in that area of the code for a small fix or something, and happened to see what the issue was on Windows and knew how to fix it.
Yeah, it might be unrelated and just a coincidence. I just wanted to give another possible view. We can only speculate.