Bug: Appimage searches for old wallet and creates filepath to non existant path.

[bardicreels]

Debian
Latest zano appimage

A few weeks ago i tried out a zano appimage, then deleted it.
Recently, i downloaded a new version
the new version still looks for the old wallet despite having had removed it a while ago.
Log of launch does not show what action is searching for the the file
Catfish search for the filename of the wallet cannot be found nor any other file named "zano" on the system

the appimage will also create a path to where it expects the wallet file to be if it does not exist.

Something is staying behind despite removing the appgimage

[bardicreels]

it's troubling that i cannot run zano appimage in a firejail.

**got it to open with --appimage prepend , it still looked for the old wallet

[bardicreels]

so you are saying a glitch in the zano cloud tracks my computer despite having removed all local references i know of or can find ?

[bardicreels]

can confirm, it somehow knows the location of the previous wallet from a different appimage a week or so ago, despite being in firejail with its own home directory

[bardicreels]

Ok, fixed it. i ran the following after a deep search

sudo rm -r ~/.cache/Zano/
sudo  rm -r ~/.Zano/

then i firejailed the F#@$ out of zano with a strict isolation config under ~/.config/firejail/zano.profile

\# Firejail profile for Zano AppImage

\# Private home directory
private ./zano

\# Allow network access
netfilter

\# Restrict file creation
nonewprivs

\# Include common security restrictions
include /etc/firejail/disable-common.inc
include /etc/firejail/disable-programs.inc

# Ignore specific blacklist entry
ignore blacklist /etc/systemd/network

then

mkdir -p ./zano

I then run it with

firejail --appimage --private --profile=~/.config/firejail/zano.profile zano-linux-x64-develop-v2.0.1.367_d63feec.AppImage 

and its files do not appear where they are not supposed to.

Looks like nothing malicious (as the previous cloud glitch suggestion that is now marked as spam suggested) and just a creation/cleanup oversight at runtime
Appimages and the whole point of appimages is to be contained so i recommend better design unless you want to become a virus like bloatware like snapd (which i also noticed was lingering and cleaned up while undergoing this project, so thanks i guess. It sucks that even dpkg purge and apt "auto*" doesn't seem to remove everything.

[bardicreels]

another issue that might be part of the is that i have "appimage launcher" installed, it creates system wide access for all appimages in a designated folder. I moved the appimage out of that directory and it works fine after the above with no duplication.

[bardicreels]

Note: It still re downloads the entire blockchain at ./zano/.Zano/blockchain_lmdb_v2/, from 0% despite having it's own local persistent home directory while using firejail

** this appears to be due to the database structure will test letting the full blockchain download

[bardicreels]

the already included appimage argument "--no-sandbox false" might negate all this, just found it

[sysfu]

I'm having what I believe to be a related issue with zano-linux-x64-develop-v2.0.1.367.AppImage. It creates data and pocketcoind folders in the root of my home directory. ???

I would like it to store configuration and wallet files in ~/.config/zano as per modern *nix convention, and anything else in ~/.local/

[cryptozoidberg]

@bardicreels thanks for the opening issue, AppImage aims to allow the installation of binary software independently of specific Linux distributions, for exactly that reason we are using it.
AppImage does not enforce sandboxing as far as i'm aware(correct me if i wrong). If you willing to improve AppImage script feel free to create PR, it would be much appreciated.

@sysfu I believe Zano can't create anything named "pocketcoind" anywhere on your computer, it's not a part of our project. Regarding working folders we'll take a look at the latest *nix recommendations (@sowle can you take a look into it?).
I'm closing this issue, but if anyone have an issues feel free to reopen it.

[sysfu]

@bardicreels thanks for the opening issue, AppImage aims to allow the installation of binary software independently of specific Linux distributions, for exactly that reason we are using it. AppImage does not enforce sandboxing as far as i'm aware(correct me if i wrong). If you willing to improve AppImage script feel free to create PR, it would be much appreciated.

@sysfu I believe Zano can't create anything named "pocketcoind" anywhere on your computer, it's not a part of our project. Regarding working folders we'll take a look at the latest *nix recommendations (@sowle can you take a look into it?). I'm closing this issue, but if anyone have an issues feel free to reopen it.

Sorry, the ~/pocketcoind and ~/data directories were from Bastyon AppImage, not Zano.

I appreciate you looking into tucking the Zano directories under ~/.config/ and ~/.local

[cryptozoidberg]

@sysfu i've mentioned issue with recent linux working folder recommendations in other issue #490 (comment) , should be fixed in one of nearest releases. Once again thanks for reporting it!