Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 2059874

Summary: pw.conf: execvp error 'pactl': No such file or directory
Product: Red Hat Enterprise Linux 9 Reporter: Martin Krajnak <mkrajnak>
Component: pipewireAssignee: Wim Taymans <wtaymans>
Status: CLOSED ERRATA QA Contact: Martin Krajnak <mkrajnak>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 9.0CC: jkoten, lmiksik, ndegraef, tpelka, vbudikov, wtaymans
Target Milestone: rcKeywords: Triaged
Target Release: ---Flags: pm-rhel: mirror+
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: pipewire-0.3.47-2.el9_0 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 2062821 (view as bug list) Environment:
Last Closed: 2022-05-17 12:31:14 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 2062821    

Description Martin Krajnak 2022-03-02 09:02:56 UTC
Description of problem:

As @vcholasta pointed out today, there is an error message:

● pipewire-pulse.service - PipeWire PulseAudio
     Loaded: loaded (/usr/lib/systemd/user/pipewire-pulse.service; disabled; vendor preset: disabled)
     Active: active (running) since Wed 2022-03-02 07:30:27 CET; 2h 30min ago
TriggeredBy: ● pipewire-pulse.socket
   Main PID: 2500 (pipewire-pulse)
      Tasks: 2 (limit: 203431)
     Memory: 33.4M
        CPU: 25.458s
     CGroup: /user.slice/user-1000.slice/user/session.slice/pipewire-pulse.service
             └─2500 /usr/bin/pipewire-pulse

Mar 02 07:30:27 t590 systemd[2176]: Started PipeWire PulseAudio.
Mar 02 07:30:27 t590 pipewire-pulse[2505]: pw.conf: execvp error 'pactl': No such file or directory


Version-Release number of selected component (if applicable):
pipewire-0.3.47-1.el9.x86_64
pipewire-libs-0.3.47-1.el9.x86_64
pipewire-debugsource-0.3.47-1.el9.x86_64
pipewire-debuginfo-0.3.47-1.el9.x86_64
pipewire-jack-audio-connection-kit-0.3.47-1.el9.x86_64
pipewire-jack-audio-connection-kit-devel-0.3.47-1.el9.x86_64
pipewire-v4l2-debuginfo-0.3.47-1.el9.x86_64
pipewire-libs-debuginfo-0.3.47-1.el9.x86_64
pipewire-utils-debuginfo-0.3.47-1.el9.x86_64
pipewire-jack-audio-connection-kit-debuginfo-0.3.47-1.el9.x86_64
pipewire-gstreamer-debuginfo-0.3.47-1.el9.x86_64
pipewire-alsa-debuginfo-0.3.47-1.el9.x86_64
pipewire-pulseaudio-debuginfo-0.3.47-1.el9.x86_64
pipewire-devel-0.3.47-1.el9.x86_64
pipewire-v4l2-0.3.47-1.el9.x86_64
pipewire-utils-0.3.47-1.el9.x86_64
pipewire-alsa-0.3.47-1.el9.x86_64
pipewire-gstreamer-0.3.47-1.el9.x86_64
pipewire-pulseaudio-0.3.47-1.el9.x86_64
pipewire-doc-0.3.47-1.el9.x86_64

How reproducible:
always


Expected results:


Additional info:

Comment 1 Wim Taymans 2022-03-02 09:50:28 UTC
It's because it always wants to load the always-sink module:

# Extra modules can be loaded here. Setup in default.pa can be moved here
context.exec = [
    { path = "pactl"        args = "load-module module-always-sink" }
    #{ path = "pactl"        args = "load-module module-switch-on-connect" }
    #{ path = "/usr/bin/sh"  args = "~/.config/pipewire/default.pw" }
]

Maybe we should require pulseaudio-tools as a runtime dependency for pipewire-pulse.

Comment 4 Wim Taymans 2022-03-04 14:17:28 UTC
> Mar 04 07:48:12 t590 wireplumber[2205]: Failed to set scheduler settings: Operation not permitted

This is because the user does not have the right permissions to set the nice level of wireplumber. It's harmless but I don't know
of a good way to add the permissions.

Comment 9 Martin Krajnak 2022-03-14 07:28:20 UTC
[test@rhel-9 ~]$ systemctl --user status pipewire-pulse.service 
● pipewire-pulse.service - PipeWire PulseAudio
     Loaded: loaded (/usr/lib/systemd/user/pipewire-pulse.service; enabled; ve>
     Active: active (running) since Mon 2022-03-14 08:15:55 CET; 2min 10s ago
TriggeredBy: ● pipewire-pulse.socket
   Main PID: 895 (pipewire-pulse)
      Tasks: 2 (limit: 24826)
     Memory: 4.1M
        CPU: 17ms
     CGroup: /user.slice/user-1000.slice/user/session.slice/pipew>
             └─895 /usr/bin/pipewire-pulse

Mar 14 08:15:55 rhel-9 systemd[848]: Started PipeWire PulseAudio.
Mar 14 08:15:56 rhel-9 pipewire-pulse[1039]: 536870912
[test@rhel-9 ~]$ rpm -q pipewire
pipewire-0.3.47-2.el9_0.x86_64

Comment 13 errata-xmlrpc 2022-05-17 12:31:14 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (new packages: pipewire), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2022:2328