Just built master. When my Wacom stylus' button is used as right click to open the popup palette, it will instantly close again unless I try my best to make the button click as quick as possible. If the button is held down the palette stays until the button is released - however if the stylus is moved while the button is held, the palette will randomly close and open again. It does not happen with regular mouse click. This issue was not present in my previous build from about a week ago. Krita Version: 4.2.0-beta (git 439f570) Languages: en_US Hidpi: false Qt Version (compiled): 5.12.3 Version (loaded): 5.12.3 OS Information Build ABI: x86_64-little_endian-lp64 Build CPU: x86_64 CPU: x86_64 Kernel Type: linux Kernel Version: 5.1.3-arch1-1-ARCH Pretty Productname: Arch Linux Product Type: arch Product Version: unknown Hardware Information GPU Acceleration: auto Memory: 16006 Mb Number of Cores: 8 Swap Location: /tmp
I suspect commit ae31080ac4fa4f7a571a196bbdf2f203c6c0dc87 Author: Dmitry Kazakov <dimula73@gmail.com> Date: Tue May 21 23:52:03 2019 +0300 Fix popup palette in WinInk mode We should eat synthesized events more carefully in the popup palette. The events may come either to the triangle widget or to its parent widget, depending on the implementaiton. Therefore we use a special event filter for that (KisMouseClickEater). CCBUG:406668 Ref T10935 Dmitry, could you take a look?
That's old; this bug has been fixed since.
*** Bug 408326 has been marked as a duplicate of this bug. ***
Could you please point out where the fix is? 4.2.1 is affected according to downstream reports
I'll ask Dmitry.
Having the same issue with 4.2.0 stable and 4.1.2. The appimage version works fine though. I'm on Arch Linux. I've tried rebuilding qt-base (which is 5.12.3 in Arch) with patches mentioned here: https://phabricator.kde.org/T10838: Namely: https://codereview.qt-project.org/#/c/252182/ https://codereview.qt-project.org/#/c/258193/ https://codereview.qt-project.org/#/c/255384/ https://codereview.qt-project.org/#/c/255382/ But didn't help.
And 4.2.1? That was rebased on Qt 5.12.3, too.
(In reply to Boudewijn Rempt from comment #7) > And 4.2.1? That was rebased on Qt 5.12.3, too. Sorry. Typo: I'm having the issue withe both 4.2.0 and 4.2.1 (not 4.1.2). Tested with qt-base 5.12.3 in Arch repo, patched with the patches mentioned in my previous comment.
But not with with the appimage, right?
(In reply to Boudewijn Rempt from comment #9) > But not with with the appimage, right? Yep. Appimage version is not affected by this bug.
Okay. Do you know whether Arch adds any patches of their own to Qt?
(In reply to Boudewijn Rempt from comment #11) > Okay. Do you know whether Arch adds any patches of their own to Qt? Not that I know of. @Antonio Rojas (He's in the cc list) is probably the right person to answer this.
there's another possibility, too, now that I think of it. The appimage cannot load the KDE plasma Qt platform plugin that might be present on your systems, and that does stuff about single and double mouse clicks. If you're using plasma, does changing the single/doubleclick setting make a difference?
C
(In reply to Tyler from comment #12) > (In reply to Boudewijn Rempt from comment #11) > > Okay. Do you know whether Arch adds any patches of their own to Qt? > > Not that I know of. @Antonio Rojas (He's in the cc list) is probably the > right person to answer this. The only patch we are applying is https://code.qt.io/cgit/qt/qtbase.git/patch/?id=2947435d which I doubt has any effect on this
(In reply to Boudewijn Rempt from comment #13) > there's another possibility, too, now that I think of it. The appimage > cannot load the KDE plasma Qt platform plugin that might be present on your > systems, and that does stuff about single and double mouse clicks. If you're > using plasma, does changing the single/doubleclick setting make a difference? I'm running Gnome though.
(In reply to Tyler from comment #16) > (In reply to Boudewijn Rempt from comment #13) > > there's another possibility, too, now that I think of it. The appimage > > cannot load the KDE plasma Qt platform plugin that might be present on your > > systems, and that does stuff about single and double mouse clicks. If you're > > using plasma, does changing the single/doubleclick setting make a difference? > > I'm running Gnome though. Gnome also has its own platform plugin. Try running it with XDG_CURRENT_DESKTOP="foo" krita
(In reply to Antonio Rojas from comment #17) > (In reply to Tyler from comment #16) > > (In reply to Boudewijn Rempt from comment #13) > > > there's another possibility, too, now that I think of it. The appimage > > > cannot load the KDE plasma Qt platform plugin that might be present on your > > > systems, and that does stuff about single and double mouse clicks. If you're > > > using plasma, does changing the single/doubleclick setting make a difference? > > > > I'm running Gnome though. > > Gnome also has its own platform plugin. Try running it with > > XDG_CURRENT_DESKTOP="foo" krita No. That didn't help. Here is the output I got: Invalid profile : "/usr/share/color/icc/colord/Crayons.icc" "Crayon Colors" Invalid profile : "/usr/share/color/icc/colord/x11-colors.icc" "X11 Colors" QObject::startTimer: Timers cannot have negative intervals Traceback (most recent call last): File "<string>", line 1, in <module> ModuleNotFoundError: No module named 'sip' krita.scripting: "Traceback (most recent call last):" krita.scripting: " File \"/usr/lib/krita-python-libs/krita/__init__.py\", line 7, in <module>" krita.scripting: " from .api import *" krita.scripting: " File \"/usr/lib/krita-python-libs/krita/api.py\", line 28, in <module>" krita.scripting: " from PyKrita.krita import *" krita.scripting: "ModuleNotFoundError: No module named 'PyQt5'" krita.scripting: "Could not import krita"
Just fully updated Arch and rebuilt master and there is no difference, same behavior as when reported. (KDE 5)
It seems that when I tick the checkbox which says "Use mouse events for right- and middle-clicks..." in Tablet settings, I'm not affected by this bug anymore. Strange... I don't have to do this with the Appimage version. My tablet is this one: https://www.wacom.com/en-in/products/pen-tablets/one-by-wacom#Specifications.
Might be a difference in the way we build Qt for the appimage still... In any case, if that checkbox clears the issue for you then I guess we can close this report.
I don't have any such checkbox in my Wacom tablet settings, and I still experience this...
(In reply to Storm Engineer from comment #22) > I don't have any such checkbox in my Wacom tablet settings, and I still > experience this... The checkbox is in Krita, this workaround seems to be working fine in my box, also on arch+plasma here.
*** Bug 419022 has been marked as a duplicate of this bug. ***
The workaround works for my Wacom Intuos tablet, too. The bug is tagged as "regression". I.e. this is something which will be fixed in a future version?
The bug is closed; there's an option in the settings to workaround this issue.
(In reply to Boudewijn Rempt from comment #26) > The bug is closed; there's an option in the settings to workaround this > issue. Yes, I know and I wrote that that the workaround works for me. However, it says "regression", which sounds like it's actually something, which once worked without a workaround and could be fixed in the future. ;-)
I was tagged regression before it was closed. As in, it was regression and then it was fixed or worked around. You can see it in History.