Results 16 comments of slees

Wow. I'm going to have to disable them for my server too then I guess. They've been causing Fatal crashes recently lmao.

> I'm thinking we should just define `openssl` instead of `libssl1.1` or `libssl3` Yeah, I almost though openssl wasn't even installed on my system, I'm reproduce this exact error now...

I'm reproducing this error on Arch though, not Debian like the post says. Mb. ![image](https://user-images.githubusercontent.com/59808149/200480370-bcf08f4b-8623-4652-b4a6-c65b02d74a81.png) > Im not even sure you can modularly dropin in ssl3 for ssl1 without some...

Okay, I just made symlinks redirecting `libssl.so.1.1` to `libssl.so` in `/usr/lib`, which then complained about `libcrypto.so.1.1` after attemppting to run sunshine again. So i created a symlink for that too...

> As I already mentioned, this has to do with the OS that we build the deb package on, 20.04. Yeah, also I just got the dependency via a pacman...

I installed sunshine via `yay -S sunshine` And when i created the symlinks it instead asked for `OPENSSL_1_1_0` which i got that exact package yesterday via `pacman -Syu`, fixing sunshine...

try switching to x11 @ptrsr if you're on wayland

Done. I've tried saving a password from HiAnime in a `chromium --user-data-dir` session; Same results.

try cleaning the build cache files and run it again? check if `-DCMAKE_POLICY_VERSION_MINIMUM=3.5 \` is in your `build()` function i think i had your issue before