Hi, I found this bug while investigating the Chromium bug https://crbug.com/1359677
I'm guessing this is caused by Chromium's use of udev for device enumeration. Gamepad API on Linux uses udev to enumerate devices in the joydev, evdev, and hidraw subsystems. flatpak has a similar problem: https://github.com/flathub/org.chromium.Chromium/issues/40 "Unfortunately we're mostly stuck like this for now, since Chromium expects to read devices from udev, which cannot be directly exposed into the sandbox due to having an unstable ABI." As noted up-thread, there's a flatpak workaround that involves configuring the udev filesystem to be read-only. I'd like to fix this by removing Chromium's dependency on udev. Is there an alternative that plays nicely with snap/flatpak sandboxing? ** Bug watch added: github.com/flathub/org.chromium.Chromium/issues #40 https://github.com/flathub/org.chromium.Chromium/issues/40 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1988660 Title: snap doesn't map joystick buttons correctly Status in chromium-browser package in Ubuntu: Incomplete Bug description: I tested the deb version and works fine. Steps to reproduce the problem: 1.Connect the PS4 joystick by Bluetooth in Linux 2.Test mapping in a webpage like gamepad-tester.com 3.Almost all buttons are incorrectly mapped Problem Description: The buttons of the joystick are incorrectly mapped in the browser and this makes impossible to play Stadia, even the right axis remain always pressed when you press R2 once, you can see the error by yourself at this short video: https://www.youtube.com/watch?v=VLPQkXyVAsM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1988660/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
