-
Notifications
You must be signed in to change notification settings - Fork 12
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
nexus_wallet-Linux-1.1.0.deb doesn't work - critical error #55
Comments
Please note, previous version of the wallet has worked on this machine without this error (Window worked and GUI was present, but wallet failed to synchronize). This is potentially a regression from previous version. |
@KenCorma could you verify this and the AppImage issue on Linux? |
Possible explanation here: electron 5.xx issue |
Just installed Debian 10 Buster on AMD64 machine. Nexus .deb package can't even be installed, reason:
Package on which Nexus-wallet is dependant on, doesn't even exist in Debian 10 Buster. |
Foundry376/Mailspring#998 (comment) Again, not a wallet issue, but an issue with a depreciating dependency. But the link above should fix that issue. However, it still will error out due to the electron builder issue. |
Why this is not tagged as BUG? Why no one is assigned to this issue? |
Closing this as the resolve is the same as Appimage |
Describe the bug
Just installed nexus_wallet-Linux-1.1.0.deb on Linux MX (Debian Stretch with improved GUI). Wallet fails with critical error.
To Reproduce
This is stock Linux, nothing has been changed and I have no knowledge of any custom changed made to sandbox helper or whatever that is.
Expected behavior
nexus-wallet command should start wallet
Screenshots
not required
Desktop (please complete the following information):
$ uname -a
Linux mx 4.19.0-5-amd64 #1 SMP Debian 4.19.37-2~mx17+1 (2019-05-15) x86_64 GNU/Linux
$ lsb_release -a
No LSB modules are available.
Distributor ID: MX
Description: MX 18.3 Continuum
Release: 18.3
Codename: Continuum
All packages are from Debian Stretch.
The text was updated successfully, but these errors were encountered: