element-hq / element-hq/element-web

Account gets logged out after previously failing libsecret access

Open
#32,121 19 comments 4 reactions 0 assignees View on GitHub
A-Electron A-Session-Mgmt O-Uncommon S-Major T-Defect
Dominant language
TypeScript
Stars
13.5k
Forks
2.8k
PR merge metrics
PR metrics pending

Description

### Steps to reproduce

1. Start element-desktop on a new profile `element-desktop --profile-dir=/tmp/element-testing` while having a libsecret backend running and available for element to write session and seshat credentails
2. Log into an account
3. Close element-desktop ^C
4. Open it again (this time blocking libsecret access which would happen over DBus) `firejail --noprofile --nodbus element-desktop --profile-dir=/tmp/element-testing`
5. Close element-desktop again ^C
6. Open it again `element-desktop --profile-dir=/tmp/element-testing`

### Outcome

#### What did you expect?

I should stay logged into the account or at least view a cached version of it because credentials couldn't be retrieved from libsecret

#### What happened instead?

I see the login screen again, probably because libsecret failed the last time element-desktop started.

### Operating system

NixOS & Debian

### Application version

Element Desktop 1.11.53

### How did you install the app?

nixpkgs unstable & packages.element.io/debian

### Homeserver

matrix.org and selfhosted Synapse 1.98.0

### Will you send logs?

Yes (these were sent from the element running as `firejail --noprofile --nodbus element-desktop --profile-dir=/tmp/element-testing`, as per the steps above)

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.