On Wed, 2023-01-18 at 12:13 +0000, Patrick O'Callaghan wrote: > The Google Stadia online gaming service is shutting down, and Google > have released an update to the game hardware controller to enable it > to > be used as a Bluetooth device with other platforms. See: > > https://stadia.google.com/controller/index_en_GB.html > > Basically, you plug in the controller on a USB port, Chrome detects > it, > and asks you to proceed. However, on trying to do this I get an error > message: > > Couldn’t connect to your controller because it’s currently being > used by another tab or program. > > Close any tabs or programs using the controller, then try again. > > Of course I'm not aware of running anything else that could interfere > with > this, but just in case I repeated the process on a clean account with > no > extraneous processes and it made no difference. > > How can I discover what is accessing the USB port? I can see the > device > details from dmesg but that doesn't translate directly to a /dev file > so I can't use fuser on it. Fixed by booting Windows on my laptop. It would still be interesting to know how to find what process is accessing the USB device under Linux though. poc _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
