[FR]: Option to set the --password-store option globally
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
Research direction
Start by reading the Helium Linux launcher and configuration entry points to see how command-line flags are passed to browser instances. The issue leaves the storage location open between settings, helium://flags/ and a config file, so first identify the project’s existing settings and flag handling. Done means launches from any application use the configured password store; the issue names no files or tests.
Written by the indexing model from the issue text.
Description
Description
A setting, either in the settings UI, as part of helium://flags/ or in some config file, which sets the --password-store flag
Who's implementing?
- I'm willing to implement this feature myself
The problem
I am running niri on Fedora KDE, so I'm using KWallet as my encryption key store. I think since I'm not on the Plasma environment, helium doesn't recognize that it should be using KWallet and falls back to some other key store. To fix this I set my launcher to start helium with the --password-store=kwallet6 flag. This works, however other launchers (like when opening a PDF with helium from Dolphin's context menu) don't have this flag configured. This results in me being logged out from every website.
Possible solutions
I suggest adding a way to set the --password-store flag globally, so that every program that launches helium uses the correct key store. The setting could be part of the settings UI, helium://flags/ or in another configuration file.
Additional context
Environment: Fedora 44, niri + KDE (KWallet 6), Helium 0.19.4.1 (Chromium 155.0.8059.84)
My current hotfix is a wrapper script inside .local/bin/ which launches helium with the correct flags, but I would like to not need it.
- Dominant language
- Shell
- Stars
- 1.1k
- Forks
- 63
- Avg merge
- 28m
- Merged PRs (30d)
- 11
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- No contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from imputnet/helium-linux
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 63/100
imputnet/helium-linux#385 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 48/100
imputnet/helium-linux#459 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 38/100
imputnet/helium-linux#457 ·
Maintainers usually reply within 1 day
-
feat
Difficulty 3/5 1-2 days Newbie friendliness 48/100
imputnet/helium-linux#455 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 48/100
imputnet/helium-linux#454 ·
Maintainers usually reply within 1 day
All issues in imputnet/helium-linux
Similar issues
-
enhancement good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
varnish/helm-varnish#173 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
command: update-lgsm distro: Debian engine: source2 game: Counter-Strike 2 regression: yes reproducible: always severity: low type: bug
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
GameServerManagers/LinuxGSM#5242 ·
Maintainers usually reply within 1 day
-
📦 Update Request
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
cdnjs/packages#2225 · 1 comment ·
Maintainers usually reply within 3 days