10175 segmentation fault megasync about megasync

[nunoachenriques]

hi @polmr, i have the same issue but a bit more clean: megasync just started to segfault after a regular upgrade on my debian gnu/linux stretch (9.0, testing). can you please, please, please :-) give priority to this issue so we all avoid being out of sync for too long...? thanks and cheers!

$ megasync --debug
15:16:28 (warn):  QT Warning: QSystemTrayIcon::setVisible: No Icon set
15:16:28 (debug): IPv6 enabled: 1 (net.cpp:61)
15:16:28 (debug): DNS servers: n.n.n.n,n.n.n.n (net.cpp:207)
15:16:28 (warn):  The app was recently restarted. Restart skipped
Segmentation fault

additionally, it seems rather strange that a patch (major.minor.patch) increment (3 to 4) causes a backward incompatibility (libcrypto++ folks should pay more attention to versioning ;-)):

[...] PATCH version when you make backwards-compatible bug fixes.

From: http://semver.org/

[polmr]

This is fixed already (only the package for 64 bits). Update megasync package / download it again from https://mega.nz/#sync and the segfault should be solved. Thanks all for reporting.

[nunoachenriques]

hi @polmr and thanks for the fast build!

apt-get update
apt-get upgrade
megasync &

et voilà! in sync again!
cheers :-)

[polmr]

Hi @jemadux.
I understand you installed the Debian 9 package. It has been generated with an alpha 7 Stretch (latests available).
The segmentation fault is likely due to a change in cryptopp library. It is compiled against libcryto++ 5.6.3 whereas testing repos offer 5.6.4
Backward compatibility is broken for cryptopp I'm afraid. I think the solution is to release a version with libcrypto linked statically (at least until a final Debian 9 is released). It shouldn't take long, but if you want an inmediate solution that might work, you can compile libcryptopp 5.6.3 and launch megasync with the corresponding LD_LIBRARY_PATH stablished to the path where you compile libcrypto++