The official appimage version of Krita comes with a Qt File dialogue, it cannot be switched to the system's default File dialogue. This Qt dialogue, however, currently has a lot of broken functions. 1. Cannot adjust column width. When I hover my cursor over the edge of a column header, the cursor doesn't its icon, and thus I cannot drag to adjust the width of a column. To work around this, I have to adjust the size of the dialogue. 2. Cannot sort files by clicking on column header. The column header is not clickable. I cannot sort files because of this. However, the column can be clicked SOMETIMES. I haven't figured out its pattern. I mitigated this issue ONCE, by restarting the system. When I was writing this report, I was unable to make it work. 3. It doesn't remember the location or file type I used last time. 4. It doesn't remember the hidden state of thumbnail. 5. It doesn't remember the dialogue size. All these issues make saving many files a real chore. Tested with: krita-5.0.6-x86_64.appimage krita-5.0.7-a002764931-x86_64.appimage krita-5.1.0-prealpha-e8e7017941-x86_64.appimage Operating System: Arch Linux KDE Plasma Version: 5.24.5 KDE Frameworks Version: 5.94.0 Qt Version: 5.15.4 Kernel Version: 5.17.9-arch1-1 (64-bit) Graphics Platform: X11
That's something you'll have to report upstream...
The only bit we actually control is the preview widget.
But the Qt dialogue works fine under Windows...
Well, on Windows, the Windows native file dialog is used, not the Qt fallback one. That can't even be selected anymore as an option.
But I was able to disable the native file dialogue on Windows, there is an option for that. And thus the Qt file dialogue can be used under Windows, and it worked fine under Windows 11. I did some more tests, it seems that not only the appimage, the native krita package from ArchLinux also has a broken Qt file dialogue. So I think Krita's Qt dialogue is broken under Linux in general. I also tested this on Kdenlive and digikam, both appimage version and arch native package. All of them affected by the same issue. Can this be a packaging problem, that we need to update our builder's Qt to a newer version?
Actually, never mind my last question. Very likely to be a Qt bug at this point. I will file a report to Qt then.
I've reported the bug to Qt: https://bugreports.qt.io/browse/QTBUG-103738
Maybe I ask which version of Qt is currently used to build Krita? They said most of the issues could not be reproduced with the latest Qt 5.15.4.
5.12.12(In reply to Tyson Tan from comment #8) > Maybe I ask which version of Qt is currently used to build Krita? They said > most of the issues could not be reproduced with the latest Qt 5.15.4. 5.12.12
Thanks!