Krita and gnome and a USI stylus

Hello! Overall, very happy with my FW12. The only real papercut I’ve run into – and I expect it’s some quirk of the various software environments – involves UI elements and krita under gnome.

I’ve got an i3, running debian 13 (trixie) and gnome 48 under wayland, with krita and a penoval USI 2.0 stylus, and my bios is set to use USI for the stylus. Everything is working well, including drawing, but for some reason, specifically the UI elements inside krita the pointer – when using the stylus ONLY – registers touches slightly below and to one side of where the stylus AND THE CURSOR are displaying on the screen. I noticed it initially in the lower right corner of the display when held in landscape mode, but it’s also happening in, for example, the menus, and the window close “x”.

It’s weird. It could easily be some interaction between gnome/gtk and/or qt and/or libinput and/or usi stylus support somewhere in the stack.

Anyway. It’s a papercut, not any kind of deal-breaker, but I was curious if I’m alone in noticing this?

1 Like

Debian Trixie is not a supported distribution and the software is often quite old. I would not be surprised if that issue were fixed in more up-to-date distributions.

1 Like

I do realize it’s not a supported distro, just wondering if anybody else had run into this and under what conditions. It looks like probably not.

I have confirmed using a fedora live image that it does not show up there. The versions of gnome and krita are the same, although the kernel is different – fedora is using 6.14.0-63 and debian 13 is using 6.12.33-1. It could easily be that. Either way, it’s clearly a software issue.

1 Like

One other observation, for anybody else who stumbles across this thread – using an MPP stylus with debian trixie, krita, and gnome is showing the same behavior – the cursor is in the right place visually, drawing is working as expected, but the UI tracked location is a couple MM off (I can see this most easily in the lower right, with brush selection – the arrow cursor turns into the “i-bar” text cursor before the cursor is over the filter text box below the brush selection widget, and when that happens presses are into that text field, not the brush you are actually over.

Not sure that makes sense, haven’t had my morning caffeine.

I think krita is Qt, so I suspect this has something to do with UI scaling or something over there, or some interaction of qt and gnome/gtk.

Anyway. Confirmed with a fedora live image that it works there correctly with both USI and MPP, so it’s definitely a software thing.

3 Likes

Thanks, that’s at least a definitely useful report since I want to use my future Framework 12 with Fedora.

1 Like

Which distribution do you use?

I’m on CachyOS and I just got a USI 2.0 stylus which only draw in a very small portion of the screen far away from where I’m actually drawing, definitely misconfigured.

I then tried Ubuntu '(live image), no stylus and no touchpad.

And after that, Min (live image) and there at least the touch pad works but the stylus isn’t. I’ll keep trying if I can get Krita installed with the live medium.

I’ve been using Debian Trixie with gnome as a desktop, and the stylus misalignment only happens inside some applications, not everything, thankfully! It was confusing that I needed to swap the MPP/USI support in the bios, but in retrospect it makes sense.

Okay, that’s the first thing I did, to set USI in the Bios in preparation for the stylus.

Yesterday I tried Mint (live) with Krita and I got the exact same effect a with my already installed CachyOS, I finally decided to install Mint (its partitioning system is bad compare to CachyOS, it wipes out everything).

After installation,same result. I can use my fingers and the result is underneath the touch point, when using the stylus only an area of 2cm tall is covered, even if I draw at the top of the screen.

I have the feeling there is something to do with xinput.

I’m having the same issue with an MPP 2.0 stylus (Metapen M2), Ubuntu 25.10, and Krita 5.2.13. Linux is 6.17.0.

Ah, the issue was that I had fractional scaling turned on in Ubuntu, and set to 133%. After turning scaling off, everything works as expected.

From some quick investigation, this looks like a bug somewhere along the chain of Krita → Qt → XWayland.