[BUG] Stylus Use Disables Touch Functionality (+Workaround)

Issue

When initially opening Weylus on my tablet, touch functionality works fine. However, after using the stylus once, touch input stops responding, only the stylus continues to work.

• When testing for received events on the laptop using xev, i no longer see any events when touching the screen after entering that bugged state.
• Toggling uinput off and on temporarily restores touch functionality until the stylus is used again.
• Also see workaround below

Background

I frequently switch between using touch for navigating and the stylus/pen for writing and drawing within Xournal++.

Environment

• Laptop:
  • Model: Lenovo ThinkPad L480
  • OS: Arch Linux 6.6.22-lts
  • Network: Tablet connected to laptop's WiFi hotspot
  • Window Manager: i3 (Xorg) Note: Got same Issue when using Desktop-PC with same configuration
• Tablet:
  • Model: Samsung Tab S6 Lite
  • OS: Android 14, Kernel 4.14.190
  • Browser: "Samsung Internet" Version 23.0.1.1 (Default) Note: Switched to default browser, because Firefox did not differentiate between stylus and touch.
• Weylus:
  • Version 0.11.4-1 from the AUR
  • In the Web interface i have Mouse, Stylus, Touch and uinput all enabled.

Current Workaround

Opening a second web interface instance seems to resolve the issue temporarily.

Method 1 - Second Tab:

1. On PC:
   • Start Weylus
2. On Tablet:
   • Start the browser
   • Open the Weylus URL (first tab)
   • Open a new tab
   • Open the Weylus URL again (second tab)
   • Close the first tab
   • Now I can freely switch between touch and stylus as I like, and both continue to work. Note: This workaround needs to be repeated after restarting Weylus or the browser.

EDIT: Method 2 - Open on Host first:

1. On PC:
   • Start Weylus
   • Start the browser
   • Open the Weylus URL
2. On Tablet:
   • Start the browser
   • Open the Weylus URL
3. On PC:
   • Close browser
4. On Tablet:
   • Now I can freely switch between touch and stylus as I like, and both continue to work.

Bottom line: I stumbled upon a workaround that's doing the job for now, although it's a bit strange. If anyone knows why this is happening, let me know. Otherwise, maybe the workaround helps someone with a similar problem.

This issue might be related: GitHub Issue #243.