search

wwmm / easyeffects

Limiter, compressor, convolver, equalizer and auto volume and many other plugins for PipeWire applications
GNU General Public License v3.0
6.41k stars 268 forks source link

Crash on hyprland autostart, but work when launched normally (both in bg) #3386

Open littleblack111 opened 3 days ago

littleblack111 commented 3 days ago

EasyEffects Version

7.1.8

What package are you using?

Arch (easyeffects)

Distribution

Arch Linux

Describe the bug

on hyprland exec-once(auto launch). i put in easyeffects --gapplication-service for it to launch in bg:

exec-once = easyeffects --gapplication-service

Expected Behavior

it to just launch in bg and not do anything

Debug Log

idk how. but in the sddm wayland-session.log. i see this: (easyeffects:123618): easyeffects-WARNING **: 18:41:57.597: convolver.cpp:342 soe: : irs filename is null. Entering passthrough mode...

Additional Information

No response

wwmm commented 2 days ago

idk how. but in the sddm wayland-session.log. i see this: (easyeffects:123618): easyeffects-WARNING **: 18:41:57.597: convolver.cpp:342 soe: : irs filename is null. Entering passthrough mode...

This won't make the app crash. It just means the convolver is in passthrough mode. Considering that it only fails when autostarted my guess is that EasyEffects is being started by hyprland before PipeWire.

littleblack111 commented 2 days ago

idk how. but in the sddm wayland-session.log. i see this: (easyeffects:123618): easyeffects-WARNING **: 18:41:57.597: convolver.cpp:342 soe: : irs filename is null. Entering passthrough mode...

This won't make the app crash. It just means the convolver is in passthrough mode. Considering that it only fails when autostarted my guess is that EasyEffects is being started by hyprland before PipeWire.

hmm. i dont think thats the case. since i have a startup sound(pw-play). And the sound is glitched there(because of the startup of easyeffect & applying effects)

but after that. in btop and pulsemixer, easyeffect is nowhere to be seen

wwmm commented 1 day ago

but after that. in btop and pulsemixer, easyeffect is nowhere to be seen

Maybe the system is killing it. What is the output of sudo journalctl -b | grep -i easyeffects right after doing a login?

littleblack111 commented 1 day ago 
Sep 16 18:05:07 ArchLinux pipewire[1653]: pw.node: (easyeffects_sink-179) graph xrun not-triggered (0 suppressed)
Sep 16 18:05:07 ArchLinux pipewire[1653]: pw.node: (easyeffects_sink-179) xrun state:0x78696f209008 pending:14/15 s:4140506578123 a:4140506650709 f:4140506671197 waiting:72586 process:20488 status:triggered
Sep 16 18:05:09 ArchLinux pipewire[1653]: pw.node: (easyeffects_sink-179) graph xrun not-triggered (1 suppressed)
Sep 16 18:05:09 ArchLinux pipewire[1653]: pw.node: (easyeffects_sink-179) xrun state:0x78696f209008 pending:5/6 s:4142576817072 a:4142576861765 f:4142576880008 waiting:44693 process:18243 status:triggered