Linux: Remember Password fails silently when there is no default keyring

Open Beginner friendly
  • Is something wrong?
#4,098 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

@datlechin is already working on this.

Since Nov 8, 2026.

  • #4105 by @datlechin — open

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
75/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
swift
Domain
databases, desktop

Research direction

Start by tracing the Remember Password flow and how it handles the locked-keyring message; the issue does not name source or test files. Check how the app detects that a secret was not stored, then compare its recovery guidance with troubleshooting.md under “Flatpak connections.” Done means the user is told the password was not saved, why, and how to create a default keyring.

Written by the indexing model from the issue text.

Description

bug platform-linux

With no default keyring, Remember Password does nothing and says nothing.

  • Seen on the beta.3 Flatpak, Fedora 44 Workstation, GNOME 50.6, automatic login with no "login" keyring yet.
  • Connect with Remember Password connects, but the password is not stored. Only the log says so ("a secret was not stored … the keyring is locked"). The next launch asks for the password again.
  • Expected: tell the user the password was not saved and why, with the same recovery as the locked-keyring message (troubleshooting.md, Flatpak connections: create a default keyring).
  • Found by the beta.3 smoke pass (#4089, known issue 6).
Dominant language
Swift
Stars
6.2k
Forks
412
Avg merge
3h 56m
Merged PRs (30d)
669

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from TableProApp/TablePro

All issues in TableProApp/TablePro

Similar issues

More Swift issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.