Contoller not connected on startup and disconnects after loading changes or content

First and foremost consider this:

• 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 -- b71be7efd2 --) 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

1. [Load up RetroArch with a controller plugged in]
2. [try using the controller]
3. [Unplug the controller and plug it back in. The controller connects successfully]
4. [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

• RetroArch: [b71be7efd2]

Environment information

• OS: [Ubuntu 20.04]
• Compiler: [N/A]

No source file, test, or entry point is named. Reproduce on Ubuntu 20.04 with RetroArch commit b71be7efd2 by checking controller recognition at startup, after an auto-restarting configuration change, and when loading playlist content. Done means the controller remains recognized through these state changes without unplugging and reconnecting it.