Package Details: megasync 4.2.0-1

Git Clone URL: (read-only)
Package Base: megasync
Description: Easy automated syncing between your computers and your MEGA cloud drive
Upstream URL:
Submitter: son_link
Maintainer: Kozeid
Last Packager: Kozeid
Votes: 321
Popularity: 6.007815
First Submitted: 2014-09-01 18:12
Last Updated: 2019-06-25 14:37

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 ... Next › Last »

attila123 commented on 2019-05-30 18:34

@Narga, I deleted (just for clarity) and re-installed megasync on my Manjaro installation. Note: initially, after update I also had the problem with, but that got fixed by re-installing megasync. I copy-pasted the full build output and after that I also did an ldd /usr/bin/megasync, plus I ran it from terminal to see that it really does not report any problem. These are all included here (needed 2 parts because of the size limitation for free users on pastebin): Hope this helps :) PS: not sure why you would need to create any symlink ?!?

Narga commented on 2019-05-30 16:20

@attila123: I recompile, reconfigure, reinstall and created a symlink of but it still is not work.

attila123 commented on 2019-05-30 15:35

It was flagged falsely out-of-date on 2019-05-22 with the reason " cannot open shared object file: No such file or directory". But there is no problem with this package, just the crypto++ package got an update, so in this case just re-install megasync (will re-configure and re-compile it). Just tried it, works fine. Update: I just see it had a crash (segmentation fault), but other than that it seems to work.

Leeo97one commented on 2019-05-23 17:32

Wait, I just installed it on my fresh Arch Linux and no problem so far.

Auswaschbar commented on 2019-05-14 17:43

@paumars same here

paumars commented on 2019-05-11 11:17

I'm not able to build the package because it has undefined references to libavformat functions, even though I have it via ffmpeg. Does anyone have this error as well?

pescepalla commented on 2019-05-04 12:02

Ah, yes. Perfect, thanks.

GuyDuNigo commented on 2019-05-03 15:06

@pescepalla This is maybe due to some cache that prevent megasync to recompile if the source code didn't change (especially if you use a tool like 'yay' to manage AUR packages). If you use yay: try removing ~/.cache/yay/megasync and building again.

pescepalla commented on 2019-05-03 13:44

Reinstalling doesn't work here, but the git version does.

wan109020 commented on 2019-05-03 04:43

@GuyDuNigo I reinstalled this package and it build again with the new crypto++ flawlessly. Reinstalling works for me