As I stated in my previous post, I suspect it is a BTRFS filesystem encoding issue for CALM. JS was 100% "future-proofed" in that regard (i.e., future operating systems), but CALM had a few holes in it.
I have plugged those holes and added more debugging information to tell us exactly what the filesystem encoding is in your system.
For my Windows 11 system:
Code:
filesystem_encoding is: utf-8
The BTRFS encoding could
easily mess with the upper/lower cases, and a lot more, including transliteration errors in paths. Think of "ASCII versus Unicode" differences.
Attached is a revised test version for you.
Please post a full debug log of your testing.
DaltonST