Skip to content
This repository has been archived by the owner on Jun 7, 2023. It is now read-only.

Seeing install libsecret-1-dev message even if its installed #1630

Closed
aayush opened this issue May 28, 2019 · 4 comments · Fixed by #1638 or #1656
Closed

Seeing install libsecret-1-dev message even if its installed #1630

aayush opened this issue May 28, 2019 · 4 comments · Fixed by #1638 or #1656
Assignees
Labels
C - Desktop L - Assigned Lifecycle - Somebody is working on this L - Has PR P - Linux Platform - Specifically relates to Linux T - Bug Type - Bug: Something isn't working

Comments

@aayush
Copy link

aayush commented May 28, 2019

Bug description

With this version trinity-desktop-0.5.1.AppImage i am seeing libsecret error.
It is asking me to install libsecret-1-dev. I installed it but still seeing this issue.
Someone in discord asked me to check if gnome-keyring is installed. gnome-keyring was installed in my system before i install libsecret-1-dev

Environment Specs

I am running it on ubuntu 18.04

What build of Trinity are you running?
trinity-desktop-0.5.1.AppImage

Steps To Reproduce

Just start that app from terminal.

Expected behaviour

App should have started, i should have seen authentication screen.

Actual behaviour

What really happened.

Errors

Screen Shot 2019-05-27 at 5 17 39 PM

Attach crash logs or screenshots of error messages if available. Please ensure that these files do not contain any personal information.

@aayush aayush added the T - Bug Type - Bug: Something isn't working label May 28, 2019
@rajivshah3 rajivshah3 added C - Desktop P - Linux Platform - Specifically relates to Linux labels May 28, 2019
@aayush
Copy link
Author

aayush commented May 28, 2019

I was not seeing this error in version 5.0, i switched to 5.1 and seeing this error message

@rajivshah3
Copy link
Member

rajivshah3 commented May 28, 2019

@rihardsgravis do you think #1548 caused this? The only change was in this commit

@rajivshah3 rajivshah3 added the P2 - High Priority - Prefer to fix or merge this label May 28, 2019
@rajivshah3
Copy link
Member

Ah wait, I think I might know what happened. If you’ve backed up your seeds/Ledger account indexes, could you try resetting the wallet to see if that helps?

@rajivshah3
Copy link
Member

rajivshah3 commented May 28, 2019

The app is probably running into an error at launch, but it’s not related to libsecret. When we started showing errors on launch to the user so that they (and we) could see what was actually happening instead of a blank screen, we used a screen that is already used to show error messages to Linux users. This screen would show a specific message if a certain error happened, and the missing dependencies message for all other issues. When we added support for showing the error to the user, there was an issue with the implementation:

{typeof Electron === 'object' && Electron.getOS() === 'linux' ? linuxContent() : generalContent()}

This would cause Windows and macOS users to see the error, but Linux users would see the missing dependencies message for almost any error, even ones unrelated to the keychain

@rihardsgravis rihardsgravis self-assigned this May 28, 2019
@rihardsgravis rihardsgravis removed the P2 - High Priority - Prefer to fix or merge this label May 28, 2019
@rajivshah3 rajivshah3 added L - Assigned Lifecycle - Somebody is working on this L - Has PR labels May 28, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
C - Desktop L - Assigned Lifecycle - Somebody is working on this L - Has PR P - Linux Platform - Specifically relates to Linux T - Bug Type - Bug: Something isn't working
Projects
None yet
3 participants