pipewire - Could not load mandatory module X:Address already in use

0xmac · 2024-04-16 08:46:07

Yay, here we go again, another pipewire problem

I've had this problem quite a while of pipewire not starting.
Sometimes it would decide to start and sometimes not. I was okay with that.
Rebooting my PC 5 times would normally get it up and running normally

But a few days ago, PipeWire decides to not start at all.
I've rebootet my Computer like 40 times wich normally would magically start it sometimes.
I've tried using different Kernels (normal, lts and zen with and without fallback initramfs),
tweaked the BIOS, disabling multiprocessing, etc.
I update my system like every 10 minutes in hope a pipewire update releases.
Nothing.

Journalctl Logs:

systemd: Listening on PipeWire PulseAudio.
systemd: Listening on PipeWire Multimedia System Sockets.
kernel: pipewire: memfd_create() called without MFD_EXEC or MFD_NOEXEC_SEAL set
pipewire: pw.conf could not load mandatory module "libpipewire-module-protocol-pulse": Address already in use
...

Then everything PipeWire related aborts with "Recource temporarily unavailable"

Since the Logs also say, that some Memory Addresses Overlap
I've tried different RAM Sticks since 16Gigs RAM on an X220 is kinda flakey
(But I never had any problems )

If I delete my ~/.config/pipewire/pipewire.conf PipeWire starts again, but with no cards reported
(Since no Modules are gettings loaded and nothing configs)

I've also tried building PipeWire from the official repo to see if the problem is occuring upstream
> nothing changed

I've also tried booting my system on different computers, no change

The guys on https://gitlab.freedesktop.org/pipewire … ssues/3713
seem to have the same problem, but with no solution

I don't know if the problem lies within pipewire or kernel .

Gosh, everything seems to break in the worst moments possible.
I have like 5 online job interviews this week, god damnit

SystemInfo:

Computer: ThinkPad X220
CPU: i5-2540M
RAM: 16 Gigs
Kernel: 6.6.27-1-lts (my main)
WM: dwm
Pipewire Version: 1.0.5

V1del · 2024-04-16 09:13:34

Why do you have configs in your user home in the first place? Also seeing dwm, make sure you start it correctly, note the blue notes in https://wiki.archlinux.org/title/Xinit#xinitrc for proper preconditions for a correct session bus, post your .xinitrc in doubt.

If you get that message, are you explicitly starting it somewhere yourself instead of via the user session? You should not be doing that. What output do you get from

systemctl --user status pipewire{,pulse} wireplumber
loginctl session-status
sudo fuser -v /dev/snd/*
aplay -l

The MEMFD message is harmless and not the cause of your problem, you are running pipewire twice, for some reason.

Last edited by V1del (2024-04-16 09:13:58)

0xmac · 2024-04-16 11:52:40

You're right
if I killall pipewire and start it again it works again

in my xinitrc pipewire is started automaticly

But the systemctl status shows, that the pipewire daemon is disabled
and that it failed
It also reports

pipewire.service: Start request repeated too quickly.

which confirms your claim that it's started multiple times

wireplumber.service is also dead

I'll remove pipewire from my xinit autostart and see what happens

Thank you

0xmac · 2024-04-19 06:13:25

After I removed pipewire from my xinitrc, pipewire does not
show up anymore in my loginctl (but did previously)

Systemctl shows, that pipewire is disabled (but running)
and wireplumber enabled but dead.
Pipewire service also shows some error logs, these include

systemctl --user status pipewire{,pulse} wireplumber

Unit pipewirepulse.service could not be found.
○ pipewire.service - PipeWire Multimedia Service
     Loaded: loaded (/usr/lib/systemd/user/pipewire.service; disabled; preset: enabled)
     Active: inactive (dead) since Thu 2024-04-18 20:05:03 CEST; 15h ago
   Duration: 614ms
TriggeredBy: ● pipewire.socket
    Process: 1242 ExecStart=/usr/bin/pipewire (code=exited, status=0/SUCCESS)
   Main PID: 1242 (code=exited, status=0/SUCCESS)
        CPU: 62ms

Apr 18 20:05:03 DEVICE wireplumber[1246]: 0x621c19ed7a90: no modules loaded from context.modules
Apr 18 20:05:03 DEVICE pipewire[1248]: mod.protocol-pulse: server 0x5c6564b4b7f0: socket '/run/user/1000/pulse>
Apr 18 20:05:03 DEVICE pipewire[1248]: mod.protocol-pulse: pulse-server 0x5c6564b4b040: failed to start server>
Apr 18 20:05:03 DEVICE pipewire[1248]: mod.protocol-pulse: 0x5c6564b4b040: no servers could be started: Addres>
Apr 18 20:05:03 DEVICE pipewire[1248]: pw.conf: 0x5c6564b189e0: could not load mandatory module "libpipewire-m>
Apr 18 20:05:03 DEVICE pipewire[1248]: default: failed to create context: Address already in use
Apr 18 20:05:03 DEVICE wireplumber[1246]: 0x621c19efded0: leaked proxy 0x621c19f5d190 id:10
Apr 18 20:05:03 DEVICE wireplumber[1246]: 0x621c19efded0: leaked proxy 0x621c19fad6f0 id:13
Apr 18 20:05:03 DEVICE wireplumber[1246]: <WpMetadata:0x621c19f38010> core sync error: core disconnected
Apr 18 20:05:03 DEVICE wireplumber[1246]: disconnected from pipewire

○ wireplumber.service - Multimedia Service Session Manager
     Loaded: loaded (/usr/lib/systemd/user/wireplumber.service; enabled; preset: enabled)
     Active: inactive (dead) since Thu 2024-04-18 20:05:03 CEST; 15h ago
   Duration: 612ms
    Process: 1243 ExecStart=/usr/bin/wireplumber (code=exited, status=0/SUCCESS)
   Main PID: 1243 (code=exited, status=0/SUCCESS)
        CPU: 44ms

Apr 18 20:05:03 DEVICE systemd[552]: Started Multimedia Service Session Manager.
Apr 18 20:05:03 DEVICE wireplumber[1243]: 0x5c9638efca70: no modules loaded from context.modules
Apr 18 20:05:03 DEVICE wireplumber[1243]: 0x5c9638f22e90: leaked proxy 0x5c9638f83910 id:10
Apr 18 20:05:03 DEVICE wireplumber[1243]: 0x5c9638f22e90: leaked proxy 0x5c9638fd3860 id:13
lines 1-33...skipping...
Unit pipewirepulse.service could not be found.
○ pipewire.service - PipeWire Multimedia Service
     Loaded: loaded (/usr/lib/systemd/user/pipewire.service; disabled; preset: enabled)
     Active: inactive (dead) since Thu 2024-04-18 20:05:03 CEST; 15h ago
   Duration: 614ms
TriggeredBy: ● pipewire.socket
    Process: 1242 ExecStart=/usr/bin/pipewire (code=exited, status=0/SUCCESS)
   Main PID: 1242 (code=exited, status=0/SUCCESS)
        CPU: 62ms

Apr 18 20:05:03 DEVICE wireplumber[1246]: 0x621c19ed7a90: no modules loaded from context.modules
Apr 18 20:05:03 DEVICE pipewire[1248]: mod.protocol-pulse: server 0x5c6564b4b7f0: socket '/run/user/1000/pulse/native' is in use
Apr 18 20:05:03 DEVICE pipewire[1248]: mod.protocol-pulse: pulse-server 0x5c6564b4b040: failed to start server on 'unix:/run/user/1000/pulse/>
Apr 18 20:05:03 DEVICE pipewire[1248]: mod.protocol-pulse: 0x5c6564b4b040: no servers could be started: Address already in use
Apr 18 20:05:03 DEVICE pipewire[1248]: pw.conf: 0x5c6564b189e0: could not load mandatory module "libpipewire-module-protocol-pulse": Address >
Apr 18 20:05:03 DEVICE pipewire[1248]: default: failed to create context: Address already in use
Apr 18 20:05:03 DEVICE wireplumber[1246]: 0x621c19efded0: leaked proxy 0x621c19f5d190 id:10
Apr 18 20:05:03 DEVICE wireplumber[1246]: 0x621c19efded0: leaked proxy 0x621c19fad6f0 id:13
Apr 18 20:05:03 DEVICE wireplumber[1246]: <WpMetadata:0x621c19f38010> core sync error: core disconnected
Apr 18 20:05:03 DEVICE wireplumber[1246]: disconnected from pipewire

○ wireplumber.service - Multimedia Service Session Manager
     Loaded: loaded (/usr/lib/systemd/user/wireplumber.service; enabled; preset: enabled)
     Active: inactive (dead) since Thu 2024-04-18 20:05:03 CEST; 15h ago
   Duration: 612ms
    Process: 1243 ExecStart=/usr/bin/wireplumber (code=exited, status=0/SUCCESS)
   Main PID: 1243 (code=exited, status=0/SUCCESS)
        CPU: 44ms

Apr 18 20:05:03 DEVICE systemd[552]: Started Multimedia Service Session Manager.
Apr 18 20:05:03 DEVICE wireplumber[1243]: 0x5c9638efca70: no modules loaded from context.modules
Apr 18 20:05:03 DEVICE wireplumber[1243]: 0x5c9638f22e90: leaked proxy 0x5c9638f83910 id:10
Apr 18 20:05:03 DEVICE wireplumber[1243]: 0x5c9638f22e90: leaked proxy 0x5c9638fd3860 id:13
Apr 18 20:05:03 DEVICE wireplumber[1243]: <WpMetadata:0x5c9638f60cd0> core sync error: core disconnected
Apr 18 20:05:03 DEVICE wireplumber[1243]: disconnected from pipewire

Is the service startet twice for some reason??

If I killall pipewire (2 times) and start it again (not with sudo)
pipe works again.

sudo fuser -v /dev/snd/* shows

                     USER        PID ACCESS COMMAND
/dev/snd/controlC0:  USER       1421 F.... wireplumber
/dev/snd/seq:        USER       1418 F.... pipewire

but only one "instance" is running touh??

I don't have the command "aplay"

I never played around with pipewire,
I use lukesmiths preconfigured dwm build
(wich already configures pipe)

Heres my xinitrc:

#!/bin/sh

userresources=$HOME/.Xresources
usermodmap=$HOME/.Xmodmap
sysresources=/etc/X11/xinit/.Xresources
sysmodmap=/etc/X11/xinit/.Xmodmap

# merge in defaults and keymaps

if [ -f $sysresources ]; then
    xrdb -merge $sysresources
fi

if [ -f $sysmodmap ]; then
    xmodmap $sysmodmap
fi

if [ -f "$userresources" ]; then

    xrdb -merge "$userresources"

fi

if [ -f "$usermodmap" ]; then
    xmodmap "$usermodmap"
fi

# start some nice programs

if [ -d /etc/X11/xinit/xinitrc.d ] ; then
 for f in /etc/X11/xinit/xinitrc.d/?*.sh ; do
  [ -x "$f" ] && . "$f"
 done
 unset f
fi

setxkbmap de

#xinput --set-prop 12 libinput Accel Speed -0.5
xinput --set-prop "PixArt Cherry USB Optical Mouse" "libinput Accel Speed" -0.75

export GTK_IM_MODULE=fcitx
export QT_IM_MODULE=fcitx
export XMODIFIERS=@im=fcitx

twm &
xclock -geometry 50x50-1+1 &
xterm -geometry 80x50+494+51 &
xterm -geometry 80x20+494-0 &
exec xterm -geometry 80x66+0+0 -name login

Last edited by 0xmac (2024-04-19 09:52:31)

seth · 2024-04-19 07:08:31

I use lukesmiths preconfigured dwm build

There's your problem.

Post your xinitrc and all outputs of the commands V1del asked for
Please use [code][/code] tags, not "quote" tags. Edit your post in this regard.

Arch Linux

#1 2024-04-16 08:46:07

pipewire - Could not load mandatory module X:Address already in use

#2 2024-04-16 09:13:34

Re: pipewire - Could not load mandatory module X:Address already in use

#3 2024-04-16 11:52:40

Re: pipewire - Could not load mandatory module X:Address already in use

#4 2024-04-19 06:13:25

Re: pipewire - Could not load mandatory module X:Address already in use

#5 2024-04-19 07:08:31

Re: pipewire - Could not load mandatory module X:Address already in use

Board footer