Fedora 38 not using Pipewire

Ask Fedora
, , , , , ,
1

Hey! Yesterday I switched to Pulseaudio by entering this command: sudo dnf swap --allowerasing pipewire-pulseaudio pulseaudio, which is written on the Fedora WiKi. Then after testing it, I tried to switch back to Pipewire by entering this command: sudo dnf swap --allowerasing pulseaudio pipewire-pulseaudio, which I found here. But from then, it shows Pulseaudio on Alsamixer, instead of Pipewire. But it says PulseAudio (on PipeWire 0.3.71) when I enter pactl info command*.*

I thought it was fine but as I wasn’t sure about it, I booted up in a live environment from ISO to check and it says Pipewire on Alsamixer and PulseAudio (on PipeWire 0.3.71) at pactl info command.

What’s the issue here? How can I use Pipewire?

Here’s my system info:

Operating System: Fedora Linux 38
KDE Plasma Version: 5.27.5
KDE Frameworks Version: 5.107.0
Qt Version: 5.15.10
Kernel Version: 6.3.8-200.fc38.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 4 × AMD Ryzen 3 3200G with Radeon Vega Graphics
Memory: 13.6 GiB of RAM
Graphics Processor: AMD Radeon Vega 8 Graphics
Manufacturer: Micro-Star International Co., Ltd.
Product Name: MS-7C52
System Version: 1.0

Alsamixer
Alsamixer1131×845 43.4 KB

Pactl
Pactl1131×845 65.6 KB

2

Please check what kind of output you get:

systemctl --user status pipewire*

If something is marked red (in bash) you have to look that it works again.

Mine looks like this:

systemctl --user status pipewire*
● pipewire-pulse.service - PipeWire PulseAudio
     Loaded: loaded (/usr/lib/systemd/user/pipewire-pulse.service; disabled; preset: disabled)
    Drop-In: /usr/lib/systemd/user/service.d
             └─10-timeout-abort.conf
     Active: active (running) since Sun 2023-06-25 12:12:19 -03; 16min ago
TriggeredBy: ● pipewire-pulse.socket
   Main PID: 2166 (pipewire-pulse)
      Tasks: 2 (limit: 18421)
     Memory: 8.1M
        CPU: 475ms
     CGroup: /user.slice/user-1000.slice/user@1000.service/session.slice/pipewire-pulse.service
             └─2166 /usr/bin/pipewire-pulse

Jun 25 12:12:19 fe38 systemd[1804]: Started pipewire-pulse.service - PipeWire PulseAudio.

● pipewire-pulse.socket - PipeWire PulseAudio
     Loaded: loaded (/usr/lib/systemd/user/pipewire-pulse.socket; enabled; preset: enabled)
     Active: active (running) since Sun 2023-06-25 12:12:16 -03; 16min ago
   Triggers: ● pipewire-pulse.service
     Listen: /run/user/1000/pulse/native (Stream)
     CGroup: /user.slice/user-1000.slice/user@1000.service/app.slice/pipewire-pulse.socket

Jun 25 12:12:16 fe38 systemd[1804]: Listening on pipewire-pulse.socket - PipeWire PulseAudio.

● pipewire.socket - PipeWire Multimedia System Socket
     Loaded: loaded (/usr/lib/systemd/user/pipewire.socket; enabled; preset: enabled)
     Active: active (running) since Sun 2023-06-25 12:12:16 -03; 16min ago
   Triggers: ● pipewire.service
     Listen: /run/user/1000/pipewire-0 (Stream)
     CGroup: /user.slice/user-1000.slice/user@1000.service/app.slice/pipewire.socket

Jun 25 12:12:16 fe38 systemd[1804]: Listening on pipewire.socket - PipeWire Multimedia System Socket.

● pipewire.service - PipeWire Multimedia Service
     Loaded: loaded (/usr/lib/systemd/user/pipewire.service; disabled; preset: disabled)
    Drop-In: /usr/lib/systemd/user/pipewire.service.d
             └─00-uresourced.conf
             /usr/lib/systemd/user/service.d
             └─10-timeout-abort.conf
     Active: active (running) since Sun 2023-06-25 12:12:17 -03; 16min ago
TriggeredBy: ● pipewire.socket
   Main PID: 1998 (pipewire)
      Tasks: 2 (limit: 18421)
     Memory: 6.1M
        CPU: 469ms
     CGroup: /user.slice/user-1000.slice/user@1000.service/session.slice/pipewire.service
             └─1998 /usr/bin/pipewire

Jun 25 12:12:17 fe38 systemd[1804]: Started pipewire.service - PipeWire Multimedia Service.
3

Here’s mine:

● pipewire.service - PipeWire Multimedia Service
     Loaded: loaded (/usr/lib/systemd/user/pipewire.service; disabled; preset: disabled)
    Drop-In: /usr/lib/systemd/user/pipewire.service.d
             └─00-uresourced.conf
             /usr/lib/systemd/user/service.d
             └─10-timeout-abort.conf
     Active: active (running) since Tue 2023-06-27 07:48:38 +06; 53min ago
TriggeredBy: ● pipewire.socket
   Main PID: 1280 (pipewire)
      Tasks: 2 (limit: 16584)
     Memory: 6.9M
        CPU: 121ms
     CGroup: /user.slice/user-1000.slice/user@1000.service/session.slice/pipewire.service
             └─1280 /usr/bin/pipewire

Jun 27 07:48:38 fedora systemd[1047]: Started pipewire.service - PipeWire Multimedia Service.

● pipewire-pulse.socket - PipeWire PulseAudio
     Loaded: loaded (/usr/lib/systemd/user/pipewire-pulse.socket; enabled; preset: enabled)
     Active: active (running) since Tue 2023-06-27 07:48:37 +06; 53min ago
   Triggers: ● pipewire-pulse.service
     Listen: /run/user/1000/pulse/native (Stream)
     CGroup: /user.slice/user-1000.slice/user@1000.service/app.slice/pipewire-pulse.socket

Jun 27 07:48:37 fedora systemd[1047]: Listening on pipewire-pulse.socket - PipeWire PulseAudio.

● pipewire-pulse.service - PipeWire PulseAudio
     Loaded: loaded (/usr/lib/systemd/user/pipewire-pulse.service; disabled; preset: disabled)
    Drop-In: /usr/lib/systemd/user/service.d
             └─10-timeout-abort.conf
     Active: active (running) since Tue 2023-06-27 07:48:44 +06; 53min ago
TriggeredBy: ● pipewire-pulse.socket

As systemd says Pipewire is active, is there anything to be worried about?