Description of problem: We have 5 sinks 0,1,2,3,14 and pactl ignores to set the Default to the only "in human sense" useful sink (the real speakers on the soundcard ) [marius@eve ~]$ pactl list sinks short 0 alsa_output.pci-0000_01_00.1.hdmi-stereo-extra1 module-alsa-card.c s16le 2ch 48000Hz RUNNING 1 alsa_output.pci-0000_00_14.2.analog-stereo module-alsa-card.c s16le 2ch 48000Hz RUNNING 2 upnp module-null-sink.c s16be 2ch 44100Hz IDLE 3 combined module-combine-sink.c s16le 2ch 44100Hz IDLE 14 lahamain module-null-sink.c s16le 2ch 48000Hz IDLE Proof: [marius@eve ~]$ pacmd info| grep Default\ sink\ name: Default sink name: alsa_output.pci-0000_01_00.1.hdmi-stereo-extra1 [marius@eve ~]$ pactl set-default-sink 1 [marius@eve ~]$ pacmd info| grep Default\ sink\ name: Default sink name: alsa_output.pci-0000_01_00.1.hdmi-stereo-extra1 [marius@eve ~]$ pactl set-default-sink 2 [marius@eve ~]$ pacmd info| grep Default\ sink\ name: Default sink name: upnp [marius@eve ~]$ pactl set-default-sink 14 [marius@eve ~]$ pacmd info| grep Default\ sink\ name: Default sink name: lahamain [marius@eve ~]$ pactl set-default-sink 1 [marius@eve ~]$ pacmd info| grep Default\ sink\ name: Default sink name: alsa_output.pci-0000_01_00.1.hdmi-stereo-extra1 this is very annoying, because all apps revert back to the hdmi display with unconnected speakers :( Version-Release number of selected component (if applicable): pulseaudio-utils-12.2-1.fc28.x86_64
This message is a reminder that Fedora 28 is nearing its end of life. On 2019-May-28 Fedora will stop maintaining and issuing updates for Fedora 28. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '28'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 28 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
This message is a reminder that Fedora 29 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 29 on 2019-11-26. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '29'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 29 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 29 changed to end-of-life (EOL) status on 2019-11-26. Fedora 29 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.