You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Only RetroArch bugs should be filed here. Not core bugs or game bugs
This is not a forum or a help section, this is strictly developer oriented
Description
[Ubuntu 20.04 (RetroArch: Frontend for libretro -- v1.10.0 -- b71be7e --) The controllers I use do not remain connected when the state of the app changes or when playing content.]
Expected behavior
[The controller should remain connected unless manually disconnected by the user. ]
Actual behavior
[When starting RetroArch I no longer see the "Controller configured on port #1 message. Also, if I make a change to a configuration that requires an auto restart, the controller is disconnected. If I start a game, the controller is disconnected. I have unplug and re-plug the controller to the usb port to get it to work. This is consistent with any controller that I use and any USB port. Also, this is a new issue. It just recently started happening.]
Steps to reproduce the bug
[Load up RetroArch with a controller plugged in]
[try using the controller]
[Unplug the controller and plug it back in. The controller connects successfully]
[Play a game from your playlist. Upon loading the game, notice that the controller is no longer recognized by the app.]
Bisect Results
[I noticed this as an issue on Monday, this week. 1-24-2022]
Version/Commit
You can find this information under Information/System Information
Just confirming this bug, on Ubuntu 21.10 and RetroArch 1.10.0 installed from the Ubuntu store. Happens with both my USB Xbox and Logitech controllers, so it's not a controller specific issue. Using usbreset causes RetroArch to detect the controller, but it's lost again after loading content. Running "snap connect retroarch:raw-usb" doesn't help. Controllers seem to work fine outside of RetroArch.
Edit: Installed manually via PPA and now my controller seems to be detected fine, so it must be a Snap specific issue.
i had the same issue here, but figure out the bug disappear if i change to SDL2.
go to Settings > Drivers > input
change to SDL2
i havent tested much, opened and closed some content to test and it seems to be working, now i just have to connect the controller once when i open retro arch.
i will test more in the next days to make sure the bug is solved, please test if it work for you too or just here!
im using ubuntu 20.04 but i had the same bug on 14.04 and probably every version of ubuntu has this issue (at least in the snap install, steam worked just fine, but steam had other issues and i dont want to deal with 2 instalations)
[edit] just for informing, the way i figured this out was because steam was working and i knew some config must be different between both versions, then i realized steam was using SDL, i wish i had tried this before
First and foremost consider this:
Description
[Ubuntu 20.04 (RetroArch: Frontend for libretro -- v1.10.0 -- b71be7e --) The controllers I use do not remain connected when the state of the app changes or when playing content.]
Expected behavior
[The controller should remain connected unless manually disconnected by the user. ]
Actual behavior
[When starting RetroArch I no longer see the "Controller configured on port #1 message. Also, if I make a change to a configuration that requires an auto restart, the controller is disconnected. If I start a game, the controller is disconnected. I have unplug and re-plug the controller to the usb port to get it to work. This is consistent with any controller that I use and any USB port. Also, this is a new issue. It just recently started happening.]
Steps to reproduce the bug
Bisect Results
[I noticed this as an issue on Monday, this week. 1-24-2022]
Version/Commit
You can find this information under Information/System Information
Environment information
The text was updated successfully, but these errors were encountered: