Given that this bug happens when even when this is not the case you have identified the wrong causeAny NTFS volume on a PC that has Hibernation aka Fast Startup enabled will have issues with ANY file sharing method mounting them due to the 'dirty bit' being set.
In terminal on Windows powergfg /h off will address almost all situations of this. Users doing a forced power off (in Windows) will still have a dirty bit set issue.
No I mean the devs of "MX Samba Config" because that's where the bug occurs... setting the shares manually in smb.config is the fix so to me it seems fixable with some kind of workaround that someone just has not gotten to yet. Now if it's true that the cause for the bug is on the samba.org side and is unfixable.... then yes its they that I actually mean.You meant the Samba.Org developers, correct? There are many open bug reports there, a few over 14 years old relating to Windows hosts being accessed by Linux Samba clients. It is likely a priority vs resource issue but I don't speak for that project. IIRC Debian (and MX) use that project's output largely as is.
Now I am not being salty because no one is fixing it (that would be a waste of energy), I am just pointing out the problem and a manual workaround that actually works because it seemingly won't actually be fixed on the MXSC side. This bug is something that has caused a lot of frustration to a lot of people from what I can remember especially because it is so difficult to pin down at first.
Statistics: Posted by rambo919 — Fri Feb 21, 2025 1:16 am