ubuntustudio-bugs team mailing list archive
-
ubuntustudio-bugs team
-
Mailing list archive
-
Message #07312
[Bug 1799838] Re: Pulse Audio Volume Control defaults to wrong hardware profile and will not save under configuration section after upgrading to Ubuntu 18.10
I believe it is a combination of two separate bugs.
1.) Headphones/line-out jack detection broken:
https://gitlab.freedesktop.org/pulseaudio/pavucontrol/issues/43
As mentioned above, my Built-in-Audio profile is listed as "Analog
Stereo Duplex (unplugged)" when it is actually plugged in.
2.) Unplugging headphones changes Built in Audio profile from analog to digital
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/390
And it keeps defaulting to "Digital Stereo IEC958 Output" on each
reboot, because the Analog Stereo Duplex jack detection is broken.
--
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to pavucontrol in Ubuntu.
Matching subscriptions: Ubuntu Studio Bugs
https://bugs.launchpad.net/bugs/1799838
Title:
Pulse Audio Volume Control defaults to wrong hardware profile and will
not save under configuration section after upgrading to Ubuntu 18.10
Status in pavucontrol package in Ubuntu:
New
Bug description:
Pulse Audio Volume Control defaults to the wrong hardware profile and
will not save the selected hardware profile under the configuration
section after upgrading from Ubuntu 18.04 to 18.10.
I have HDMI out from my GPU to my desktop monitor "GP104 High
Definition Audio Controller" and "Built-in Audio" from my on-board
audio.
I typically wish to use my built-in audio which should send output to
my headphones. The problem is that on the Configuration page the
"Built-in Audio" option always defaults to "Digital Stereo IEC958
Output" when I need it to use "Analog Stereo Duplex (unplugged)".
Note: It is not actually unplugged.
I can select the analog stereo profile, but it will not save
permanently. Every time I reboot may machine it resets to "Digital
Stereo IEC958 Output".
Note: I've also tried to use the "Set as fallback" button without
success. This did not happen with 18.04.
ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: pavucontrol 3.0-4
ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
Uname: Linux 4.18.0-11-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.10-0ubuntu13
Architecture: amd64
Date: Wed Oct 24 18:01:52 2018
InstallationDate: Installed on 2018-05-10 (166 days ago)
InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
ProcEnviron:
LANGUAGE=en_US
TERM=xterm-256color
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: pavucontrol
UpgradeStatus: Upgraded to cosmic on 2018-10-20 (4 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pavucontrol/+bug/1799838/+subscriptions
References