Marek Rusinowski

Ah, looks like exactly the same case and I just failed to find that closed issue. This can be probably closed as duplicate then. (I wonder what GLFW does that...

@flibitijibibo I think I found the culprit... Under weston I can make both GLFW and SDL windows to crash. The behavior there is the same. Under Gnome 42 though only...

I've opened question in `libdecor` https://gitlab.gnome.org/jadahl/libdecor/-/issues/35 and also opened the issue in `mutter` to highlight the issue there too https://gitlab.gnome.org/GNOME/mutter/-/issues/2234. Also Re merge request mentioned in https://github.com/libsdl-org/SDL/issues/4769#issuecomment-1017899013: I believe that...

@flibitijibibo There is a workaround! We can run the programs that have this problem with environment variable `LIBDECOR_PLUGIN_DIR=null` set, this will cause libdecor to not load any plugin, fallback to...

The login mechanism references in this issue no longer exists, obsolete.

Out of scope for lobby, will need to be handled via website, by design.

Out of scope for lobby, will need to be handled via website, by design.

With last rework, the code this bug refers no longer exists

FYI: I got the code signing cert from certum at the moment, and started manually signing releases of launcher. The main issue is that that particular cert (maybe other have...

My latest research: For code signing for Windows, there is in my opinion basically a single good option nowadays: https://azure.microsoft.com/en-us/products/trusted-signing, which is supported in [Beta in the electron-builder](https://www.electron.build/code-signing-win#using-azure-trusted-signing-beta) since end...