SUMMARY On X11, the file dialog in Krita would select files with a single click, and open them only on the second click. I recently switched to KDE wayland and noticed that the file picker now instantly opens files on the first click. "Enable native file dialogs" doesn't work on my system so I'm stuck with the default file picker which is difficult to use thanks to this bug. I am certain that it is a bug and not intended behaviour since it's inconsistent across platforms. STEPS TO REPRODUCE 1. Turn off "Enable native file dialogs" in Settings->Configure Krita->Miscellaneous 2. Open file picker 3. Attempt to select a file or directory by left-clicking it OBSERVED RESULT File is opened or directory is entered. EXPECTED RESULT File or directory should be selected. OS/VERSION INFORMATION: OS: Arch Linux Kernel: 6.12.49-1-lts Wayland desktop: KDE Plasma 6.4.5 X11 desktop: Xorg 21.1.18-2, bspwm 0.9.10-4 Krita Version: 5.2.13 Qt Version: 5.15.17 ADDITIONAL INFORMATION I tested Krita 5.2.13 on a KDE plasma wayland desktop (issue is present) and a bspwm x11 desktop (issue is not present). Both tests were done on the same system with the same configuration. Note I haven't tested it with the X11 version of KDE. I also tried downgrading to several older versions to see if the issue was still present. I went as far back as 5.2.6, the oldest version I have cached, and the issue was still there. All of the previous tests were done with the pacman distributed version of krita. I also tested the official krita 5.2.11 AppImage and it had the same bug.
I recall looking into a similar issue a while ago and it ended up being caused by Qt using KDE-specific configuration. Does it work as expected when you edit ~/.config/kdeglobals and under the `[KDE]` heading add `SingleClick=false`? Create the file and the heading if it doesn't exist yet. It should look something like this after you're done: [KDE] SingleClick=false
(In reply to dra.w.p.il.e+bugskde from comment #1) > I recall looking into a similar issue a while ago and it ended up being > caused by Qt using KDE-specific configuration. Does it work as expected when > you edit ~/.config/kdeglobals and under the `[KDE]` heading add > `SingleClick=false`? Create the file and the heading if it doesn't exist yet. > > It should look something like this after you're done: > > [KDE] > SingleClick=false Holy crap, that worked! Thank you so much. My kdeglobals file didn't have that line, it's strange that it's added automatically when you set the clicking behavior in the plasma settings gui
(In reply to milobit64 from comment #2) > (In reply to dra.w.p.il.e+bugskde from comment #1) > > I recall looking into a similar issue a while ago and it ended up being > > caused by Qt using KDE-specific configuration. Does it work as expected when > > you edit ~/.config/kdeglobals and under the `[KDE]` heading add > > `SingleClick=false`? Create the file and the heading if it doesn't exist yet. > > > > It should look something like this after you're done: > > > > [KDE] > > SingleClick=false > > Holy crap, that worked! Thank you so much. My kdeglobals file didn't have > that line, it's strange that it's added automatically when you set the > clicking behavior in the plasma settings gui **that it's NOT added automatically I mean
Cool, that's a workaround I guess. My suspicion is that this may an old setting not used by Plasma anymore, but Qt still interprets it. Not sufficiently familiar with KDE to determine it myself though. For anyone else wanting to look at it, the cause for Qt5 is in qtbase, qgenericunixthemes.cpp. Grep for SingleClick in there.
It's not something we can influence from within Krita, so I think we should just close this report.
What I was thinking was changing the product on this bug to whatever the correct KDE thing is so that they can decide whether to do anything about putting the setting (back?) into kdeglobals. It affects other Qt applications as well, not just Krita. But just closing it because it's an upstream issue is also fine.