Restart sound on Fedora 44

Ask Fedora
, , ,
1

How do i restart sound on Fedora 44 KDE Plasma?

Operating System: Fedora Linux 44
KDE Plasma Version: 6.6.5
KDE Frameworks Version: 6.26.0
Qt Version: 6.11.1
Kernel Version: 7.0.10-201.fc44.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 8 × Intel® Core™ i7-7700K CPU @ 4.20GHz
Memory: 16 GiB of RAM (15.6 GiB usable)
Graphics Processor: Quadro RTX 4000
Manufacturer: Gigabyte Technology Co., Ltd.
Product Name: Z170X-Gaming 7
2

If sound is crashing then it would be worth trying to find out why.

systemctl --user status pipewire.service

Are you seeing errors in the user or system journals?

Typcially you can restart the pipewire.service if it’s crashed.

systemctl --user restart pipewire.service
3

If my answer would be as short as your question, I would tell you: Restart the Computer.

However this might be an alternative :wink: :

# to check status first: 
systemctl --user status pipewire{,-pulse}.socket

# restart:
systemctl --user restart pipewire{,-pulse}.socket

Source

4 
● pipewire.service - PipeWire Multimedia Service
     Loaded: loaded (/usr/lib/systemd/user/pipewire.service; enabled; 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 Sat 2026-06-06 10:11:40 CEST; 2h 17min ago
 Invocation: 90651adbbe504dbda6786ecd10514db0
TriggeredBy: ● pipewire.socket
   Main PID: 2472 (pipewire)
      Tasks: 3 (limit: 18930)
     Memory: 11.2M (peak: 31.5M, swap: 2.1M, swap peak: 2.1M)
        CPU: 1.363s
     CGroup: /user.slice/user-1000.slice/user@1000.service/session.slice/pipewire.service
             └─2472 /usr/bin/pipewire

Jun 06 10:11:40 ws-study systemd[2453]: Started pipewire.service - PipeWire Multimedia Service.
Jun 06 10:11:40 ws-study pipewire[2472]: mod.rt: could not set nice-level to -11: Permission denied
Jun 06 10:11:40 ws-study pipewire[2472]: mod.raop-sink: sess.latency.msec 250.000000 should be an integer multiple of rtp.ptime 7.981859

Not crashing, just gets garbled.

5

Please decide if you want to have this solved here or over at kde discuss.

6

Is this not DE independent?

7

Likely this is why it garbed.
The service cannot run at a high enough priority to keep up with the audio processing.

And that error may be due to selinux as you showed over on kde discuss (it is you isn’t it).

8

Thanks

(I cannot resist this:I always thought that with Linux I no longer need to restart the computer everytime an errors occurs as with some other OS)

So systemctl --user restart pipewire{,-pulse}.socket resulted in no audio which is better than to wake up the neighbours with this static droning it did before. But not really a solution

● pipewire-pulse.socket - PipeWire PulseAudio
     Loaded: loaded (/usr/lib/systemd/user/pipewire-pulse.socket; enabled; preset: enabled)
     Active: active (running) since Sat 2026-06-06 12:32:30 CEST; 1min 30s ago
 Invocation: 1c3bf367cd7a46d4b3860838246f0909
   Triggers: ● pipewire-pulse.service
     Listen: /run/user/1000/pulse/native (Stream)

Jun 06 12:32:30 ws-study systemd[2453]: Closed pipewire-pulse.socket - PipeWire PulseAudio.
Jun 06 12:32:30 ws-study systemd[2453]: Stopping pipewire-pulse.socket - PipeWire PulseAudio...
Jun 06 12:32:30 ws-study systemd[2453]: Listening on pipewire-pulse.socket - PipeWire PulseAudio.
9

Lets repeat:

Operating System: Fedora Linux 44
KDE Plasma Version: 6.6.5
KDE Frameworks Version: 6.26.0
Qt Version: 6.11.1
Kernel Version: 7.0.10-201.fc44.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 8 × Intel® Core™ i7-7700K CPU @ 4.20GHz
Memory: 16 GiB of RAM (15.6 GiB usable)
Graphics Processor: Quadro RTX 4000
Manufacturer: Gigabyte Technology Co., Ltd.
Product Name: Z170X-Gaming 7
10

I saw this, however you have been asked not to use the whole internet for you, asking in all the forums for a solution :stuck_out_tongue: There is a worldwide bandwidth shortage :rofl:

I think as long as we can keep it general, for Fedora, everyone has a profit out of it. In the end KDE & Workstation are editions now, If I have to learn two different procedures, it will get even for me to much tweaking in the Terminal.

I know what you mean … at least we don’t show a blue screen :slight_smile:
When stopping medication, you should do it slowly. So, some times a restart is OK.

11

It works IF you leave the pipewire{,-pulse}.service user units at the default disabled state. Those services are supposed to be triggered by the socket units.

Otherwise try restarting the user service units and not the sockets.

12

@anotheruser
Just for checking the status is best then, right?

systemctl --user status pipewire{,-pulse}*  #shows sockets & services


# And for restarting just restart like:

systemctl --user restart pipewire  

# and it will automatically restart what is needed right?

P.S.
Is there a verbose option when restarting, to see what is OK and what fails?

Sorry for all this questions. I think it is worth to have a standard procedure. I understood that an edition has the basics for everyone same and the DE is just different.
As we do check and restart sockets and services this should be standard procedure.

13

By default the restart blocks until the service is up and running.
If it fails you should see an error from systemctl.

When I’m debugging services I tend to use the --no-block option and then run journalctl -f to see the logs are the service starts up.

14

@theking2 I found a nice script which creates a diagnosis about audio.

It is from framework computers website and refers to Fedora: