Bug 405787

Summary:	Cursor not working anymore after moving the cursor off the canvas and back
Product:	[Applications] krita	Reporter:	Takiro Ryo <takiro-kde>
Component:	Usability	Assignee:	Krita Bugs <krita-bugs-null>
Status:	RESOLVED FIXED
Severity:	normal	CC:	halla
Priority:	NOR
Version First Reported In:	git master (please specify the git hash!)
Target Milestone:	---
Platform:	Manjaro
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Takiro Ryo 2019-03-23 18:44:59 UTC

SUMMARY
If you use a tablet (wacom pro in my case) and use the stylus to move the cursor off the canvas, for example to the dockers, it stops working on the canvas. The cursor is missing (like klicking or using the side buttons) doesn't work anymore, except in the dockers.
Activating any menu item or doing something in the dockers (like changing layers) usually brings the cursor back.

Sometimes the cursor doesn't break but it's still often enough to make it hard to work with Krita at the moment.

The Tablet is working fine in other applications and outside Krita.

Might be related to Bug 405369, since they appear at the same time and moving the mouse for a second, brings back the cursor and the pen is working again.


STEPS TO REPRODUCE
1. Use the Stylus to move the cursor to the docker. Clicking anything is not needed, just hovering over some UI-Elements is usually enough.
2. Use the Stylus to move the cursor back to the canvas.
3. Try to paint.

OBSERVED RESULT
Cursor is missing, and nothing happens.

EXPECTED RESULT
Cursor should be visible and Pen-Buttons should work.

Krita 4.1.8
Operating System: Manjaro Linux 
KDE Plasma Version: 5.15.3
KDE Frameworks Version: 5.56.0
Qt Version: 5.12.1
Kernel Version: 4.19.30-1-MANJARO
OS Type: 64-bit
Processors: 8 × Intel® Core™ i7-4790 CPU @ 3.60GHz
Memory: 31,4 GiB of RAM

Comment 1 Takiro Ryo 2019-03-23 19:05:45 UTC

I just downgraded my package to Krita 4.1.7.101, everything is fine in there. So the issue was definetly introduced with 4.1.8

Comment 2 Halla Rempt 2019-03-23 19:31:49 UTC

How did you downgrade? TO an appimage, or a repo package?

The only thing that 4.1.8 has is a workaround for bugs in Qt 5.12 -- and depending on how those packages are built, yes, that workaround can introduce bugs. 

Use the appimage instead, if your distribution's packages are broken.

Comment 3 Takiro Ryo 2019-03-23 19:37:56 UTC

I downgraded to a repo package. I still had an old version in my package cache. Just did `pacman -U /var/cache/pacman/pkg/krita-4.1.7.101-2-x86_64.pkg.tar.xz`

Comment 4 Halla Rempt 2019-03-23 20:50:46 UTC

I'm sorry, but this really sounds distribution specific. Please try the appimage instead.

Comment 5 Bug Janitor Service 2019-03-24 04:33:13 UTC

Thanks for your comment!

Automatically switching the status of this bug to REPORTED so that the KDE team
knows that the bug is ready to get confirmed.

In the future you may also do this yourself when providing needed information.

Comment 6 Halla Rempt 2019-03-24 12:41:22 UTC

Bad bot...  I still need to know whether the appimage works for the reporter.

Comment 7 Takiro Ryo 2019-03-25 18:42:41 UTC

I tried the app image but the latest I could find was version 4.1.7 (https://krita.org/en/download/krita-desktop/) which is even older than my currently installed 4.1.7.101-2 (from the repositories). The app image of course works fine just as expected, since the 4.1.7.101-2 version does too. The issue only appears after upgrading to 4.1.8. To check if it doesn't affect the appimage I'd need one in version 4.1.8.

Comment 8 Bug Janitor Service 2019-03-26 04:33:12 UTC

Thanks for your comment!

Automatically switching the status of this bug to REPORTED so that the KDE team
knows that the bug is ready to get confirmed.

In the future you may also do this yourself when providing needed information.

Comment 9 Halla Rempt 2019-03-26 08:37:08 UTC

Try the nightly build: https://binary-factory.kde.org/job/Krita_Nightly_Appimage_Build/

4.1.8 only has some workarounds for tablet bugs in Qt 5.12, nothing more, but depending on the distribution, yes, tablet support might be broken. Qt 5.12 is giving us a lot of grief. The appimage uses Qt 5.9, which is known to work. 

You are not missing any functionality or bug fixes if you use the 4.1.7 appimage.

Comment 10 Halla Rempt 2019-03-26 15:29:25 UTC

Note also that the daily appimage builds have another work-around for the issues in Qt 5.12.