Package Details: megasync 5.4.0.0-1

Git Clone URL: https://aur.archlinux.org/megasync.git (read-only, click to copy)
Package Base: megasync
Description: Official MEGA desktop application for syncing with MEGA Cloud Drive
Upstream URL: https://github.com/meganz/MEGAsync/
Licenses: LicenseRef-Mega-Limited-Code-License
Submitter: son_link
Maintainer: dbermond
Last Packager: dbermond
Votes: 382
Popularity: 1.88
First Submitted: 2014-09-01 18:12 (UTC)
Last Updated: 2024-07-25 13:44 (UTC)

Latest Comments

1 2 3 4 5 6 .. 51 Next › Last »

kirija commented on 2024-07-09 21:07 (UTC) (edited on 2024-07-09 21:07 (UTC) by kirija)

@vagelis The error happened during syncing some of my simulation files, there are a lot of them with the same name (but different paths). This is partly because I didn't sync for several weeks. So it's impossible to locate which file triggered the error. My local folder is also not shared with other OS. I just tried reinstalling megasync, it didn't help.

vagelis commented on 2024-07-09 20:54 (UTC)

@kirija check the last file you've updated, through the web portal of Mega or ither device comnected to the account. If you have a dual boot sharing the directory with Windows or other OS, maybe that one did not shutdown correctly, creating the issue (happened to me some time ago) with the file permissions. You can finaly purge the whole application and config files and reinstall from scratch.

kirija commented on 2024-07-09 20:49 (UTC)

I got the following error during syncing:


MEGAprivate ERROR DUMP
Application: MEGAsync [64 bit]
Hash: 3b452b01c9aab4ac87804304adbf5cc5
Version code: 50300.2
Module name: MEGA
Timestamp: 1720557538174
Operating system: Linux
System version:  manjarolinux 24.0.3/#1 SMP PREEMPT_DYNAMIC Wed Jun 19 18:55:06 UTC 2024
System release:  6.1.94-1-MANJARO
System arch: x86_64
Error info:
Segmentation fault (11) at address 0x98
Stacktrace:
megasync(+0x613e10) [0x55c7bc91be10]
megasync(+0x613e10) [0x55c7bc91be10]
megasync(+0x613de0) [0x55c7bc91bde0]
megasync(+0x613de0) [0x55c7bc91bde0]
megasync(+0x613de0) [0x55c7bc91bde0]
megasync(+0x613de0) [0x55c7bc91bde0]
megasync(+0x613de0) [0x55c7bc91bde0]
megasync(+0x613de0) [0x55c7bc91bde0]
megasync(+0x613de0) [0x55c7bc91bde0]
megasync(+0x613de0) [0x55c7bc91bde0]
megasync(+0x613de0) [0x55c7bc91bde0]
megasync(+0x613de0) [0x55c7bc91bde0]
megasync(+0x613de0) [0x55c7bc91bde0]
megasync(+0x633eb6) [0x55c7bc93beb6]
megasync(+0x674e01) [0x55c7bc97ce01]
/usr/lib/libstdc++.so.6(+0xe0c84) [0x7f66ca4e0c84]
/usr/lib/libc.so.6(+0x92ded) [0x7f66ca2a6ded]
/usr/lib/libc.so.6(+0x1160dc) [0x7f66ca32a0dc]

To be more precise, the error happens in the previous sync, and forced megasync to shutdown. The above log pops up when reruning megasync again. An error message also shows up after the program termination saying that the error may be due to insufficient storage, memory (both are not true), or file permission. I would like to check which file triggered the error for its permission, but I cannot seem to do it since the program terminates on its own. How do I resolve this?

vagelis commented on 2024-06-27 16:46 (UTC)

@bearbee yeah same here. Seems to be ok after the second time

bearbee commented on 2024-06-27 16:41 (UTC)

@vagelis I had the same issue but after rebuild and system restart everything was ok

I'm still using latest 4.x version instead of 5.x due to many issues with 5.x which were reported on github. Thus can't tell how 5.x will run after rebuild/restart.

vagelis commented on 2024-06-23 15:34 (UTC)

Thanx dbermond, I'll monitor and keep this in mind.

dbermond commented on 2024-06-23 15:30 (UTC)

@vagelis Either the rebuild was not properly made against the right ffmpeg, or you have something else depending on ffmpeg that also lacks a rebuild.

vagelis commented on 2024-06-23 11:27 (UTC) (edited on 2024-06-23 11:27 (UTC) by vagelis)

Hi there. After last update I get "megasync: error while loading shared libraries: libavcodec.so.60: cannot open shared object file: No such file or directory". I've managed to work around this after rebuild the package but after restarting my system the issue reappears. Any hints?

kirija commented on 2024-06-20 21:57 (UTC)

During syncing, I always get issue notifications of various reasons, such as duplicate names, incompatible file type, etc. This is issue detection is a new feature which I believe was introduced in the last few updates. The sync process won't proceed unless I manually address these issues. Why does megasync ask me to resolve duplicate names, isn't that one of the jobs of a synchronizer? Also these files that triggered issue have always been there and the previous version of megasync never had issue synchronizing them.

jlxip commented on 2024-06-19 19:13 (UTC)

@guiu.rocafort I was running into issues and installing those packages fixed it. They should definitely be added to dependencies; not build, but actual runtime dependencies.

1 2 3 4 5 6 .. 51 Next › Last »