Pipewire crashs regularly with fedora 44 - too many open files

Ask Fedora
,
1

Dear all

I’ve already read all the questions and answers related to my problem, but none of them led to a solution.

Pipewire and Wireplumber crash on my system every day with no apparent pattern. I currently have Fedora 44 installed (with GNOME), and my hardware is: HP Elite x360 1040 14-inch G10 2-in-1 / 13th Gen Intel Core i7-1355U x12.

I’ve also searched everywhere outside of this forum and even tried all the suggestions from HP, but nothing helps.

How can I prevent pipewire and wireplumber from crashing?

pipewire: version 1.6.8-1.fc44.x86_64
wireplumber: version 0.5.14-1.fc44.x86_64

Some lines from the user logs:

--Sep 11 08:32:18 fedora pipewire[3828]: mod.raop-sink: can’t connect: Too many open files
Sep 11 08:32:18 fedora pipewire[3828]: mod.raop-discover: Can’t load module: Too many open files
Sep 11 08:32:20 fedora pipewire[3828]: mod.raop-sink: can’t connect: Too many open files
Sep 11 08:32:20 fedora pipewire[3828]: mod.raop-discover: Can’t load module: Too many open files
Sep 11 08:32:50 fedora pipewire[3828]: mod.raop-sink: can’t connect: Too many open files
Sep 11 08:32:50 fedora pipewire[3828]: mod.raop-discover: Can’t load module: Too many open files

Any tips would be greatly appreciated.

Thank you very much and best regards,

Mike

2

I recall something like this a while ago but cannot find the topic.

In case it helps I updated your title to include “too many open file”.

It would be interesting to know what open files pipewire has when this happens.

Use the PID from the log what does lsof -p <PID> list.
The PID is the number in [] above it’s 3828.

When I run the lsof on pipewire on my desktop I see 126 lines of output as a comparison.

3

Hi Barry,

I get 1259 lines of output. Too many lines to post here …

4

Are there lots of Apple devices on your network? https://docs.pipewire.org/page_module_raop_discover.html says:

If no stream.rules are given, it will create a sink for all announced streams.

5

Thanks for this tip. I have already seen that a lot of MacBooks are available if I click on the speaker.

Now I renamed the file /usr/share/pipewird/pipewird.conf.d/50-raop.conf to /usr/share/pipewird/pipewird.conf.d/50-raop and rebooted. The error has not occurred since then.

Thank you very much for your help.

regards
Mike

6

Editing files in /usr/share is discouraged as updates may lose your edits. I removed the package that provides the raop configuration:

% sudo dnf5 info pipewire-config-raop.x86_64
Updating and loading repositories:
Repositories loaded.
Available packages
Name           : pipewire-config-raop
Epoch          : 0
Version        : 1.6.8
Release        : 1.fc44
Architecture   : x86_64
Download size  : 11.9 KiB
Installed size : 35.0   B
Source         : pipewire-1.6.8-1.fc44.src.rpm
Repository     : updates
Summary        : PipeWire configuration enabling the raop module
URL            : https://pipewire.org/
License        : MIT
Description    : This package contains the configuration file to enable the RAOP module.
Vendor         : Fedora Project
7

this is a temporary fix only, because a pipewire update will reinstall the file.
rename the file again and then remove pipewire-config-raop

$ rpm -qf /usr/share/pipewire/pipewire.conf.d/50-raop.conf
pipewire-config-raop-1.6.8-1.fc44.x86_64