Bug 337484 - hardware profile settings not saved across reboot
Summary: hardware profile settings not saved across reboot
Status: REPORTED
Alias: None
Product: Phonon
Classification: Frameworks and Libraries
Component: settings (show other bugs)
Version: 4.7.1
Platform: Ubuntu Linux
: NOR normal
Target Milestone: 4.8
Assignee: Harald Sitter
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-07-16 05:46 UTC by Amichai Rothman
Modified: 2021-03-09 22:37 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Amichai Rothman 2014-07-16 05:46:15 UTC
On Kubuntu 14.04, KDE 4.13.2, in System Settings -> Multimedia -> Audio and Video Settings -> Audio Hardware Setup, there are two options under Sound Card, both labeled 'Built-in Audio'. One of them is configured with "Analog Stereo Duplex" profile and works ok. The other has 3 profiles, all labeled "Digital Stereo (HDMI) Output" (I indeed have multiple monitors/TV connected, all from iGPU, no other video card). When selecting any of them, the Connector setting (under the Device Configuration pane below) changes between "HDMI / DisplayPort", "HDMI / DisplayPort 2" and "HDMI / DisplayPort 3" accordingly. The second one is the correct one in my configuration (TV audio output), and works ok when selected.

However, the latter setting is lost after a system reboot - the selected profile reverts back to the first one, i.e. the one whose Connector is "HDMI / DisplayPort", and the correct setting (the second one, with "HDMI / DisplayPort 2") needs to be manually configured again after every reboot.

(Note: the TV at connector 2 is usually turned off, and is turned on only occasionally. Desktop/display/geometry configuration works properly though regardless of if/when TV is turned on - and audio should do the same).
Comment 1 Justin Zobel 2021-03-09 22:37:00 UTC
Thank you for the bug report.

As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists.

If this bug is no longer persisting or relevant please change the status to resolved.