Ripcord closing

Ripcord is a Discord and Slash QT client.

I’ll switch workspaces to see if’n I’ve any messages, and find that the app has closed. No error messages, just gone. It does the same thing on my other computer that runs KDE as well as this one which usually runs UKUI and occasionally Cinnamon, so it would seem to be DE agnostic. Launching it from the terminal gets the following: QSslSocket: cannot resolve SSL_set_alpn_protos QSslSocket: cannot resolve SSL_CTX_set_alpn_select_cb QSslSocket: cannot resolve SSL_get0_alpn_selected

and after it’s gone, we get:

The X11 connection broke: No error (code 0)
X connection to :0 broken (explicit kill or server shutdown).

Any ideas what’s going on, and whether it’s something I can fix?

1 Like

Ok, didn’t see a direct correlation in @joekamprad 's link, but when I yay’d it again, there’s now two choices for Ripcord, Ripcord and Ripcord-arch-libs, so I installed the latter, and so far, so good, knock on wood, twelve hours and it’s still working, well, not counting having had the system freeze a couple times, but that’s not related. So, I guess tentatively solved.