Vincent Chernin

> -Maybe add a warning to easy effects prompting the user to check if all pipewire modules are installed and enabled if it times out? No idea how feasible that...

In CI the warnings show up in the GitHub CodeQL job but not in the Arch job. https://github.com/wwmm/easyeffects/actions/runs/5004142144/jobs/8966331929#step:6:264 The difference between them is that the Arch build has a wrapper...

This warning appears depending on the flags used. You can hide the warning by setting one of the following: - `-Dbuildtype=plain` (no optimizations and debug info) - `-Dbuildtype=debug` (no optimizations)...

I have seen this before... strangely it only occurs sometimes. As you can see from the symlink the issue is somehow yelp from the host launches instead of one in...

It looks like a bug of the wrapper script used to check the pipewire version. I was planning on getting rid of said script for a while, and replacing it...

> but it seems I can't close the window and leave EasyEffects running in the background as I used to Can you show logs when trying to disable shutdown on...

> at 19:23:47 I press Ctrl+W, which closes the entire application instead of just the window. Did you mean Ctrl+Q here? Ctrl+W only closes the window. I don't see anything...

> Isn't there a reliable way to check the Pipewire version in the application rather than relying on a script? There is, you can just do a string comparison of...

> That is the system Pipewire version. Where is the Flatpak version? We only need to check the system (daemon) version. The flatpak version (the library) is from the flatpak...

> Is it hardcoded in Easyeffects? Yes. > I don't know if bad things happen when we show two message dialogs at the same time I think this situation can’t...