Seedance 2.5 Flash: A New Way to Create AI-Powered Videos
Content creators, marketers, and businesses are finding creating images and videos more and more effortless via AI. As…
On Ubuntu my DualSense works in Steam games but your gamepad tester in Chrome shows nothing, even after pressing buttons. Firefox also nothing. I installed Chrome as a Snap I think. What's missing?
On Linux, browsers read controllers through system input devices, and sandboxed Snap or Flatpak browsers may not be allowed to access them. Steam uses its own permissions, which is why games work. Install the browser from a regular package, or grant device access to the sandboxed one.
This is a permissions issue rather than a controller problem. On Linux, browsers read controllers from the system's input device files. Two things can block them.
Sandboxed browsers. Browsers installed as Snap or Flatpak packages run in a sandbox, and the sandbox may not include access to game controller devices. Steam has its own setup and device rules, so games work while the browser sees nothing. The quickest test is a browser installed from a regular package, or granting device access to the sandboxed one, for Flatpak for example with a tool such as Flatseal.
Device permissions. Even outside a sandbox, your user needs permission to read the controller's input device. Steam installs device rules for supported controllers on many distributions, often via a package with a name like steam-devices. If that is missing, browsers and some games cannot read the controller. Installing it and reconnecting the controller usually fixes access.
The DualSense itself is well supported on recent Linux kernels, so once permissions are right, the tester should show it with a standard layout after a button press.
Tested on: Applies to DualSense and other controllers on Ubuntu and similar distributions with Chrome and Firefox. Browser controller access per the W3C Gamepad specification.
Checked by Simon Fletcher on . How we verify answers
Open Source Contributor And Device ID Specialist at Gamepad Tester
Vikram contributes to open source Gamepad API tooling, with a focus on device identification. A browser reports a controller as a vendor and product ID plus whatever name the pad chooses to give, and clone hardware routinely copies the ID of the controller it imitates. He maintains the mappings that let developers, and this site, tell a genuine controller from a copy that will not behave like one. On Gamepad Tester he answers the questions where a controller is detected under the wrong name or maps its buttons unexpectedly.
Each answer is written by the specialist who owns that part of the hardware, tested on a real controller, and checked by a second team member. How we verify answers
Answers are free general guidance from the Gamepad Tester Team and the community. Opening a controller or replacing a thumbstick module can void your warranty, so check the maker's support or warranty first. Battery and soldering work carries a real risk of damage or injury.
Every test runs in your own browser with the Gamepad API. No sign up, no download, and your controller data never leaves your device.
Content creators, marketers, and businesses are finding creating images and videos more and more effortless via AI. As…
Ask ChatGPT how to check a controller for stick drift, or which pad to buy next, and the answer you get is no longer…
Plenty of controller blogs start the same way. You fix your own stick drift, write up what worked, and realize you…
The newest replies from players and the Gamepad Tester Team.