switch-on-connect mistakes startup for USB hotplug, so seemingly ignores the old default device on reboot

Bug #1877194 reported by Ma H
58
This bug affects 9 people
Affects Status Importance Assigned to Milestone
PulseAudio
Unknown
Unknown
pulseaudio (Ubuntu)
Low
Unassigned

Bug Description

Similar to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1847570

Only difference is that it does not reset to HDMI output, but to one of my USB-outputs. It does not respect the change I made after reboot.

In short:
1. Boot system
2. "Analogue Output - RODE NT-USB" is selected by default. I want to use "Line Out - Built-in Audio", which I choose.
3. Reboot.
4 Output device is now back to "Analogue Output - RODE NT-USB".

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: pulseaudio 1:13.99.1-1ubuntu3
ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
Uname: Linux 5.4.0-29-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC2: marcus 1604 F.... pulseaudio
 /dev/snd/controlC0: marcus 1604 F.... pulseaudio
 /dev/snd/controlC1: marcus 1604 F.... pulseaudio
 /dev/snd/pcmC1D0c: marcus 1604 F...m pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Wed May 6 23:40:08 2020
InstallationDate: Installed on 2020-05-06 (0 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
SourcePackage: pulseaudio
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/27/2017
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 3703
dmi.board.asset.tag: Default string
dmi.board.name: MAXIMUS VIII HERO
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3703:bd12/27/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnMAXIMUSVIIIHERO:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

Revision history for this message
Ma H (mah-dvlpr) wrote :
description: updated
description: updated
Ma H (mah-dvlpr)
description: updated
Ma H (mah-dvlpr)
description: updated
Ma H (mah-dvlpr)
description: updated
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

We configure PulseAudio by default to automatically choose hotplugged devices so it might be thinking booting with USB counts as hotplugging. To avoid this you should just be able to comment out:

  load-module module-switch-on-connect

from /etc/pulse/default.pa

Changed in pulseaudio (Ubuntu):
status: New → Incomplete
Revision history for this message
Ma H (mah-dvlpr) wrote :

Hi Daneil!

Commenting out "load-module module-switch-on-connect" in /etc/pulse/default.pa did indeed work.

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

OK, thanks. So it's kind of working as designed and kind of not...

If you would like to get this fixed then please open a new bug upstream:

  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues

with a title like:

  switch-on-connect mistakes startup for USB hotplug

Changed in pulseaudio (Ubuntu):
importance: Undecided → Low
summary: - Selected audio output device not persistent between reboots (Resets to
- USB-device)
+ switch-on-connect mistakes startup for USB hotplug
Changed in pulseaudio (Ubuntu):
status: Incomplete → Triaged
Revision history for this message
Ma H (mah-dvlpr) wrote : Re: switch-on-connect mistakes startup for USB hotplug

Seems reasonable.

Created an issue: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/886

Thank you for the help.

Revision history for this message
Sebastien Bacher (seb128) wrote :

Thanks

Revision history for this message
Adam Niedling (krychek) wrote :
Revision history for this message
Ma H (mah-dvlpr) wrote :

Yes, I thought so too. I even linked it in the description. Since the issue persists after the supposed fix however, it is still an issue.

Matthew M. Dean (fireculex), for example, also still has issues (see the other ticket, second to last comment).

As mentioned by Daniel van Vugt (vanvugt), on the last comment, if there still are issues -> create a new ticket, which I did.

I guess the major difference is that in my case it is a USB-device and not an HDMI.

tags: added: groovy
summary: - switch-on-connect mistakes startup for USB hotplug
+ switch-on-connect mistakes startup for USB hotplug, so seemingly ignores
+ the old default device on reboot
tags: removed: groovy
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.