Lost audio after modifying /etc/pipewire/pipewire.conf and restarting pipewire

General system Newbie
1

pls help, i was trying to play around with the config but ended up killing audio all i see is this now
image

systemctl --user restart pipewire pipewire-pulse wireplumber                                                                                  ─╯

    ~ ····················································································································· 12:57:47 AM  ─╮
❯ systemctl --user status pipewire pipewire-pulse wireplumber                                                                                   ─╯
● pipewire.service - PipeWire Multimedia Service
     Loaded: loaded (/usr/lib/systemd/user/pipewire.service; enabled; preset: enabled)
     Active: active (running) since Tue 2025-04-08 00:57:47 IST; 7s ago
 Invocation: c391cdad3541409481857e7bf0082583
TriggeredBy: ● pipewire.socket
   Main PID: 60650 (pipewire)
      Tasks: 1 (limit: 18774)
     Memory: 676K (peak: 1.8M)
        CPU: 10ms
     CGroup: /user.slice/user-1000.slice/user@1000.service/session.slice/pipewire.service
             └─60650 /usr/bin/pipewire

Apr 08 00:57:47 vansh-81y4 systemd[892]: Stopping PipeWire Multimedia Service...
Apr 08 00:57:47 vansh-81y4 systemd[892]: Stopped PipeWire Multimedia Service.
Apr 08 00:57:47 vansh-81y4 systemd[892]: Started PipeWire Multimedia Service.
Apr 08 00:57:47 vansh-81y4 pipewire[60650]: pw.context: 0x5efefd858630: no modules loaded from context.modules

● pipewire-pulse.service - PipeWire PulseAudio
     Loaded: loaded (/usr/lib/systemd/user/pipewire-pulse.service; enabled; preset: enabled)
     Active: active (running) since Tue 2025-04-08 00:57:47 IST; 7s ago
 Invocation: ba17eafc7044414eb4a014756dff267b
TriggeredBy: ● pipewire-pulse.socket
   Main PID: 60652 (pipewire-pulse)
      Tasks: 3 (limit: 18774)
     Memory: 2M (peak: 2.2M)
        CPU: 15ms
     CGroup: /user.slice/user-1000.slice/user@1000.service/session.slice/pipewire-pulse.service
             └─60652 /usr/bin/pipewire-pulse

Apr 08 00:57:47 vansh-81y4 systemd[892]: Stopping PipeWire PulseAudio...
Apr 08 00:57:47 vansh-81y4 systemd[892]: Stopped PipeWire PulseAudio.
Apr 08 00:57:47 vansh-81y4 systemd[892]: Started PipeWire PulseAudio.

lines 1-33...skipping...
● pipewire.service - PipeWire Multimedia Service
     Loaded: loaded (/usr/lib/systemd/user/pipewire.service; enabled; preset: enabled)
     Active: active (running) since Tue 2025-04-08 00:57:47 IST; 7s ago
 Invocation: c391cdad3541409481857e7bf0082583
TriggeredBy: ● pipewire.socket
   Main PID: 60650 (pipewire)
      Tasks: 1 (limit: 18774)
     Memory: 676K (peak: 1.8M)
        CPU: 10ms
     CGroup: /user.slice/user-1000.slice/user@1000.service/session.slice/pipewire.service
             └─60650 /usr/bin/pipewire

Apr 08 00:57:47 vansh-81y4 systemd[892]: Stopping PipeWire Multimedia Service...
Apr 08 00:57:47 vansh-81y4 systemd[892]: Stopped PipeWire Multimedia Service.
Apr 08 00:57:47 vansh-81y4 systemd[892]: Started PipeWire Multimedia Service.
Apr 08 00:57:47 vansh-81y4 pipewire[60650]: pw.context: 0x5efefd858630: no modules loaded from context.modules

● pipewire-pulse.service - PipeWire PulseAudio
     Loaded: loaded (/usr/lib/systemd/user/pipewire-pulse.service; enabled; preset: enabled)
     Active: active (running) since Tue 2025-04-08 00:57:47 IST; 7s ago
 Invocation: ba17eafc7044414eb4a014756dff267b
TriggeredBy: ● pipewire-pulse.socket
   Main PID: 60652 (pipewire-pulse)
      Tasks: 3 (limit: 18774)
     Memory: 2M (peak: 2.2M)
        CPU: 15ms
     CGroup: /user.slice/user-1000.slice/user@1000.service/session.slice/pipewire-pulse.service
             └─60652 /usr/bin/pipewire-pulse

Apr 08 00:57:47 vansh-81y4 systemd[892]: Stopping PipeWire PulseAudio...
Apr 08 00:57:47 vansh-81y4 systemd[892]: Stopped PipeWire PulseAudio.
Apr 08 00:57:47 vansh-81y4 systemd[892]: Started PipeWire PulseAudio.

● wireplumber.service - Multimedia Service Session Manager
lines 1-34...skipping...
● pipewire.service - PipeWire Multimedia Service
     Loaded: loaded (/usr/lib/systemd/user/pipewire.service; enabled; preset: enabled)
     Active: active (running) since Tue 2025-04-08 00:57:47 IST; 7s ago
 Invocation: c391cdad3541409481857e7bf0082583
TriggeredBy: ● pipewire.socket
   Main PID: 60650 (pipewire)
      Tasks: 1 (limit: 18774)
     Memory: 676K (peak: 1.8M)
        CPU: 10ms
     CGroup: /user.slice/user-1000.slice/user@1000.service/session.slice/pipewire.service
             └─60650 /usr/bin/pipewire

Apr 08 00:57:47 vansh-81y4 systemd[892]: Stopping PipeWire Multimedia Service...
Apr 08 00:57:47 vansh-81y4 systemd[892]: Stopped PipeWire Multimedia Service.
Apr 08 00:57:47 vansh-81y4 systemd[892]: Started PipeWire Multimedia Service.
Apr 08 00:57:47 vansh-81y4 pipewire[60650]: pw.context: 0x5efefd858630: no modules loaded from context.modules

● pipewire-pulse.service - PipeWire PulseAudio
     Loaded: loaded (/usr/lib/systemd/user/pipewire-pulse.service; enabled; preset: enabled)
     Active: active (running) since Tue 2025-04-08 00:57:47 IST; 7s ago
 Invocation: ba17eafc7044414eb4a014756dff267b
TriggeredBy: ● pipewire-pulse.socket
   Main PID: 60652 (pipewire-pulse)
      Tasks: 3 (limit: 18774)
     Memory: 2M (peak: 2.2M)
        CPU: 15ms
     CGroup: /user.slice/user-1000.slice/user@1000.service/session.slice/pipewire-pulse.service
             └─60652 /usr/bin/pipewire-pulse

Apr 08 00:57:47 vansh-81y4 systemd[892]: Stopping PipeWire PulseAudio...
Apr 08 00:57:47 vansh-81y4 systemd[892]: Stopped PipeWire PulseAudio.
Apr 08 00:57:47 vansh-81y4 systemd[892]: Started PipeWire PulseAudio.

● wireplumber.service - Multimedia Service Session Manager
     Loaded: loaded (/usr/lib/systemd/user/wireplumber.service; enabled; preset: enabled)
lines 1-35...skipping...
● pipewire.service - PipeWire Multimedia Service
     Loaded: loaded (/usr/lib/systemd/user/pipewire.service; enabled; preset: enabled)
     Active: active (running) since Tue 2025-04-08 00:57:47 IST; 7s ago
 Invocation: c391cdad3541409481857e7bf0082583
TriggeredBy: ● pipewire.socket
   Main PID: 60650 (pipewire)
      Tasks: 1 (limit: 18774)
     Memory: 676K (peak: 1.8M)
        CPU: 10ms
     CGroup: /user.slice/user-1000.slice/user@1000.service/session.slice/pipewire.service
             └─60650 /usr/bin/pipewire

Apr 08 00:57:47 vansh-81y4 systemd[892]: Stopping PipeWire Multimedia Service...
Apr 08 00:57:47 vansh-81y4 systemd[892]: Stopped PipeWire Multimedia Service.
Apr 08 00:57:47 vansh-81y4 systemd[892]: Started PipeWire Multimedia Service.
Apr 08 00:57:47 vansh-81y4 pipewire[60650]: pw.context: 0x5efefd858630: no modules loaded from context.modules

● pipewire-pulse.service - PipeWire PulseAudio
     Loaded: loaded (/usr/lib/systemd/user/pipewire-pulse.service; enabled; preset: enabled)
     Active: active (running) since Tue 2025-04-08 00:57:47 IST; 7s ago
 Invocation: ba17eafc7044414eb4a014756dff267b
TriggeredBy: ● pipewire-pulse.socket
   Main PID: 60652 (pipewire-pulse)
      Tasks: 3 (limit: 18774)
     Memory: 2M (peak: 2.2M)
        CPU: 15ms
     CGroup: /user.slice/user-1000.slice/user@1000.service/session.slice/pipewire-pulse.service
             └─60652 /usr/bin/pipewire-pulse

Apr 08 00:57:47 vansh-81y4 systemd[892]: Stopping PipeWire PulseAudio...
Apr 08 00:57:47 vansh-81y4 systemd[892]: Stopped PipeWire PulseAudio.
Apr 08 00:57:47 vansh-81y4 systemd[892]: Started PipeWire PulseAudio.

● wireplumber.service - Multimedia Service Session Manager
     Loaded: loaded (/usr/lib/systemd/user/wireplumber.service; enabled; preset: enabled)
     Active: active (running) since Tue 2025-04-08 00:57:47 IST; 7s ago
 Invocation: 2349607c4a8140f0b39a500ccd4843a6
   Main PID: 60651 (wireplumber)
      Tasks: 3 (limit: 18774)
     Memory: 1.6M (peak: 1.9M)
2

There shouldn’t be a /etc/pipewire/... to modify. Did you create it? Undo whatever you did and pipewire should come back.

Then post what you’re trying to achieve or the actual changes you made.

3

image
image1384×337 13.3 KB

what should i remove from here?

4

ok i removed pipewire.conf now everything is back. thanks a lot mate!!

5

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.