Bug 382661 - touch painting not working on linux
Summary: touch painting not working on linux
Status: RESOLVED UPSTREAM
Alias: None
Product: krita
Classification: Applications
Component: General (show other bugs)
Version: git master (please specify the git hash!)
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Krita Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-07-24 15:29 UTC by animtim
Modified: 2018-05-25 08:33 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description animtim 2017-07-24 15:29:45 UTC
Touch painting is supposed to be re-enabled on git master, but it doesn't work on linux here. Though zoom and pan touch work...

Only touch related log I have is, when using touch pan and zoom:

krita.input: KisAbstractInputAction "Faire un panoramique du tableau" tried to process event data from an unhandled event type QEvent::Type(TouchUpdate)
krita.input: KisAbstractInputAction "Faire un zoom sur le tableau" tried to process event data from an unhandled event type QEvent::Type(TouchUpdate)

And if I do 
export QT_LOGGING_RULES="krita.input=true" && krita
I don't see any more touch input log.
Comment 1 wolthera 2017-07-24 15:59:14 UTC
Does work here on kde neon for what it is worth.
Comment 2 animtim 2017-07-25 09:46:55 UTC
wolthera, do you know which driver is used there for your touchscreen?

evdev or libinput (or another) ? (I'm quite sure it's using libinput here)
Comment 3 Halla Rempt 2017-11-24 10:39:03 UTC
In any case, this sounds like an issue with another component in the stack than Krita. It might even be a Qt version issue.
Comment 4 LinuxUserGD 2018-05-24 19:47:10 UTC
Touch also doesn't work for me (convertible) although it is enabled by default. I've tried it on Ubuntu and Arch Linux (using git master). Touch pan and zoom works as expected. Is this a hardware specific issue?
Comment 5 Halla Rempt 2018-05-25 08:33:43 UTC
Probably it is a hardware issue, or it is a kernel issue, or a library issue. It is, in any case, not a bug in Krita, so it is inappropriate to keep this bug open.