Sound: ubuntu loses track of the selected output sink

[Tarmo Turunen]

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.

[Tarmo Turunen (dimarchi)]

This concerns Ubuntu 22.04.1 LTS, I forgot to mention.

[Ubuntu Foundations Team Bug Bot (crichton)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Libera.chat.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1986452/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

[Tarmo Turunen (dimarchi)]

Brian Murray has set the package, so I'm not going to touch a thing here (my thanks for the package selection).

[Sebastien Bacher (seb128)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer these questions:
* Is this reproducible?
* If so, what specific steps should we take to recreate this bug?

This will help us to find and resolve the problem.

[Tarmo Turunen (dimarchi)]

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?

[Launchpad Janitor (janitor)]

[Expired for pulseaudio (Ubuntu) because there has been no activity for 60 days.]