It is reproducible. In order to recreate the same environment you need a HyperX Cloud Flight S, USB version and an audio device connected to the Line Out on the motherboard, if present. In my case that is so.
This link discusses a possible solution (delayed register): https://www.reddit.com/r/HyperX/comments/fobp2s/cloud_flight_s_microphone_help_linux/ I have not tested whether it works. The workaround mentioned in the initial post does work. Do you need some logs, outputs from some commands, or an apport report in order to see my hardware, if that helps? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1986452 Title: Sound: ubuntu loses track of the selected output sink Status in pulseaudio package in Ubuntu: Incomplete Bug description: Whenever I'm on Ubuntu the audio loses track of the selected output device (Line Out - Built-in Audio), and does not save the selected output when restarting (and perhaps re-logging, I have not tried this). Having several output options to choose from the system apparently chooses the first detected device (in my case, HyperX Cloud Flight S, an USB device). HyperX Cloud Flight S is appropriately selected as the input device. This was present in 20.04 LTS, as well, but not in 18.04 LTS. Workaround: open the Sound Settings, select the correct output device and keep the Settings window with the Sound settings selected minimized on the Favorites. If you select some other settings or close the Settings Ubuntu will lose track of the output device in a few seconds. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1986452/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
