Bug 31611 - cauldron pulseaudio sound server fails to play tcp streams
Summary: cauldron pulseaudio sound server fails to play tcp streams
Status: RESOLVED INVALID
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: High major
Target Milestone: ---
Assignee: All Packagers
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-02-27 19:06 CET by Barry Jackson
Modified: 2023-03-01 23:33 CET (History)
1 user (show)

See Also:
Source RPM: pulseaudio-16.1-12.mga9.src.rpm
CVE:
Status comment:


Attachments

Description Barry Jackson 2023-02-27 19:06:07 CET
Description of problem:
As summary.
I have an rtl_airband server running 24/7 which outputs pulseaudio compatible audio streams to two Mageia computers on the LAN. My Mga8 laptop and desktop (when runnin Mga8) both play this stream as required by un-muting the application in the plasma volume control dialogue.

In Cauldron with the same settings in default.pa set manually or via paprefs there is no application shown to be playing sound.

The start-up of the user PA server seems to give a clue:

[baz@localhost ~]$ systemctl --user status pulseaudio
● pulseaudio.service - Sound Service
     Loaded: loaded (/usr/lib/systemd/user/pulseaudio.service; disabled; preset: disabled)
     Active: active (running) since Mon 2023-02-27 16:01:39 GMT; 1h 45min ago
TriggeredBy: ● pulseaudio.socket
   Main PID: 4682 (pulseaudio)
      Tasks: 9 (limit: 9395)
     Memory: 9.0M
        CPU: 522ms
     CGroup: /user.slice/user-1000.slice/user@1000.service/session.slice/pulseaudio.service
             ├─4682 /usr/bin/pulseaudio --daemonize=no --log-target=journal
             └─4701 /usr/libexec/pulse/gsettings-helper

Feb 27 16:01:39 localhost systemd[3203]: Starting pulseaudio.service...
Feb 27 16:01:39 localhost pulseaudio[4682]: Failed to open module module-esound-protocol-tcp.so: module-esound-p>
Feb 27 16:01:39 localhost pulseaudio[4682]: Failed to open module "module-esound-protocol-tcp".
Feb 27 16:01:39 localhost pulseaudio[4682]: pa_module_load() failed
Feb 27 16:01:39 localhost pulseaudio[4682]: stat('/etc/pulse/default.pa.d'): No such file or directory
Feb 27 16:01:39 localhost systemd[3203]: Started pulseaudio.service.
lines 1-18/18 (END)

Neither module-esound-protocol-tcp.so nor /etc/pulse/default.pa.d exist in any cauldron package.

I'm not sure if the above is the root cause or a red herring.
Barry Jackson 2023-02-27 19:09:02 CET

Priority: Normal => High

Comment 1 Barry Jackson 2023-02-27 19:55:30 CET
The message at the rtl_airband server for the Cauldron machine (192.168.1.65) is :
rtl_airband[483]: pulse: 192.168.1.65: connection failed: Connection refused.
Comment 2 Lewis Smith 2023-02-27 20:35:56 CET
Thank you for the report.
Unsure where to assign, so doing so globally.
CC'ing ghibo and wally in the hope they can help.

Assignee: bugsquad => pkg-bugs
CC: (none) => ghibomgx, jani.valimaa

Comment 3 Giuseppe Ghibò 2023-02-27 21:11:52 CET
How di you configured pulseaudio the first time?
Comment 4 Barry Jackson 2023-02-27 21:46:14 CET
The first time from installation?

Changed headphones to line out and increased notification level in systemsetting5 

Edited /etc/pulse/default.pa similar to my working Mga8 systems.

When this failed I reverted changes in /etc/pulse/default.pa and used paprefs to make all the changes.

Nothing worked including using a new user.

Other sound output is fine.

Any ideas?
Comment 5 Giuseppe Ghibò 2023-02-27 22:19:01 CET
but the pulseaudio process is running? ps -ef | grep pulseaudio shows something?
Comment 6 Barry Jackson 2023-02-28 10:51:19 CET
Yes
baz         3465    3215  0 09:34 ?        00:00:00 /usr/bin/pulseaudio --daemonize=no --log-target=journal

Content of /etc/pulse/default.pa with comments stripped out:

[baz@localhost ~]$ cat default.pa.raw
.fail
load-module module-device-restore
load-module module-stream-restore
load-module module-card-restore
load-module module-augment-properties
load-module module-switch-on-port-available
.ifexists module-switch-on-connect.so
load-module module-switch-on-connect
.endif
.ifexists module-udev-detect.so
load-module module-udev-detect
.else
load-module module-detect
.endif
.ifexists module-jackdbus-detect.so
.nofail
load-module module-jackdbus-detect channels=2
.fail
.endif
.ifexists module-bluetooth-policy.so
load-module module-bluetooth-policy
.endif
.ifexists module-bluetooth-discover.so
load-module module-bluetooth-discover
.endif
.ifexists module-esound-protocol-unix.so
load-module module-esound-protocol-unix
.endif
load-module module-native-protocol-unix
.ifexists module-gsettings.so
.nofail
load-module module-gsettings
.fail
.endif
load-module module-default-device-restore
load-module module-always-sink
load-module module-intended-roles
load-module module-suspend-on-idle
.ifexists module-console-kit.so
load-module module-console-kit
.endif
.ifexists module-systemd-login.so
load-module module-systemd-login
.endif
load-module module-position-event-sounds
load-module module-role-cork
load-module module-filter-heuristics
load-module module-filter-apply
.nofail
.include /etc/pulse/default.pa.d
[baz@localhost ~]$ cat /etc/pulse/default.pa.d
cat: /etc/pulse/default.pa.d: No such file or directory
[baz@localhost ~]$
Comment 7 Barry Jackson 2023-02-28 11:06:34 CET
After posting the above I noticed that this line was missing:

load-module module-native-protocol-tcp auth-ip-acl=127.0.0.1;192.168.1.0/24

Seems that paprefs does something different, however adding it (as it is in Mga8) it has made no difference.

Note I am restarting users PA server after any changes (pulseaudio -k)
Comment 8 Giuseppe Ghibò 2023-02-28 11:30:02 CET
What I noticed is that the module module-esound-protocol-tcp.so which was present in pulseaudio 14 of mga8, is no longer existing in mga9, and there is another module.
Comment 9 Barry Jackson 2023-02-28 11:50:18 CET
Yes, however in my default.pa in Mga8 module-esound-protocol-tcp is not loaded (well not by default.pa as it's commented out).

This is an interesting read: https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/1899  (it's not all about pipewire).
Comment 10 Giuseppe Ghibò 2023-02-28 11:56:26 CET
Just to know, can you try with shorewall temporarely turned down? Maybe it's rejected there.
Comment 11 Barry Jackson 2023-02-28 13:02:04 CET
Done that with firewall wide open - no difference, but I do have the correct port open anyway.
4713/tcp as in Mga8.
Jani Välimaa 2023-02-28 19:49:35 CET

CC: jani.valimaa => (none)

Comment 12 Barry Jackson 2023-03-01 23:33:00 CET
Found the problem!
I just discovered that the Mga9 install had defaulted to DCHP.
This machine has always had a fixed IP and it never crossed my mind that the IP had changed when I installed this Mga9.
tcp streams are now working so closing as INVALID Doh!

Resolution: (none) => FIXED
Status: NEW => RESOLVED

Comment 13 Barry Jackson 2023-03-01 23:33:48 CET
Invalid not fixed

Resolution: FIXED => INVALID


Note You need to log in before you can comment on or make changes to this bug.