** Changed in: chromium-browser (Ubuntu)
Status: Incomplete => New
--
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
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:
set 06 15:25:47 carlos-notebook gsd-power[2252]: Call to iio-proxy failed:
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name :1.136 was not
provided by any .service files
set 06 15:25:47 carlos-notebook upowerd[1314]: treated changed event as add on
Can you attach Chromium's stderr and the journalctl output?
** Tags added: snap
--
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
As I said chromium in the deb version works ok I tested a PPA, all snaps
of chromium and chromium based like brave have the same problem.
Even flatpak chromium if you add this command flatpak --user override
--filesystem=/run/udev:ro org.chromium.Chromium works fine.
I tested a PS4 controller
That video you linked suggests running a command that fixes the mappings
for this joystick:
https://wiki.archlinux.org/title/Gamepad#Playstation_5_(Dualsense)_controller.
This doesn't sound like a snap-specific problem. Can you reproduce in
Google Chrome installed as a deb?
** Changed in:
6 matches
Mail list logo
