Closed cfanoulis closed 4 years ago
This is a known issue with linux and Dispatch. Some more info:
I looked at the backtrace that occurs on linux, and it seems like Discord uses reqwest per said libraries README OpenSSL 1.0.1, 1.0.2, or 1.1.0 is supported. So you can attempt to roll back in-order to make it work. Rolling back your openssl comes with consequences though, such as possibly completely messing up your installation.
Downgrading OpenSSL to 1.1.0 or lower should work, what did you downgrade to?
In the meantime, raising this issue internally again.
I downgraded to openssl 1.1.0 from the official apt repos and ssl 1.0.2 from ubuntu-security... not only did they not work, 1.0.2 also made my linux installation unbootable
Downgrading major OpenSSL versions is always a terrible idea because a lot of critical system components are linked to it, and pin to a major version (a program linked against 1.0 can't use 1.1 and vice-versa). This is not a good suggestion, and it will most likely lead to more broken Linux installs than fixed dispatch installs.
If you are on Arch Linux, you can install the openssl-1.0
package to keep both major versions installed side by side: https://www.archlinux.org/packages/core/x86_64/openssl-1.0/
heyo, any update on this?
We've got a working version that we'll be releasing shortly!
hooray! Thanks a lot!
Describe the bug When trying to login, dispatch burps the following error:
Steps to reproduce
dispatch login
Expected behavior The login flow begins
Actual behaviour Dispatch panics and throws the above error
Additional context Full trace: https://hasteb.in/wapizeyu.rb I was suggested to downgrade openssl, but that didn't help