Failed to register: Timeout was reached

[AntonioBerna]

EasyEffects Version

7.4.1

What package are you using?

Arch (easyeffects)

Distribution

Manjaro XFCE

Describe the bug

I opened the terminal and typed easyeffects and got the following message:

Failed to register: Timeout was reached

Expected Behavior

No response

Debug Log

Debug Log

Failed to register: Timeout was reached

Additional Information

No response

[wwmm]

Kill easyeffects easyeffects -q and try to start it in debug mode G_MESSAGES_DEBUG=easyeffects easyeffects so we can see if there is anything suspicious in the logs.

[AntonioBerna]

Kill easyeffects easyeffects -q and try to start it in debug mode G_MESSAGES_DEBUG=easyeffects easyeffects so we can see if there is anything suspicious in the logs.

Hi, thank you for your response. I'm trying using your suggestion and I get this result:

G_MESSAGES_DEBUG=easyeffects easyeffects
(process:29103): easyeffects-DEBUG: 15:33:34.282: 	easyeffects.cpp:35	easyeffects version: 7.1.4
(process:29103): easyeffects-DEBUG: 15:33:34.288: 	easyeffects.cpp:45	locale directory: /usr/share/locale
(easyeffects:29103): easyeffects-DEBUG: 15:33:34.295: 	presets_manager.cpp:162user presets directory already exists: /home/berna/.config/easyeffects/
(easyeffects:29103): easyeffects-DEBUG: 15:33:34.295: 	presets_manager.cpp:162user presets directory already exists: /home/berna/.config/easyeffects/input
(easyeffects:29103): easyeffects-DEBUG: 15:33:34.295: 	presets_manager.cpp:162user presets directory already exists: /home/berna/.config/easyeffects/output
(easyeffects:29103): easyeffects-DEBUG: 15:33:34.295: 	presets_manager.cpp:162user presets directory already exists: /home/berna/.config/easyeffects/autoload/input
(easyeffects:29103): easyeffects-DEBUG: 15:33:34.295: 	presets_manager.cpp:162user presets directory already exists: /home/berna/.config/easyeffects/autoload/output
(easyeffects:29103): easyeffects-DEBUG: 15:33:35.250: 	pipe_manager.cpp:1481	compiled with PipeWire: 1.0.2
(easyeffects:29103): easyeffects-DEBUG: 15:33:35.250: 	pipe_manager.cpp:1482	linked to PipeWire: 1.0.3
(easyeffects:29103): easyeffects-DEBUG: 15:33:35.256: 	pipe_manager.cpp:1452	core version: 1.0.3
(easyeffects:29103): easyeffects-DEBUG: 15:33:35.256: 	pipe_manager.cpp:1453	core name: pipewire-0
(easyeffects:29103): easyeffects-DEBUG: 15:33:35.256: 	pipe_manager.cpp:1364	found metadata: settings

[wwmm]

pipe_manager.cpp:1364 found metadata: settings

There should be a default metadata too. Usually distributions put it in the package pipewire-pulse. You probably do not have it installed.

[AntonioBerna]

pipe_manager.cpp:1364 found metadata: settings

There should be a default metadata too. Usually distributions put it in the package pipewire-pulse. You probably do not have it installed.

My computer has pulseaudio installed by default and if I try to install pipewire-pulse I find a conflict between the two. Is there a way to see which applications on my computer need pulseaudio? Because in that case I might consider replacing it with pipewire-pulse.

[wwmm]

Is there a way to see which applications on my computer need pulseaudio?

If you try to uninstall it pacman will tell the list of packages that would be broken by this action and probably abort right after.

Because in that case I might consider replacing it with pipewire-pulse.

You have to in order to use PipeWire. The package pipewire-pulse provides a compatibility layer for apps that depend on Pulseaudio. It conflicts with Pulseaudio but as far as I know it is safe to let Pulseaudio to be replaced by it. I am not aware of any audio or video app that does not work in the compatibility layer.