Wireplumber not working after update to Kernel 5.16.7

Ask Fedora
,
1 
$ systemctl --user status wireplumber
× wireplumber.service - Multimedia Service Session Manager
     Loaded: loaded (/usr/lib/systemd/user/wireplumber.service; enabled; vendor preset: enabled)
     Active: failed (Result: exit-code) since Thu 2022-02-10 19:00:12 -03; 6min ago
    Process: 2333 ExecStart=/usr/bin/wireplumber (code=exited, status=70)
   Main PID: 2333 (code=exited, status=70)
        CPU: 30ms

Feb 10 19:00:12 fedy systemd[1909]: wireplumber.service: Main process exited, code=exited, status=70/SOFTWARE
Feb 10 19:00:12 fedy systemd[1909]: wireplumber.service: Failed with result 'exit-code'.
Feb 10 19:00:12 fedy systemd[1909]: wireplumber.service: Scheduled restart job, restart counter is at 5.
Feb 10 19:00:12 fedy systemd[1909]: Stopped Multimedia Service Session Manager.
Feb 10 19:00:12 fedy systemd[1909]: wireplumber.service: Start request repeated too quickly.
Feb 10 19:00:12 fedy systemd[1909]: wireplumber.service: Failed with result 'exit-code'.
Feb 10 19:00:12 fedy systemd[1909]: Failed to start Multimedia Service Session Manager.

Journalctl:

Feb 10 19:00:11 fedy rtkit-daemon[1037]: Successfully made thread 2180 of process 2171 (/usr/bin/wireplumber) owned by '1000' RT at priority 20.
Feb 10 19:00:11 fedy wireplumber[2171]: Failed to open module /usr/lib64/wireplumber-0.4/libwireplumber-module-route-settings-api: /usr/lib64/wireplumber-0.4/libwireplumber-module-route-settings-api.so: cannot open shared object file: No such file or directory
Feb 10 19:00:11 fedy systemd[1909]: wireplumber.service: Main process exited, code=exited, status=70/SOFTWARE
Feb 10 19:00:11 fedy systemd[1909]: wireplumber.service: Failed with result 'exit-code'.
Feb 10 19:00:11 fedy systemd[1909]: wireplumber.service: Scheduled restart job, restart counter is at 1.
Feb 10 19:00:11 fedy rtkit-daemon[1037]: Successfully made thread 2207 of process 2205 (/usr/bin/wireplumber) owned by '1000' RT at priority 20.
Feb 10 19:00:11 fedy wireplumber[2205]: Failed to open module /usr/lib64/wireplumber-0.4/libwireplumber-module-route-settings-api: /usr/lib64/wireplumber-0.4/libwireplumber-module-route-settings-api.so: cannot open shared object file: No such file or directory
Feb 10 19:00:11 fedy systemd[1909]: wireplumber.service: Main process exited, code=exited, status=70/SOFTWARE
Feb 10 19:00:11 fedy systemd[1909]: wireplumber.service: Failed with result 'exit-code'.
Feb 10 19:00:12 fedy systemd[1909]: wireplumber.service: Scheduled restart job, restart counter is at 2.
Feb 10 19:00:12 fedy rtkit-daemon[1037]: Successfully made thread 2232 of process 2231 (/usr/bin/wireplumber) owned by '1000' RT at priority 20.
Feb 10 19:00:12 fedy wireplumber[2231]: Failed to open module /usr/lib64/wireplumber-0.4/libwireplumber-module-route-settings-api: /usr/lib64/wireplumber-0.4/libwireplumber-module-route-settings-api.so: cannot open shared object file: No such file or directory
Feb 10 19:00:12 fedy systemd[1909]: wireplumber.service: Main process exited, code=exited, status=70/SOFTWARE
Feb 10 19:00:12 fedy systemd[1909]: wireplumber.service: Failed with result 'exit-code'.
Feb 10 19:00:12 fedy systemd[1909]: wireplumber.service: Scheduled restart job, restart counter is at 3.
Feb 10 19:00:12 fedy rtkit-daemon[1037]: Successfully made thread 2268 of process 2257 (/usr/bin/wireplumber) owned by '1000' RT at priority 20.
Feb 10 19:00:12 fedy wireplumber[2257]: Failed to open module /usr/lib64/wireplumber-0.4/libwireplumber-module-route-settings-api: /usr/lib64/wireplumber-0.4/libwireplumber-module-route-settings-api.so: cannot open shared object file: No such file or directory
Feb 10 19:00:12 fedy systemd[1909]: wireplumber.service: Main process exited, code=exited, status=70/SOFTWARE
Feb 10 19:00:12 fedy systemd[1909]: wireplumber.service: Failed with result 'exit-code'.
Feb 10 19:00:12 fedy systemd[1909]: wireplumber.service: Scheduled restart job, restart counter is at 4.
Feb 10 19:00:12 fedy rtkit-daemon[1037]: Successfully made thread 2338 of process 2333 (/usr/bin/wireplumber) owned by '1000' RT at priority 20.
Feb 10 19:00:12 fedy wireplumber[2333]: Failed to open module /usr/lib64/wireplumber-0.4/libwireplumber-module-route-settings-api: /usr/lib64/wireplumber-0.4/libwireplumber-module-route-settings-api.so: cannot open shared object file: No such file or directory
Feb 10 19:00:12 fedy systemd[1909]: wireplumber.service: Main process exited, code=exited, status=70/SOFTWARE
Feb 10 19:00:12 fedy systemd[1909]: wireplumber.service: Failed with result 'exit-code'.
Feb 10 19:00:12 fedy systemd[1909]: wireplumber.service: Scheduled restart job, restart counter is at 5.
Feb 10 19:00:12 fedy systemd[1909]: wireplumber.service: Start request repeated too quickly.
Feb 10 19:00:12 fedy systemd[1909]: wireplumber.service: Failed with result 'exit-code'.
Feb 10 19:02:41 fedy sudo[3345]:  luciano : TTY=pts/0 ; PWD=/home/luciano ; USER=root ; COMMAND=/usr/bin/systemctl --user start wireplumber
Feb 10 19:03:06 fedy sudo[3419]:  luciano : TTY=pts/0 ; PWD=/home/luciano ; USER=root ; COMMAND=/usr/bin/systemctl start wireplumber
Feb 10 19:03:26 fedy sudo[3477]:  luciano : TTY=pts/0 ; PWD=/home/luciano ; USER=root ; COMMAND=/usr/bin/systemctl status wireplumber
Feb 10 19:03:37 fedy sudo[3514]:  luciano : TTY=pts/0 ; PWD=/home/luciano ; USER=root ; COMMAND=/usr/bin/systemctl --user status wireplumber
Feb 10 19:04:29 fedy sudo[3660]:  luciano : TTY=pts/0 ; PWD=/home/luciano ; USER=root ; COMMAND=/usr/bin/systemctl --user stop wireplumber
Feb 10 19:04:35 fedy sudo[3681]:  luciano : TTY=pts/0 ; PWD=/home/luciano ; USER=root ; COMMAND=/usr/bin/systemctl --user status wireplumber
Feb 10 19:04:54 fedy sudo[3745]:  luciano : TTY=pts/0 ; PWD=/home/luciano ; USER=root ; COMMAND=/usr/bin/dnf reinstall wireplumber
Feb 10 19:05:12 fedy sudo[3832]:  luciano : TTY=pts/0 ; PWD=/home/luciano ; USER=root ; COMMAND=/usr/bin/systemctl --user status wireplumber
Feb 10 19:05:24 fedy sudo[3871]:  luciano : TTY=pts/0 ; PWD=/home/luciano ; USER=root ; COMMAND=/usr/bin/systemctl --user restart wireplumber
Feb 10 19:07:12 fedy rtkit-daemon[1037]: Successfully made thread 4191 of process 4186 (/usr/bin/wireplumber) owned by '1000' RT at priority 20.
Feb 10 19:07:12 fedy wireplumber[4186]: Failed to open module /usr/lib64/wireplumber-0.4/libwireplumber-module-route-settings-api: /usr/lib64/wireplumber-0.4/libwireplumber-module-route-settings-api.so: cannot open shared object file: No such file or directory
Feb 10 19:07:12 fedy systemd[1909]: wireplumber.service: Main process exited, code=exited, status=70/SOFTWARE
Feb 10 19:07:12 fedy systemd[1909]: wireplumber.service: Failed with result 'exit-code'.
Feb 10 19:07:12 fedy systemd[1909]: wireplumber.service: Scheduled restart job, restart counter is at 1.
Feb 10 19:07:12 fedy rtkit-daemon[1037]: Successfully made thread 4196 of process 4195 (/usr/bin/wireplumber) owned by '1000' RT at priority 20.
Feb 10 19:07:12 fedy wireplumber[4195]: Failed to open module /usr/lib64/wireplumber-0.4/libwireplumber-module-route-settings-api: /usr/lib64/wireplumber-0.4/libwireplumber-module-route-settings-api.so: cannot open shared object file: No such file or directory
Feb 10 19:07:12 fedy systemd[1909]: wireplumber.service: Main process exited, code=exited, status=70/SOFTWARE
Feb 10 19:07:12 fedy systemd[1909]: wireplumber.service: Failed with result 'exit-code'.
Feb 10 19:07:12 fedy systemd[1909]: wireplumber.service: Scheduled restart job, restart counter is at 2.
Feb 10 19:07:12 fedy rtkit-daemon[1037]: Successfully made thread 4201 of process 4200 (/usr/bin/wireplumber) owned by '1000' RT at priority 20.
Feb 10 19:07:12 fedy wireplumber[4200]: Failed to open module /usr/lib64/wireplumber-0.4/libwireplumber-module-route-settings-api: /usr/lib64/wireplumber-0.4/libwireplumber-module-route-settings-api.so: cannot open shared object file: No such file or directory
Feb 10 19:07:12 fedy systemd[1909]: wireplumber.service: Main process exited, code=exited, status=70/SOFTWARE
Feb 10 19:07:12 fedy systemd[1909]: wireplumber.service: Failed with result 'exit-code'.
Feb 10 19:07:13 fedy systemd[1909]: wireplumber.service: Scheduled restart job, restart counter is at 3.
Feb 10 19:07:13 fedy rtkit-daemon[1037]: Successfully made thread 4209 of process 4208 (/usr/bin/wireplumber) owned by '1000' RT at priority 20.
Feb 10 19:07:13 fedy wireplumber[4208]: Failed to open module /usr/lib64/wireplumber-0.4/libwireplumber-module-route-settings-api: /usr/lib64/wireplumber-0.4/libwireplumber-module-route-settings-api.so: cannot open shared object file: No such file or directory
Feb 10 19:07:13 fedy systemd[1909]: wireplumber.service: Main process exited, code=exited, status=70/SOFTWARE
Feb 10 19:07:13 fedy systemd[1909]: wireplumber.service: Failed with result 'exit-code'.
Feb 10 19:07:13 fedy systemd[1909]: wireplumber.service: Scheduled restart job, restart counter is at 4.
Feb 10 19:07:13 fedy rtkit-daemon[1037]: Successfully made thread 4214 of process 4213 (/usr/bin/wireplumber) owned by '1000' RT at priority 20.
Feb 10 19:07:13 fedy wireplumber[4213]: Failed to open module /usr/lib64/wireplumber-0.4/libwireplumber-module-route-settings-api: /usr/lib64/wireplumber-0.4/libwireplumber-module-route-settings-api.so: cannot open shared object file: No such file or directory
Feb 10 19:07:13 fedy systemd[1909]: wireplumber.service: Main process exited, code=exited, status=70/SOFTWARE
Feb 10 19:07:13 fedy systemd[1909]: wireplumber.service: Failed with result 'exit-code'.
Feb 10 19:07:13 fedy systemd[1909]: wireplumber.service: Scheduled restart job, restart counter is at 5.
Feb 10 19:07:13 fedy systemd[1909]: wireplumber.service: Start request repeated too quickly.
Feb 10 19:07:13 fedy systemd[1909]: wireplumber.service: Failed with result 'exit-code'.

If inxi -Fzx would be helpfully there is one on my other request because of the loginproblem:

2

Have you tried restarting wireplumber.
I have faced this type of a issue in a old kernel of f35 can’t remember the kernel V
But i just restarted wire plumber then it was ok.

3

Hi, maybe you want also to check that above file are available. If not or if it available but the problem persist, you could try to install/reinstall wireplumber-libs package and then try to logout and login again.

Update:

The other ways to install soname *.so is by for example by using:

sudo dnf install /usr/lib64/wireplumber-0.4/libwireplumber-module-route-settings-api.so

Found this cool trick from here

1 Like
4

I copied once the files from /usr/share/wireplumber to etc/wireplumber. I remembered me today an just renamed the files in /etc .

To use my audio i changed >
dnf swap wireplumber pipewire-media-session and today after renaming the /etc,

I changed back to wireplumber > dnf swap pipewire-media-session wireplumber

Now wireplumber works again. I just get a scheduler error which I will ignore:

$ systemctl --user status wireplumber
● wireplumber.service - Multimedia Service Session Manager
     Loaded: loaded (/usr/lib/systemd/user/wireplumber.service; enabled; vendor preset: enabled)
     Active: active (running) since Fri 2022-02-11 08:57:10 -03; 34min ago
   Main PID: 2285 (wireplumber)
      Tasks: 4 (limit: 18437)
     Memory: 10.6M
        CPU: 262ms
     CGroup: /user.slice/user-1000.slice/user@1000.service/session.slice/wireplumber.service
             └─2285 /usr/bin/wireplumber

Feb 11 08:57:10 fedy systemd[1896]: Started Multimedia Service Session Manager.
Feb 11 08:57:10 fedy wireplumber[2285]: Failed to set scheduler settings: Operation not permitted
1 Like
5

Can partially confirm the problem and the solution! My wireplumber fails with exactly the same error, and after I overwrote the config file for wireplumber in /etc (which I modified before) with the original config file in /usr/share and restarted the service, the error goes away. I also get the same scheduler failure warning. However, I updated both pipewire and the kernel before the problem happens, so it is also possible that the newer version of pipewire and wireplumber are not compatible with part of the old config.

6

Mine etc/wireplumber was empty of files:

$ tree
.
├── bluetooth.lua.d
├── common
├── main.lua.d
└── policy.lua.d

Have deleted the wireplumber directory in etc now.
I will see if the error still occurs after reboot.

7

I installed Fedora-Linux 36 in a virtual environment and saw that the error is there too. So, looks like a bug who is not fixed yet.

Which Desktop Environment are you using @ytliu ?

8

@ilikelinux Have you already tried to update to 5.16.8?

I have wireplumber problems for several months, although different than yours (and mostly related to customizations of my Fedora). But the update to 5.16.8 solved them and now it works fine. So, there seem to be changes in the kernel that are related to wireplumber.

9

Yes, i do Linux fedy 5.16.8-200.fc35.x86_64

My system is running inkl. wireplumber, it is just about the error.
See request:

if you check status of wireplumber do you get also the error @py0xc3 ?

Failed to set scheduler settings: Operation not permitted

I checked on Bugzilla but could not find the error listed.

10

@ilikelinux yes, that error is logged.

bash-5.1$ systemctl --user status wireplumber.service
 wireplumber.service - Multimedia Service Session Manager
     Loaded: loaded (/usr/lib/systemd/user/wireplumber.service; enabled; vendor preset: enabled)
     Active: active (running) since Wed 2022-02-16 12:11:11 CET; 14h ago
   Main PID: 2293 (wireplumber)
      Tasks: 4 (limit: 19076)
     Memory: 12.7M
        CPU: 4.829s
     CGroup: /user.slice/user-1000.slice/user@1000.service/session.slice/wireplumber.service
             2293 /usr/bin/wireplumber

Feb 16 12:11:11 localhost.localdomain systemd[1759]: Started Multimedia Service Session Manager.
Feb 16 12:11:11 localhost.localdomain wireplumber[2293]: Failed to set scheduler settings: Operation not permitted

It seems to happen once, at boot:

[root@localhost ~]# journalctl --since "2 days ago" | grep ireplum
Feb 15 12:13:05 localhost.localdomain rtkit-daemon[1159]: Successfully made thread 2262 of process 2262 (/usr/bin/wireplumber) owned by '1000' high priority at nice level -11.
Feb 15 12:13:05 localhost.localdomain rtkit-daemon[1159]: Successfully made thread 2270 of process 2262 (/usr/bin/wireplumber) owned by '1000' RT at priority 20.
Feb 15 12:13:05 localhost.localdomain wireplumber[2262]: Failed to set scheduler settings: Operation not permitted
Feb 15 12:24:57 localhost.localdomain rtkit-daemon[1180]: Successfully made thread 2230 of process 2230 (/usr/bin/wireplumber) owned by '1000' high priority at nice level -11.
Feb 15 12:24:57 localhost.localdomain rtkit-daemon[1180]: Successfully made thread 2284 of process 2230 (/usr/bin/wireplumber) owned by '1000' RT at priority 20.
Feb 16 02:15:22 localhost.localdomain wireplumber[2230]: [string "policy-bluetooth.lua"]:121: bad argument #1 to 'find' (string expected, got nil)
Feb 16 02:15:22 localhost.localdomain wireplumber[2230]: stopped by signal: Terminated
Feb 16 02:15:22 localhost.localdomain wireplumber[2230]: disconnected from pipewire
Feb 16 02:15:23 localhost.localdomain systemd[1742]: wireplumber.service: Consumed 6.943s CPU time.
Feb 16 12:11:11 localhost.localdomain rtkit-daemon[1157]: Successfully made thread 2293 of process 2293 (/usr/bin/wireplumber) owned by '1000' high priority at nice level -11.
Feb 16 12:11:11 localhost.localdomain rtkit-daemon[1157]: Successfully made thread 2311 of process 2293 (/usr/bin/wireplumber) owned by '1000' RT at priority 20.
Feb 16 12:11:11 localhost.localdomain wireplumber[2293]: Failed to set scheduler settings: Operation not permitted

Everything works fine. I assume this error is not related to your issue / modification.

11

According to journalctl --since "1 year ago" | grep "Failed to set scheduler settings: Operation not permitted", the error happens on boot since 16 January evening. The error only occurs with wireplumber.

1 Like
12

Same error is noted here

1 Like
13

Sorry for the late reply, I use the KDE spin of Fedora 35.