Package Details: megasync 5.5.0.0-2

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: 380
Popularity: 0.26
First Submitted: 2014-09-01 18:12 (UTC)
Last Updated: 2024-10-06 03:37 (UTC)

Latest Comments

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

dbermond commented on 2024-10-06 03:37 (UTC)

@ewilcox there are lots of building warnings, and not only this one you mentioned. They should be reported upstream, and not here downstream. Checksums fixed.

ewilcox commented on 2024-10-05 22:44 (UTC)

While attempting to update MEGAsync to version 5.5.0.0_Linurx,pamac produced the following error output:

Refreshing AUR... Cloning megasync build files... Generating megasync information... Checking megasync dependencies... Resolving dependencies... Checking inter-conflicts...

Building megasync... ==> Making package: megasync 5.5.0.0-1 (Sat 05 Oct 2024 06:38:39 PM EDT) ==> Checking runtime dependencies... ==> Checking buildtime dependencies... ==> Retrieving sources... -> Updating MEGAsync git repo... -> Updating meganz-sdk git repo... -> Found 010-megasync-freeimage-remove-obsolete-ffmpeg-macros.patch -> Found 020-megasync-sdk-fix-cmake-dependencies-detection.patch -> Found 030-megasync-app-fix-cmake-dependencies-detection.patch ==> ERROR: Integrity checks (sha256) differ in size from the source array. Failed to build megasync

ewilcox commented on 2024-10-05 14:41 (UTC)

While building MEGAsync, I noted the following Warning (I don't know if it's important, but I wanted you to know):

/usr/src/debug/megasync/MEGAsync/src/MEGASync/mega/src/megaclient.cpp: In member function ‘pw_key’: /usr/src/debug/megasync/MEGAsync/src/MEGASync/mega/src/megaclient.cpp:9360:40: warning: argument 1 value ‘18446744073709551615’ exceeds maximum object size 9223372036854775807 [-Walloc-size-larger-than=] /usr/include/c++/14.2.1/new:133: note: in a call to allocation function ‘operator new []’ declared here 133 | _GLIBCXX_NODISCARD void* operator new _GLIBCXX_THROW (std::bad_alloc)

3xploiton3 commented on 2024-09-14 02:07 (UTC)

i got error 

--   Package 'libpdfium', required by 'virtual:world', not found
CMake Error at /usr/share/cmake/Modules/FindPkgConfig.cmake:645 (message):
  The following required packages were not found:

   - libpdfium

Call Stack (most recent call first):
  /usr/share/cmake/Modules/FindPkgConfig.cmake:873 (_pkg_check_modules_internal)
  src/MEGASync/mega/contrib/cmake/modules/sdklib_libraries.cmake:142 (pkg_check_modules)
  src/MEGASync/mega/contrib/cmake/modules/sdklib_target.cmake:327 (load_sdklib_libraries)
  src/MEGASync/mega/CMakeLists.txt:135 (include)


-- Configuring incomplete, errors occurred!
==> ERROR: A failure occurred in build().
    Aborting...
 -> error making: megasync-exit status 4
 -> Failed to install the following packages. Manual intervention is required:
megasync - exit status 4

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.

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