meganz / MEGAsync

Easy automated syncing between your computers and your MEGA Cloud Drive
Other
1.59k stars 277 forks source link

Cannot start after update to 4.7.2-4 on Manjaro Linux #755

Open InSimpleTermsJordan opened 1 year ago

InSimpleTermsJordan commented 1 year ago

When attempting to start megasync via Konsole after updating from 4.6.8 to 4.7.2 via Pamac, the following message is returned: megasync: error while loading shared libraries: libssl.so.3: cannot open shared object file: No such file or directory Attempted reinstalling megasync and openssl and restarting PC to no avail.

tristobal commented 1 year ago

Same error here. I tried to uninstall megasync (via Yay), then I reinstalled it again following Desktop App - MEGA, but the error is still the same. Its seems that Megasync requires OpenSSL 3, but the lastest version in pacman/yay is core/openssl 1.1.1.q-1

PacoPuerta commented 1 year ago

Same issue here. I had to downgrade to version 4.6.8 which works with openssl 1.1.1 ---

polmr commented 1 year ago

4.7.2 Arch Linux package depends on OpenSSL 3, currently available in Arch Linux repositories. Manjaro will soon update it.

pete-willard commented 1 year ago

Soon™️ https://forum.manjaro.org/t/any-thoughts-on-when-is-openssl-going-to-be-updated/85275

pete-willard commented 1 year ago

Glad to report a Manjaro update just dropped and OpenSSL was indeed bumped to v3.0.7. The latest MegaSync app now works.

InSimpleTermsJordan commented 1 year ago

Can confirm. (well, transfers still hang for long periods of time, so "works" may be too generous, but the app starts, anyway.)

On Wed, Nov 16, 2022 at 2:30 AM Piotr Wierzbicki @.***> wrote:

Glad to report a Manjaro update just dropped and OpenSSL was indeed bumped to v3.0.7. The latest MegaSync app now works.

— Reply to this email directly, view it on GitHub https://github.com/meganz/MEGAsync/issues/755#issuecomment-1316591854, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABUXTM62KK4OFR74P2EEJUDWISLQ7ANCNFSM6AAAAAARZ75RFQ . You are receiving this because you authored the thread.Message ID: @.***>