[krita] [Bug 363225] Qt5 under Linux get stuck in "clicking" state, and Krita become unusable

[Boudewijn Rempt via KDE Bugzilla]

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

Boudewijn Rempt  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|CONFIRMED   |RESOLVED

--- Comment #25 from Boudewijn Rempt  ---
Okay, this is related to allowing touch events on Linux. Now that that has been
disabled, this can no longer happen...

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

[krita] [Bug 363225] Qt5 under Linux get stuck in "clicking" state, and Krita become unusable

[Camille Bissuel via KDE Bugzilla]

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

--- Comment #24 from Camille Bissuel  ---
Hi Dimitry,

sorry if I have been unclear.

Yes, I ran the Appimage (and the Alpha 2 equally). they both work, as my
packaged Krita.
But none of these are actually correctly enabling touch events, so I can't
reproduce the bug. Since I reinstalled my system (see comment 19), I lose touch
events support, but the bug is not occuring.

So my guess is that there is a library or setting missing to enable touch
events in Qt or Krita, because they work in Gnome, but I don't know which one
despite my blind tentatives with various packages to enable it again.

Said in another way : before I was able to zoom in and out smoothly into Krita
3 with my fingers, now I can't (touch event are really rarely detected, and are
really lagging), and I don't now how to enable it again, so I can't reproduce
my own bug anymore.

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

[krita] [Bug 363225] Qt5 under Linux get stuck in "clicking" state, and Krita become unusable

[Dmitry Kazakov via KDE Bugzilla]

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

--- Comment #23 from Dmitry Kazakov  ---
Hi, Camille!

I didn't understood, were you able to to run the AppImage in the end? The point
is that AppImage has a patched version of Qt, so it should work differently
from what is compiled using the system library. Here is the link to the latest
AppImage present:

http://files.kde.org/krita/3/linux/devbuilds/krita-3.0.1-Alpha2-d33dbe0-x86_64.appimage

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

[krita] [Bug 363225] Qt5 under Linux get stuck in "clicking" state, and Krita become unusable

[Camille Bissuel via KDE Bugzilla]

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

--- Comment #22 from Camille Bissuel  ---
@Dimitry
I can't reproduce with the Appimage, because I didn't found which QT package is
responsible for a real touch input since I reinstalled my whole distribution (I
can't pinch to zoom in Krita now)...  And I'm not really wanting to try… to be
able to continue using Krita 3 ... 

But, if you can say to me which package or setting I should install or enabled,
I'll try... !

In the meanwhile, I noticed a little note in the Input-wacom 0.32 release : 
https://sourceforge.net/p/linuxwacom/mailman/message/35257555/
" Fix a Cintiq 27QHD touch issue"

So maybe it's fixed, I'm waiting for the package (linux kernel) to land stable
on archlinux...

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

[krita] [Bug 363225] Qt5 under Linux get stuck in "clicking" state, and Krita become unusable

[Tyson Tan via KDE Bugzilla]

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

--- Comment #21 from Tyson Tan  ---
Also related to this bug is Bug 363283. I'm using appimage 3.0.1 beta on Ubuntu
Gnome 16.04.1. That bug still happens from time to time, although it doesn't
feel as frequent as when I reported it, or it's just because I've found a very
easy work around for it -- when it stuck to cursor mode, move the cursor out of
the canvas and then move back -- it's free now.

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

[krita] [Bug 363225] Qt5 under Linux get stuck in "clicking" state, and Krita become unusable

[Dmitry Kazakov via KDE Bugzilla]

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

Dmitry Kazakov  changed:

   What|Removed |Added

 CC||dimul...@gmail.com

--- Comment #20 from Dmitry Kazakov  ---
Hi, Camille! Did you try to run AppImage version of Krita? The point is, into
AppImage we put a patched version of Qt, with some tablet-related bugs fixed.
Does it also happen with AppImage?

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

[krita] [Bug 363225] Qt5 under Linux get stuck in "clicking" state, and Krita become unusable

[wolthera via KDE Bugzilla]

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

wolthera  changed:

   What|Removed |Added

 Status|UNCONFIRMED |CONFIRMED
 Ever confirmed|0   |1
 CC||griffinval...@gmail.com

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

[krita] [Bug 363225] Qt5 under Linux get stuck in "clicking" state, and Krita become unusable

[Camille Bissuel via KDE Bugzilla]

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

--- Comment #19 from Camille Bissuel  ---
Another user (Jasper Mattsson) confirmed this is also happening with a Lenovo
Thinkpad Yoga S13 : https://bugreports.qt.io/browse/QTBUG-54085

In a desperate attempt (because this is really annoying for my daily work), I
wiped and reinstalled my Linux distribution (Antergos) entirely, reinstalling
only the Gnome desktop environment and Krita and Scribus dependencies on the Qt
side (attica-qt5, libdbusmenu-qt5, phonon-qt5, phonon-qt5-vlc, polkit-qt5,
qt5-base, qt5-declarative, qt5-script, qt5-svg, qt5-tools, qt5-x11extras,
qt5-xmlpatterns, sonnet).

Interestingly, touch events aren't detected in Krita now (I can't pinch to zoom
for example), but they are on the Gnome side. I suppose there is one (Qt) lib
missing, I don't know which one. Any idea ?
And after a week of daily work I can say the bug is not occurring without touch
events. If something similar happen, any new click will "unlock" the clicking
state. So this is happening, but no need to restart X to stop it.

So this is really an upstream bug, do we close here ? At least it should be
marked as confirmed (I can't do it)...

Thanks again !

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

[krita] [Bug 363225] Qt5 under Linux get stuck in "clicking" state, and Krita become unusable

[Camille Bissuel via KDE Bugzilla]

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

--- Comment #18 from Camille Bissuel  ---
Thanks Tyson !

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

[krita] [Bug 363225] Qt5 under Linux get stuck in "clicking" state, and Krita become unusable

[Tyson Tan via KDE Bugzilla]

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

Tyson Tan  changed:

   What|Removed |Added

 CC||tyson...@mail.com

--- Comment #17 from Tyson Tan  ---
I can reproduce Comment8, too. But in my case, only a middle click can release
Krita from the move lock state.

Tested on Ubuntu Gnome Edition 16.04, Krita 3.0 from Krita Lime PPA, Intuos4.

I don't have a touch sensitive tablet so I couldn't test comment7.

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

[krita] [Bug 363225] Qt5 under Linux get stuck in "clicking" state, and Krita become unusable

[Camille Bissuel via KDE Bugzilla]

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

--- Comment #16 from Camille Bissuel  ---
So, what can I do to help more ? Do you need more logs ? On which hardware did
you try to reproduce ?

What do you think of Jason Gerecke insight : 
"It almost sounds like Qt is dropping events from other
devices once the pen comes in proximity, and doesn't always properly
clean up their state by releasing any buttons that may have been pressed."

Is Krita dropping events from other devices when the pen enter detection ?

Thanks again for your hard work !

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

[krita] [Bug 363225] Qt5 under Linux get stuck in "clicking" state, and Krita become unusable

[Boudewijn Rempt via KDE Bugzilla]

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

Boudewijn Rempt  changed:

   What|Removed |Added

Summary|QT5 under Linux get stuck   |Qt5 under Linux get stuck
   |in "clicking" state, and|in "clicking" state, and
   |Krita become unusable   |Krita become unusable

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

[krita] [Bug 363225] QT5 under Linux get stuck in "clicking" state, and Krita become unusable

[Boudewijn Rempt via KDE Bugzilla]

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

--- Comment #15 from Boudewijn Rempt  ---
This might still be a bug in krita, since we handle tablet evens on Linux
outside Qt. But we re-use the Qt code, so the bug might come from there. I
haven't been able to reproduce the bug myself, though.

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

[krita] [Bug 363225] QT5 under Linux get stuck in "clicking" state, and Krita become unusable

[Camille Bissuel via KDE Bugzilla]

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

Camille Bissuel  changed:

   What|Removed |Added

Version|3.0 Beta|3.0

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

[krita] [Bug 363225] QT5 under Linux get stuck in "clicking" state, and Krita become unusable

[Camille Bissuel via KDE Bugzilla]

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

--- Comment #14 from Camille Bissuel  ---
After a discussion on the Linux Wacom mailing list :
https://sourceforge.net/p/linuxwacom/mailman/message/35151033/
Jason Gerecke, the Linux Wacom maintainer was able to reproduce on a Cintiq 24
HD Touch and confirmed it's probably a Qt bug. 
I just started a Qt bug report here :
https://bugreports.qt.io/browse/QTBUG-54085

 Any confirmation from others Krita users would be welcome though ;)

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

[krita] [Bug 363225] QT5 under Linux get stuck in "clicking" state, and Krita become unusable

[Camille Bissuel via KDE Bugzilla]

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

--- Comment #13 from Camille Bissuel  ---
I installed the latest plasma desktop, tested Krita with it and the bug
occurred, and the whole Plasma desktop became totally stuck in clicking state.
So I was clicking  everywhere by simply hovering any interface.

This bug is driving me crazy, and basically I'll need to abandon Krita if this
is not fixed a way or another… : I can't spend several hours a day rebooting
because of this.
I understand this is linked to some upstream bug, but can you PLEASE give me
some advice on how to report this correctly and where in the QT/KDE maze ?

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

[krita] [Bug 363225] QT5 under Linux get stuck in "clicking" state, and Krita become unusable

[Camille Bissuel via KDE Bugzilla]

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

Camille Bissuel  changed:

   What|Removed |Added

Summary|Sometimes the pen inputs|QT5 under Linux get stuck
   |events are locked in|in "clicking" state, and
   |"clicking" state on the |Krita become unusable
   |Krita interface, and the|
   |interface become unusable   |

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