https://bugs.kde.org/show_bug.cgi?id=363225

            Bug ID: 363225
           Summary: Sometimes the pen inputs events are locked in
                    "clicking" state on the Krita interface, and the
                    interface become unusable
           Product: krita
           Version: 3.0 Beta
          Platform: Other
                OS: Linux
            Status: UNCONFIRMED
          Severity: grave
          Priority: NOR
         Component: tablet support
          Assignee: krita-bugs-n...@kde.org
          Reporter: welc...@nylnook.com

Sorry warning : I probably don't have enough info to correctly fill this bug
report, but the buggy behaviour is so annoying and I can't continue debugging
without some guidance… 

I use Krita 3 Beta on Archlinux (Antergos distrib) build from AUR (git 8ff1a4c)
on a new shiny (since a few months) Wacom Cintiq 27 Touch tablet, with Gnome
3.20, libwacom 0.18 and xf86-input-wacom 0.32 on an AMD gpu and OpenGL enabled…

When Krita start, everything is fine : mouse events are correctly separated
from pen events and touch events.

Sometimes, and I can't figure out right now what is triggering the bug, the pen
events are locked in a sort of "drag and drop" (or continuously clicking) with
every interface element of Krita (dockers, popup palette, and so on…), but not
the Canvas. So basically the interface become barely usable, and I must stop
drawing.
Please see the attached video.
Additionally, changing window focus and coming back to Krita (see video at
1:14) directly on the canvas result in the system cursor not hiding. I can't
figure out if it's linked or not to the continuous clicking behavior.
Sometimes simply triggering a touch event resolve the issue. Sometimes I have
to close an reopen Krita. Sometimes I even have to log off my session and log
again.

There is probably some upstream issue related, but this bug occur only in Krita
3 (not 2.9), and not in Gimp or Mypaint (opening both software at the same time
prove it).

This happen quite often, and I won't be able to use Krita 3 for long if this
issue is not solved one way or another… This is happening since I'm testing
Krita 3 from several weeks. I waited to know more, but I can't find out where
to dig to be more precise.
Is there some command line tool I can use to give you a better bug report ?
what do you need me to provide ?


Thanks again for you great work !


Reproducible: Sometimes

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to