meganz
Bad Version 5.2, 5.3, 5.4, 5.5!
After Update, every sync lists the same files again and again. Additional it delivers an error "could not sync...because fie has changed local and remote. But I only deleted some old versions of that file. Where can I get an 4.12.2 deb ???
To make working versions unavailable, and replace them by "beta"-versions is not a good idea. Significantly reduces trust in the development / developers. I NEVER will install an update, if i have no install package of the predecessor.
I have the same problem in Debian 12. Where can we get the 4.12.2 deb version?
I can understand that any release has bugs and regressions, but it seems very poorly planned that a major change is made without proper notice and, to make matters worse, the previous version is no longer available immediately after each new version.
I have had to go back to the previous version from the same day. I don't know if it will fail the same on Windows or Mac, but on Linux some of my normal folders appeared as if they were "linked folders" (I don't know the reason...) and it didn't let me synchronize about 200 files.
I have the official version prior to this one. I don't think that I'm breaking the rules by sharing it for those who need to go back to the previous version to avoid bugs:
https://mega.nz/file/8FYWEJIB#bF7NLl9VhRH3HNd5QHvQSJBSUPiCjgT4uYZHPe5MiTE
Note: I only have the version equivalent to Ubuntu 20.04. I don't know the compatibility with other versions.
@p1xt4n @MAlfare
Regards.
Please, you should do something about this issue, as of right now, users on Ubuntu 20.04 to 22.04 seems to can't use the app. I have the same issue on 22.04 and I can't install the previous version, as it is made unavailable directly when the new version comes out. I can't sync my files to my filesystem for a week now.
Please fix the issue As soon s possible. Thanks
Dear users,
Apologies for the inconveniences. From v5.2.0 we are rolling out the new sync v2 algorithm that will boost and enhance the sync process. Please, reach our help desk team sending an email to support describing your specific issue, so we can help you with that.
Regards.
Hi!
The first thing I noticed, was that the same file name scrolled through during the sync. This is unnecessary, but apparently harmless.
Then there was a warning "Problem detected". This contained the reason: "File changed both locally and in the cloud". This concerned files that I synchronize daily.
I have NEVER changed files in the cloud! Why would I do that?
So I always chose to keep the local file.
Then one file was "moved" to another, that has nothing to do with each other, except that they are in the same directory. I then found this file in the version list of the other file, which was immediately noticeable due to its size (approx. 367kB / 5.5MB).
It then messed up several files, that were stored together in a completely different directory. A file that was always larger than 27MB, suddenly had 3MB, which is the size of another file, that has now suddenly 5.2MB. Since this is binary data, I can't say anything about the content.
I hope this information is helpful.
Regards Manfred
Another example for mixed up files! The older and smaller one cannot be opened. The file was NEVER edited, neither local nor in the cloud, so there should be not two versions! Beside the fact, that this file was created on March 28th and definitely did NOT exist on March 26th!
And now I can guess what file, 15kB in size, was killed 🙁
It was an Open Document File named "Jahresausgleich_2024.ods"
alf@Ida ~/Schreibtisch $ file Zahnarzt_15signed.pdf Zahnarzt_15signed.pdf: OpenDocument Spreadsheet
I can no longer recommend Megasync for data backups with a clear conscience.
Dear users,
Apologies for the inconveniences. From v5.2.0 we are rolling out the new sync v2 algorithm that will boost and enhance the sync process. Please, reach our help desk team sending an email to support describing your specific issue, so we can help you with that.
Regards.
I did on April 10th. Ticket ID: CZE-114-43157 Subject: MEGAsync Issue Department: Support Got a reply om April 17th Sent a reply the same day, answering a lot of questions including a link to a zip-file, containing log-file and screen shots, which is not downloaded til at least 3rd of Mail. On Mai, 3rd I got a receipt mail, telling me, that my response will be forwarded.
A few more examples of how MEGAsync throws file names and file contents together. But nobody seems to be interested.
Upgrade: megasync:amd64 (5.2.0-2.1, 5.2.1-4.1) on 27.04.2024 SAME SHIT! Files was created on 29.04.2024, all "versions" before are different files !!!
Worst because non-existent support I have ever experienced Nobody is reading here, and nobody does react on my feedback to: [email protected] [email protected] [#CZE-114-43157]: MEGAsync Issue
I am not a user who usually complains because I understand the difficulties and frenetic pace of work in companies dedicated to software development. However, while I appreciate that Mega has a client for Linux, I do criticize that, like many other companies, it doesn't mind treating Linux users as second-class customers.
megasync 5.2.1 is still eating my data and regurgitating it with a different name :-(
Hello all, for those like me using mint 21.3 (ubuntu 22.04 based) I could solve the issue installing megasync 4.12.2 for ubuntu 20.04 (shared in this thread) at first if you tray to install will receive an error about dependencies not met. you need to download a couple of packages, links below, and the install will carry on successfully. I've install in two laptops with mint 21.3 and works as it should be.
http://security.ubuntu.com/ubuntu/pool/main/i/icu/libicu66_66.1-2ubuntu2.1_amd64.deb http://security.ubuntu.com/ubuntu/pool/main/o/openssl/libssl1.1_1.1.1f-1ubuntu2.22_amd64.deb
@safdemonte Your instructions are well meant, thank you for that. But I'm certainly not going to mess up my system with packages that aren't made for it in order to get around the crap that the developers have produced with 5.2. Unfortunately, they have no great interest in correcting their mess. Which ultimately means not relying on MEGA and using other/additional backup solutions.
It's been more than three months now.
I have not updated yet from version 4.X.X because of the bugs. Mega makes the argument that it is recommended to always use the latest version and does not provide access to older versions, even provisionally. This is nonsense!
Do they expect us to leave our devices unusable due to a bad update? There may be a stable channel and a beta channel.
Regards.