Bug: Mouse cursor is visible

[DesertRider]

Describe the bug
The mouse cursor is visible on the displayed pages.

To Reproduce
Steps to reproduce the behavior:
Booting the Raspberry Pi the cursor appears and never does not disappears when Chromium load and display pages.

Expected behavior
I've tested another solution (https://github.com/TOLDOTECHNIK/Raspberry-Pi-Kiosk-Display-System) with the same hardware, OS, and Chromium version, and the mouse cursor is hidden.

Environment Details
Please complete as applicable:

• Device model: Raspberry Pi 3B+
• OS & Version: Raspberry Pi OS Desktop 64-bit, Trixie 13.2
• Display: HDMI screen (Sharp TV)
• Browser: Chromium (chromium/stable 1:144.0.7559.59-1~deb13u1+rpt1 armhf)
• Kiosk Setup Method: using chromium --kiosk, Wayland

[DesertRider]

Inspired Raspberry-Pi-Kiosk-Display-System, I gave a look at the install script, I created 2 files:

/home/pi/.config/labwc/rc.xml :

<?xml version="1.0"?>
<labwc_config>
  <keyboard>
    <keybind key="W-h">
      <action name="HideCursor"/>
      <action name="WarpCursor" to="output" x="1" y="1"/>
    </keybind>
  </keyboard>
</labwc_config>

/home/pi/.config/labwc/autostart :

# Hide cursor on startup (simulate Win+H hotkey)
sleep 1 && wtype -M logo -k h -m logo &

I rebooted the Pi and the mouse cursor is gone!

[debloper]

Good news that labwc/labwc#2633 now supports hiding mouse cursor. Bad news is that there isn't a cross-compositor way to do it still. The most elegant way to do this is still a maintenance nightmare: #23 (comment)

Will mark this to be addressed in the .next release planning, but I'm think this feature request is gonna get kicked further down the road, in need of a better solution.

[Clemiax]

Hello,

is there any news on this ?

[tismofied]

Would love to know as well. I've just been plugging a mouse to my rpi, moving the mouse pointer to the corner then unplugging the mouse each time I reboot for updates. It's not ideal but it is what it is until there is a better solution lol

[debloper]

As I've touched on this before: until an elegant solution is found, this issue will stay in the fridge. Yes, there are convoluted ways to solve this, and if any of those you're happy with, that's great... but no, I'd prefer not to add disproportionate complexity (or prospective supply chain attack vector) for solving a pet peeve.

I haven't looked into finding a solution lately (in the last 6 months), so in case something has materially changed, such that this is now a trivial first party config/fix, then it's possible that I'm unaware of it. In such a case, please point me to the right directions or submit a patch, and I'll try to mend it ASAP.