module-echo-cancel fails on first run

Bug #1916851 reported by Shahar Or
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
PulseAudio
New
Unknown
pulseaudio (Ubuntu)
Confirmed
Low
Unassigned

Bug Description

I have the following in `.config/pulse/default.pa`:

```
.include /etc/pulse/default.pa
load-module module-echo-cancel aec_method=webrtc aec_args="analog_gain_control=0 digital_gain_control=1"
```

After a reboot, there is no echo cancelled device.

And then I run `systemctl --user restart pulseaudio` and the echo cancelled devices appear.

That's a bit of a hassle.

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: pulseaudio 1:13.99.2-1ubuntu2.3
ProcVersionSignature: Ubuntu 5.8.0-44.50-generic 5.8.18
Uname: Linux 5.8.0-44-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu50.5
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: shahar 39906 F.... pulseaudio
 /dev/snd/controlC1: shahar 39906 F.... pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Thu Feb 25 16:05:48 2021
InstallationDate: Installed on 2010-10-12 (3788 days ago)
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
SourcePackage: pulseaudio
UpgradeStatus: Upgraded to groovy on 2020-10-25 (122 days ago)
dmi.bios.date: 10/24/2018
dmi.bios.release: 5.11
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2.1a
dmi.board.asset.tag: Default string
dmi.board.name: X10SRA
dmi.board.vendor: Supermicro
dmi.board.version: 1.01
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 17
dmi.chassis.vendor: Supermicro
dmi.chassis.version: 0123456789
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.1a:bd10/24/2018:br5.11:svnSupermicro:pnX10SRA:pvr0123456789:rvnSupermicro:rnX10SRA:rvr1.01:cvnSupermicro:ct17:cvr0123456789:
dmi.product.family: Default string
dmi.product.name: X10SRA
dmi.product.sku: Default string
dmi.product.version: 0123456789
dmi.sys.vendor: Supermicro
modified.conffile..etc.pulse.system.pa: [modified]
mtime.conffile..etc.pulse.system.pa: 2021-02-20T16:50:24.134862

Revision history for this message
Shahar Or (mightyiam) wrote :
Revision history for this message
Shahar Or (mightyiam) wrote :

I noticed that if I comment out the loading of the `module-card-restore` in `/etc/pulse/default.pa` then this problem does not occur. The echo cancelled devices are present on the first run. Of course, I do like having my cards restored!

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in pulseaudio (Ubuntu):
status: New → Confirmed
Revision history for this message
Bijay Shah (bijay135) wrote :

Hello, I got similar issue, I am using this in default.pa

### Enable echo/noise cancellation
load-module module-echo-cancel aec_method=webrtc aec_args="analog_gain_control=0 digital_gain_control=1" source_name=echocancelledsource
set-default-source echocancelledsource

It works when I use pulseaudio -k in terminal, echo cancelled sink/sources are shown and the echo cancelled source is default. This also retains on log off and re login but after a restart it does not apply at all.

For now my solution is to add a entry to gnome startup application preferences as "pulseaudio echo cancel" and use this in command "pulseaudio -k".

I tried using "sleep 5/10/30 && pulseaudio -k" as command but no matter what sleep seconds it didn't load module at all, only using the command without sleep works.

This method also retains volume/state of echo cancelled sources so it's fine for now hope it gets fixed soon officially.

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

Thank you for your bug report, the issue has also been reported upstream on https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/1195 , you might want to add your comments there

Changed in pulseaudio (Ubuntu):
importance: Undecided → Low
status: Confirmed → Triaged
Revision history for this message
Bijay Shah (bijay135) wrote :

I have added information about this issue in upstream, hoping to get some insights soon.

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

Thank you for reporting this bug to Ubuntu.
Ubuntu 20.10 (groovy) reached end-of-life on July 22, 2021.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in.

Changed in pulseaudio (Ubuntu):
status: Triaged → Won't Fix
Revision history for this message
Bijay Shah (bijay135) wrote :

I have this problem in 20.4.2 LTS as well not sure if op is still interested.

tags: added: focal
removed: groovy
Changed in pulseaudio (Ubuntu):
status: Won't Fix → Confirmed
Changed in pulseaudio:
status: Unknown → New
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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