github12101
commented
5 years ago As for "stuck at 100%" it's currently extracting the database into the correct folder.... as you say 3.83 GB worth. Once finished it will automatically restart the core and you'll continue syncing the remaining blocks normally, although it should say "extracting database" or something to inform the user of this process.
Upon finished downloading there should be a message - unpacking! Must be added, as this process can take as long as downloading did. And core must be stopped while bootstrap is being downloaded.
Right now, I can see from terminal, core has been stopped and restarted again to accept bootstrap, my guess when zip file has been already unpacked. It should be stopped when downloading is started, not when file is unpacked.
$ ./nexus_wallet-Linux-1.1.0.AppImage
19:30:26.559 › File server listening on port 9331!
19:30:27.001 › Checking if core binary exists: /tmp/.mount_nexus_iVvcYZ/resources/assets/linux/cores/nexus-linux-x64
19:30:27.002 › Core binary exists
19:30:27.002 › nexus.conf exists. Importing username and password.
19:30:27.002 › Core Parameters: -daemon,-avatar,-server,-rpcthreads=4,-fastsync,-datadir=/home/pioruns/.Nexus,-rpcport=9336,-verbose=0,-stake=1
19:30:27.003 › Core Manager: Starting core
19:30:27.010 › Core Manager: Core has started (process id: 3324)
pos 462 201
20:30:24.524 › Core Manager: Stop function called
20:30:27.768 › Core Manager: Core still running after stop command for: 0 seconds, CorePID: 3331
20:30:28.800 › Core Manager: Core still running after stop command for: 1 seconds, CorePID: 3331
20:30:29.828 › Core Manager: Core still running after stop command for: 2 seconds, CorePID: 3331
20:30:30.868 › Core Manager: Core still running after stop command for: 3 seconds, CorePID: 3331
20:30:31.900 › Core Manager: Core still running after stop command for: 4 seconds, CorePID: 3331
20:30:33.010 › Core Manager: Core stopped gracefully.
20:30:34.613 › Checking if core binary exists: /tmp/.mount_nexus_iVvcYZ/resources/assets/linux/cores/nexus-linux-x64
20:30:34.613 › Core binary exists
20:30:34.613 › nexus.conf exists. Importing username and password.
20:30:34.740 › Core Parameters: -daemon,-avatar,-server,-rpcthreads=4,-fastsync,-datadir=/home/pioruns/.Nexus,-rpcport=9336,-verbose=0,-stake=1
20:30:34.740 › Core Manager: Starting core
20:30:34.769 › Core Manager: Core has started (process id: 3530)
KenCorma
Describe the bug Just downloaded nexus_wallet-Linux-1.1.0.AppImage 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. I can see Licence Agreement I can click Yes, but it fails with error
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.