Upgraded to Fedora 41, now EasyEffects don't work

Ask Fedora
1

I upgraded to Fedora 41 and now EasyEffects do not launch:

If I use “G_MESSAGES_DEBUG=easyeffects easyeefects” in the command line it shows this:

(easyeffects:3138): easyeffects-DEBUG: 10:21:50.836: pipe_manager.cpp:1564 compiled with PipeWire: 1.2.5
(easyeffects:3138): easyeffects-DEBUG: 10:21:50.836: pipe_manager.cpp:1565 linked to PipeWire: 1.2.6

(easyeffects:3138): easyeffects-ERROR **: 10:21:50.867: pipe_manager.cpp:1598 context connection failed

I uninstalled it and then reinstalled and then uninstalled again, installed the flatpak package, still don’t launch.
I see this topic EasyEffects service won't launch at startup, it’s not the same issue.

2

Can you post: systemctl --user status pipewire\* wireplu\*

Thanks

1 Like
3

I don’t have anything using sound:

$ systemctl --user status pipewire* wireplu*
× pipewire.socket - PipeWire Multimedia System Sockets
Loaded: loaded (/usr/lib/systemd/user/pipewire.socket; enabled; preset: enabled)
Active: failed (Result: service-start-limit-hit) since Fri 2024-11-08 21:15:39 -03; 2min 33s ago
Duration: 902us
Invocation: 1a90e83c11f04d07bc10cc28d78e8800
Triggers: ● pipewire.service
Listen: /run/user/1000/pipewire-0 (Stream)
/run/user/1000/pipewire-0-manager (Stream)

nov 08 21:15:39 fedora systemd[1957]: Listening on pipewire.socket - PipeWire Multimedia System Sockets.
nov 08 21:15:39 fedora systemd[1957]: pipewire.socket: Failed with result ‘service-start-limit-hit’.

× pipewire.service - PipeWire Multimedia Service
Loaded: loaded (/usr/lib/systemd/user/pipewire.service; disabled; 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: failed (Result: exit-code) since Fri 2024-11-08 21:15:32 -03; 2min 40s ago
Duration: 20ms
Invocation: 39a598c311194405b6581eb7d8e415de
TriggeredBy: × pipewire.socket
Process: 2176 ExecStart=/usr/bin/pipewire (code=exited, status=234)
Main PID: 2176 (code=exited, status=234)

nov 08 21:15:32 fedora systemd[1957]: pipewire.service: Scheduled restart job, restart counter is at 5.
nov 08 21:15:32 fedora systemd[1957]: pipewire.service: Start request repeated too quickly.
nov 08 21:15:32 fedora systemd[1957]: pipewire.service: Failed with result ‘exit-code’.
nov 08 21:15:32 fedora systemd[1957]: Failed to start pipewire.service - PipeWire Multimedia Service.
nov 08 21:15:39 fedora systemd[1957]: pipewire.service: Start request repeated too quickly.
nov 08 21:15:39 fedora systemd[1957]: pipewire.service: Failed with result ‘exit-code’.
nov 08 21:15:39 fedora systemd[1957]: Failed to start pipewire.service - PipeWire Multimedia Service.

● pipewire-pulse.service - PipeWire PulseAudio
Loaded: loaded (/usr/lib/systemd/user/pipewire-pulse.service; disabled; preset: disabled)
Drop-In: /usr/lib/systemd/user/service.d
└─10-timeout-abort.conf
Active: active (running) since Fri 2024-11-08 21:15:39 -03; 2min 34s ago
Invocation: 7a9290885b624dbdb711e017d91fca40
TriggeredBy: ● pipewire-pulse.socket
Main PID: 2648 (pipewire-pulse)
Tasks: 3 (limit: 18546)
Memory: 1.3M (peak: 1.8M)
CPU: 58ms
CGroup: /user.slice/user-1000.slice/user@1000.service/session.slice/pipewire-pulse.service
└─2648 /usr/bin/pipewire-pulse

nov 08 21:18:00 fedora pipewire-pulse[2648]: mod.protocol-pulse: 0x55bd5f6ae8c0: failed to connect client: Host está desligado
nov 08 21:18:00 fedora pipewire-pulse[2648]: mod.protocol-pulse: client 0x55bd5f6c96b0 [GNOME Volume Control Media Keys]: ERROR command:9 (>
nov 08 21:18:04 fedora pipewire-pulse[2648]: mod.protocol-pulse: 0x55bd5f6ae8c0: failed to connect client: Host está desligado
nov 08 21:18:04 fedora pipewire-pulse[2648]: mod.protocol-pulse: client 0x55bd5f6c9210 [GNOME Shell Volume Control]: ERROR command:9 (SET_C>
nov 08 21:18:05 fedora pipewire-pulse[2648]: mod.protocol-pulse: 0x55bd5f6ae8c0: failed to connect client: Host está desligado
nov 08 21:18:05 fedora pipewire-pulse[2648]: mod.protocol-pulse: client 0x55bd5f6c96b0 [GNOME Volume Control Media Keys]: ERROR command:9 (>
nov 08 21:18:09 fedora pipewire-pulse[2648]: mod.protocol-pulse: 0x55bd5f6ae8c0: failed to connect client: Host está desligado
nov 08 21:18:09 fedora pipewire-pulse[2648]: mod.protocol-pulse: client 0x55bd5f6c9210 [GNOME Shell Volume Control]: ERROR command:9 (SET_C>
nov 08 21:18:10 fedora pipewire-pulse[2648]: mod.protocol-pulse: 0x55bd5f6ae8c0: failed to connect client: Host está desligado
nov 08 21:18:10 fedora pipewire-pulse[2648]: mod.protocol-pulse: client 0x55bd5f6c96b0 [GNOME Volume Control Media Keys]: ERROR command:9 (>

● pipewire-pulse.socket - PipeWire PulseAudio
Loaded: loaded (/usr/lib/systemd/user/pipewire-pulse.socket; enabled; preset: enabled)
Active: active (running) since Fri 2024-11-08 21:15:29 -03; 2min 43s ago
Invocation: b2303c0eec074d83868f3ccfc14a09b2
Triggers: ● pipewire-pulse.service
Listen: /run/user/1000/pulse/native (Stream)
CGroup: /user.slice/user-1000.slice/user@1000.service/app.slice/pipewire-pulse.socket

nov 08 21:15:29 fedora systemd[1957]: Listening on pipewire-pulse.socket - PipeWire PulseAudio.

4

That looks like the pipewire.service is failed.
Does restarting it work?
systemctl --user restart pipewire\*

Looking at journalctl --no-host --no-pager -b --user -u pipewire\* may provide some additional information.

Are you not running wireplumber?

Thanks

1 Like
5

Yes, thanks for the command line " journalctl --no-host --no-pager -b --user -u pipewire\*", I discover that my pipewire configuration at /home/user/.config/pipewire/pipewire.conf had some problems, deleted it and voilà everything is ok now.
Pipewire have changed it’s configs?
Really thanks!

1 Like