rnote icon indicating copy to clipboard operation
rnote copied to clipboard

Stylus Primary Button working but not doing what it is configured to do in the settings

Open anonymous00365 opened this issue 2 months ago • 4 comments

Describe the bug
Lenovo 2in1 Ideapad Flex 5i 16IRU8 Laptop running CachyOS/Arch based Linux. In settings menu, primary button configured to be the rubber (or eraser, which ever you prefer), however it does not remove any of my writings. When I change from the pen tool to the rubber tool, and then press the primary button, it works as a "temporary" pen, and when I stop pressing said button, it goes back to being the rubber tool...

I have been using the secondary button as the rubber but there is the issue that when the stylus is hovering, and I press the secondary button, the rnote canvas follows the stylus??? like as if I am touching it?

Expected behavior
When pressed, the primary button should be a temporary rubber/eraser When pressed, the secondary button should not move the canvas

Desktop (please complete the following information):

  • OS: [CachyOS Arch Linux]
  • App Version: [e.g. Rnote v0.13.1-1.1]
  • Installation Source: [Archlinux Community Repo,]
  • Desktop Environment: [KDE Plasma 5]
  • Display Server: [e.g. Wayland]
  • Input Source: [On-Screen-Tablet]

anonymous00365 avatar Oct 24 '25 00:10 anonymous00365

Does the flatpak behave differently ? As you're on arch, the gtk version is probably the recent 4.20.x series, which comes with fresh new issues related to pen input on wayland.

So you can try to either downgrade gtk4 to 4.18 to test or use the flatpak version (runs on the gnome 48 sdk, with a gtk4 4.18.x version)

Doublonmousse avatar Oct 26 '25 18:10 Doublonmousse

I have the same problem on Fedora KDE plasma 43 flatpak version with my AES 1.0 setup with latest for everything

Xyndra avatar Nov 03 '25 13:11 Xyndra

Just tested it on latest git and the problem has not been solved yet

Xyndra avatar Nov 03 '25 17:11 Xyndra

Ok so the weirdest thing just happened while testing: at first, my main installed version had this problem. Then I got the latest git version, built it myself, and that also didn't work(and still doesn't). But now, when opening the main app again, it somehow works there???

Xyndra avatar Nov 03 '25 18:11 Xyndra