-
Notifications
You must be signed in to change notification settings - Fork 120
App doesn't recognize installed dependencies #621
Comments
Same problem/bug is on Ubuntu 18.04.1 LTS. All asked libraries installed but still the message with "Missing security dependencies". Additionally I Installed Trinity Wallet on a new laptop and got there a stuck after "choose your ledger account index" like #589 . |
Is this still reproducable with Trinity desktop |
Hi Rihards, updated from 0.4.2 to 0.4.3 and still the same problem (Ubuntu 18.04.1 LTS). |
Can finally reproduce when running the wallet as root user ( |
OK thanks :) |
Closed in #779 |
Wanted to try Trinity Wallet on Ubuntu 18.04.1 LTS. Have the same issue. Downloaded trinity-desktop-0.4.6.AppImage. All dependencies are up to date. Someone else this problem again with Trinity Wallet 0.4.6? |
@DannyS86 is the |
@DannyS86 do you run App with sudo? Only work when you do NOT start with sudo |
@IOTANGLE42 yes, I started with sudo. Without the trinity wallet won't come up without displaying any information in the Terminal. |
I've deleted the folder |
@luca-moser thank you, that's it! Deleting the |
I got the same issue on Debian 9.6 (stretch) and Ubuntu 16.04 (xenial)
gnome-keyring-daemon is running (tested with seahorse) and i'm not root. The keytar example mentioned in atom/node-keytar#132 actually does work here, showing my password. |
I will close this issue as the original issue is reported to be fixed (Trinity doesn't register correctly as an application should be opened as a new issue). |
Bug description
Trinity Desktop is unable to correctly determine the installed dependencies shown by "Missing security dependencies" screen:
Screenshot from 2018-11-21 12-49-01
![image](https://user-images.githubusercontent.com/1385611/48839441-d683d080-ed8b-11e8-80fa-e9f6208990f2.png)
Environment Specs
Ubuntu 18.10 64x
Steps To Reproduce
Expected behaviour
Trinity should start and recognize the dependencies.
Actual behaviour
The "Missing security dependencies" screen is shown.
The text was updated successfully, but these errors were encountered: