Vincent Chernin

Glad to hear it worked! On the update needing a reboot, it's likely because you had shutdown on window closed disabled. Every time you tried to close to window it...

> I do not remember now cases where an upgrade to EasyEffects required it to be killed and restarted. It may be something really particular to this issue situation. I...

> It is more about the user restarting its computer after updating the server than restarting the audio application I see, yeah that's out of scope here. I will investigate...

> My opinion here is probably pointless I don't think so :) > "Oh you never have to reboot unless you want to on Linux" This one annoys me... at...

Luckily, it turns out we don't need any portal. Flatpak is supposed to create the marker file `/app/.updated` (in the sandbox) which means the app has been updated. So that...

To make it easier to understand their implementation I squashed their (3?) relevant commits https://github.com/vchernin/portal-test/commit/d99c0904f65778ee358a98b4d6bde224b041d270 > But it will still be something running in the background without offering any benefit...

> If I set an EQ apart from the default loading Oratory1990, say bassy-k361, and then close EE, returning back to my work, it works as intended. But whenever I...

Was this on the flatpak build? If so please make sure you are on 6.2.7. Even if not, maybe whatever fixed the flatpak build in 6.2.7 will also help in...

What is strange about the message? It is behaving as intended (ignoring the not starting part). Does ``` flatpak run --command=easyeffects com.github.wwmm.easyeffects ``` work differently than ``` flatpak run com.github.wwmm.easyeffects...

So with both commands it launches now? But it didn’t work before launching with the debug variable? I am not sure why that would happen.