Crash on startup upgrade dialog

[summoner001]

When I launch the Megasync application this window pops up:

Security upgrade

Your accounts security is now beeing upgraded. This will happen only once. If you've seen this message for this account before, click cancel.

When I click on cancel -> the application exits
When I click on yes -> Failed to upgrade security. Error: Temporarily not available

Problem occured in this release: https://aur.archlinux.org/packages/megasync-bin

OS: Latest Arch Linux
Current installed release: https://aur.archlinux.org/packages/megasync-bin
The same problem is present in the megasync 5.2.0.0-1 - https://aur.archlinux.org/packages/megasync version.

[sallirom]

I have exactly the same problem, sync unusable.

[saflo76]

I have 2 Arch linux machines, one works fine even with latest megasync version, the other went with this error since the major update version (5.2) and the error still persists with last 5.2.1-4 package.
Cannot evince anything in journal to understand what triggers this issue, I tried to wipe any of my userspace data and package reinstall, but at the moment of signing with my mega account right after confirmation the error described above happens and program apparently crashes.

[meatspinner]

Same here. I've tried to install from both the official repo as well as AUR and Chaotic AUR but the issue persists; Logging out through the website and log in through the app does nothing to solve the issue.

Not sure if either KDE 6 or Arch is the problem.

[summoner001]

@meatspinner I'm using gnome46 so I don't think it's a kde 6 problem.

[sallirom]

@meatspinner I'm using gnome46 so I don't think it's a kde 6 problem.

yeah, same here. I have Manjaro with KDE in one machone and Manjaro with XFCE in another one. The problem appears on both of them.

[meatspinner]

@meatspinner I'm using gnome46 so I don't think it's a kde 6 problem.

@meatspinner I'm using gnome46 so I don't think it's a kde 6 problem.

yeah, same here. I have Manjaro with KDE in one machone and Manjaro with XFCE in another one. The problem appears on both of them.

Its likely an Arch issue then. I'll try to install either the flatpak package or an older version of megasync to see if I can sync, at least temporarily.

[Randal400]

I have two machines with ARCH + XFCE, one has the same problem and the other works well.

I don't know what is happening but is disappointing

[saflo76]

I can't be in front of the issue machine now but from the other (the one which works) I have discovered that if you run from terminal megasync with --debug parameter you can follow all debug messages for internal program operations, this may turn useful to spot something for bugged cases.
I will try it later in the "bugged" installation.

[veroneze]

05/09-16:32:43.097337 140595241363136 INFO Request (UPGRADE_SECURITY) starting [megaapi_impl.cpp:16457] 05/09-16:32:43.097391 140595241363136 DBG Upgrading cryptographic subsystem. [megaclient.cpp:11368] 05/09-16:32:43.097397 140595241363136 WARN Keys not available [megaclient.cpp:11391] 05/09-16:32:43.097403 140595241363136 WARN Request (UPGRADE_SECURITY) finished with error: Temporarily not available [megaapi_impl.cpp:16499]

[meatspinner]

I've tried everything I could think of and the only thing that worked was this AUR package:

https://aur.archlinux.org/packages/megasync-nopdfium
(For some reason the URL isn't working so you've to copy the URL text).

Its a temporary fix until the devs fix the issue.

[sallirom]

THANK YOU, thank you so much for the heads up, this was extremely helpful. 🙏

I've tried everything I could think of and the only thing that worked was this AUR package:

https://aur.archlinux.org/packages/megasync-nopdfium (For some reason the URL isn't working so you've to copy the URL text).

Its a temporary fix until the devs fix the issue.

[Randal400]

I've tried everything I could think of and the only thing that worked was this AUR package:

https://aur.archlinux.org/packages/megasync-nopdfium (For some reason the URL isn't working so you've to copy the URL text).

Its a temporary fix until the devs fix the issue.

Then I would have to uninstall the official app and install this from AUR?

[meatspinner]

I've tried everything I could think of and the only thing that worked was this AUR package:
https://aur.archlinux.org/packages/megasync-nopdfium (For some reason the URL isn't working so you've to copy the URL text).
Its a temporary fix until the devs fix the issue.

Then I would have to uninstall the official app and install this from AUR?

I think so, for now. I don't think you can have both versions installed at the same time.

[vtmateos]

Dear users,
A new update for ARCH has been pushed in order to fix some linking issues with libs. Please update and let us know if there is any other problem. Thanks.

[Randal400]

I made the update but the problem continues :-(

[summoner001]

Megasync-bin the problem is still there in v5.2.1-5

[vtmateos]

Hi,
v5.2.1-5 is an AUR package that MEGA does not offer support for. We have updated our Arch packages under this repo url https://mega.nz/linux/repo/Arch_Extra/x86_64/

Did you test the ArchLinux version from the MEGA repo?

[summoner001]

I checked the package you linked. I think it's the same as the package in AUR, just with a different maintainer, but I won't argue. I installed it. Yes, the problem is also present in the official package.

[vtmateos]

Hi,
The package deals with some linking issues that avoid running the app on Arch linux. It seems that this is a different issue with the current logged account in MEGAsync. Please, would you mind to contact our support system so they can perform some check ups over your accounts?

They will help with that.

Apologies for the inconveniences.

[summoner001]

This is not an account problem. I can't even log in through the app because the window that you see in the screenshot pops up before the login window...

[vtmateos]

Hi,
You are already logged in from previous execution, that is why the log in dialog does not pop up. You have still an active session.
Please, if you want further assistance reach our support team so they will ask for your account and they can perform some verifications. [email protected].

Thanks.

[summoner001]

Ok I understand now. I wrote to support about this. Thank you! have a nice day!