https://bugs.kde.org/show_bug.cgi?id=422574
--- Comment #5 from K.J. Petrie <kde.b...@kjpetrie.co.uk> --- Interesting. So this is less a Windows/Linux issue and more a QT/GNU one. Two fundamentally different approaches to identifying files only exposed when someone with one understanding encounters behaviour originating from the other. The only question now is how to close this. From the QT perspective it's not seen as a bug because this is QT's intended behaviour. From a GNU perspective it's a fundamental flaw in QT which applications can't fix, so needs a can't fix/won't fix response (which is not available here). It's hardly resolved, but can't be resolved. An interesting journey, though. Thanks for getting to the bottom of it. -- You are receiving this mail because: You are watching all bug changes.
