Main Menu -> Configuration file -> Reset to Defaults: Controller disconnected

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

[Description of the bug]

Expected behavior

It would be nice to be able to use the controller when "Reset to Defaults" is activated without having to restart RetroArch.

In some OSes this is of particular importance. For example, in Chromecast with Google TV, there's no keyboard that can be used, and the voice remote that comes with the Chromecast cannot be used to navigate in RetroArch. So the only way to close Retroarch in Chromecast after you click on "Reset to Defaults", is to either press the Home button on the voice remote or to unplug/plug the electricity (if you don't have access to the voice remote), and then "Clear cache" for RetroArch in Google TV operating system. This is very inconvenient.

Actual behavior

The controller stops working. The only way to make it work again, is to close RetroArch, and then start it again.

Controllers are automatically connected to .cfg files in the retroarch/autoconfig/ (default) directory, and has nothing to do with any settings. So "Reset to Defaults" does not remove any controller setting related to connectivity.

Steps to reproduce the bug

• Main Menu -> Online Updater -> Update Controller Profiles
• Main Menu -> Quit RetroArch
• Connect a controller via Bluetooth or USB
• Start RestoArch
• Use the controller to navigate with the D-PAD and the face buttons to navigate and activate: Main Menu -> Configuration file -> Reset to Defaults

Bisect Results

[Try to bisect and tell us when this started happening]

Version/Commit

You can find this information under Information/System Information

• RetroArch: 1.16.0 Appimage

Environment information

• OS: GNU/Linux
• Compiler: [In case you are running local builds]

Reproduce the issue through Main Menu -> Configuration file -> Reset to Defaults after updating controller profiles and restarting RetroArch. Start by tracing the configuration reset flow and observe how controller input behaves afterward, including on Chromecast with Google TV. Done means the controller remains usable without restarting RetroArch.