theGreatWhiteShark

I haven't looked into it yet. But it definitely rings a bell. Somewhere I did read about this behavior in the past. AFAIR the argument goes like this: if there...

> Firstly, this feels like it's a bug, or at least undesirable behaviour, on the part of some particular plugin. It's not true for all plugins, and it's not true...

> care would need to be taken to avoid swamping the user with error report dialogs It doesn't always have to be dialogs. We could also display errors (and warnings)...

> There is still the downside that only the newest message is displayed. But this itself is worth fixing right away. How about introducing a history of length X (adjustable...

Hey @Nikita2552 , Sorry for the late reply. Of course, go for it :)

Hey @Lucretia, Seems like your to plugins `amp.so` and `delay.so` are bricked and causing the crash. Do they work in other applications?

> Both applications should catch any error, not crash without giving any indication of what happened and that's what both do. I'm not an expert on these system-level kind of...

> Although, if the app is going to kill itself, I'd prefer to be given a message box saying why if possible. Hey @Lucretia , could you check whether the...

TBH I do not understand the point of this issue. Changing the config folder after more than 20 years feels like something that can only bring harm (and lot's of...

> The point is follow the XDG standard so Linux users found configuration, data and cache files on the expected folders. Then for example if the user runs out of...