Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Issue]: megasync 5.9.0 crashes immediately upon startup on devuan chimaera (bullseye), but seems to run on devuan daedalus (bookworm) #1058

Open
systemdlete opened this issue Mar 16, 2025 · 3 comments

Comments

@systemdlete
Copy link

Issue

Starting megasync 5.9.0 from your repos crashes immediately on Devuan Chimaera (bullseye). However, megasync 5.8.0 runs on Chimaera, and the 5.9.0 version runs on Daedalus.


Summary

The app starts to run, a window briefly appears, but the canvas does not get painted (I can still see the background). Then it disappears for a split second, reappears, then disappears again.


Steps to Reproduce (For Bug Reports)

List the steps to reproduce the issue:

  1. Install megasync 5.9.0 from the mega.nz repos.
  2. Start megasync (from command line or desktop menu or any other method; result is the same)
  3. Watch a window pop up and disappear twice.

What happened?

The program appears to have crashed, although I cannot find a corefile or any other traces of the run.


What did you expect to happen?

Expected the same login window to come up as I see on other systems running megasync successfully, such as 5.8.0 on Chimaera or 5.9.0 on Daedalus.


Environment Details

Provide details about the environment where the issue occurred.

Devuan Chimaera (Debian Bullseye without systemd)
XFCE4 desktop
VM with 4GB RAM and 4 CPUs
All installed system software and applications are up-to-date.


Additional Context

This is a system that does NOT run systemd. Hopefully, mega.nz does not hardcode systemd dependencies into its code (this has been a widespread problem elsewhere in the software kingdom).


@systemdlete
Copy link
Author

Didn't realize that there is a --debug option to megasync (would be nice/helpful if something like --help was also available; I thought megasync had no options at all!). So attached is a log.

Also, it appears that megasync DOES work on a different Devuan Chimaera instance. So it is something peculiar to the system-in-question, not a generic issue. Still, it would be nice to have more information rather than just quietly crashing, even with the debug log.

megasync.log

@vtmateos
Copy link
Member

Hi,
Does the app prompt you the crash report dialog after it crashed?
There should be some crashes under $HOME/.local/share/data/Mega Limited/MEGAsync that will contain the stack trace to analyse.
Please copy paste the stack trace of the crashed thread so we can verify what is happening.
Thanks.

@systemdlete
Copy link
Author

systemdlete commented Mar 18, 2025

The program did not prompt me for the crash report, but it did create a .dmp file each time it crashed. Log:

Application: MEGAsync [64 bit]
Version code: 50900.7
Module name: MEGA
Timestamp: 1742103585720
Operating system: Linux
System version:  devuan 4/#1 SMP Debian 5.10.226-1 (2024-10-03)
System release:  5.10.0-33-amd64
System arch: x86_64
Error info:
Illegal instruction (4) at address 0x7f3b5864e033
Stacktrace:
[0x7f3b5864e033]
[0x7f3b5864e033]

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants