I'd like to start the AppImage (defi-app-2.3.1.AppImage)
However this is not easy. May be their is a fault on the Image or I have missing information.
I expected to start the defi-app-2.3.1.AppImage just by clicking it as user without error messages.
What I see is, sandbox needs root access for tmp/.mount_defi..., however sandbox is not allowed under root access. This is the point where the cat bits itselfs in the tail.
I have an AppImage running on the other Linux-PC with the same behaviour, but maybe error ((defi-app:10627): libnotify-WARNING **: 13:30:17.697: Failed to connect to proxy) I get on that terminal has to do with the missing sandbox. See my other issue #609.
@Martin8617: Thanks for opening an issue, it is currently awaiting triage.
The triage/accepted label can be added by foundation members by writing /triage accepted in a comment.
In the meantime, you can:
Details
I am a bot created to help the DeFiCh developers manage community feedback and contributions. You can check out my manifest file to understand my behavior and what I can do. If you want to use this for your project, you can check out the DeFiCh/oss-governance-bot repository.
Hi @Martin8617 , thanks for your feedback, please give us time to investigate this. The team has halted v2.3.1 at the moment due to some issues. I'll update you again when the team fixes it and is ready for release.
Hi @Martin8617 , update v2.3.2 is out, this is a mandatory update. 鈥≒lease read through the release notes before updating.
Do give a thumbs up to this comment if your issue has been resolved, otherwise, please send new information (include screenshots) and app logs. Thank you
Hi Bella, the problem isn't related to 2.3.1.
I had it with 2.3.0 too. Please find the logs from the DeFi-Wallet-2.3.2.AppImage - it's the same.
Additional information: The libnotify-warning: Failed to connect to proxy occurs when I open the wallet with the password (wallet works even with this warning...)
Remark to the closed issue #609:
I just use the DeFi-Wallet for the MN-Owner now. MN-Operator runs with defid 1.6.1 without change of firewall or network settings with inbound connection. I believe the use of "no-sandbox" has influence of the rpc configuration (see debug-app.log) as well as of the blocking of inbound connection.
200402.zip
I see blockchain works, libnotify is engine for showing desktop notifications it does not have anything related to the blockchain, it's a part of Electron. --no-sandblox is required when you run as root, why you want to do that?
Hi @Martin8617 , the team as investigated your logs, the error you faced Unable to bind to 0.0.0.0:8555 on this computer. DeFi Blockchain is probably already running did your app start?
@bvbfan: I have to run as root because the app opens an tmp-folder (/tmp/.mount_defi...) and this is only able with root-access. As a consequense the --no-sandbox has to be added.
@izzycsy: Yes, the app starts and works.
The normal permissions of /tmp are drwxrwxrwt so that's mean 1777 changing them makes you a responder. So you should take this personally and solve it for you.
@bvbfan, I have an idea what you mean, however I don't know who to solve this permission issue...
Hi @Martin8617 , v2.4.0 is out, this is a mandatory update. Please read through the release notes before updating. _This comment is to notify you about the update._
Hi @Martin8617 v2.4.2 is out, this is a mandatory update. Please read through the release notes before updating. _This comment is to notify you about the update._
Posting non-bug related issues here will eventually turn stale. For future Linux related post (if it's not a suspected bug) you can post your idea on DeFiChain Discussions, share your findings with the community. In the mean time, I'll provide a link to Linux: Running the app as a webapp #736 , there are other community members in discussion on an idea that might be related.