Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#61354 - [chromium] unlocking keyring

Attached to Project: Arch Linux
Opened by Alberto Salvia Novella (es20490446e) - Friday, 11 January 2019, 14:53 GMT
Last edited by Evangelos Foutras (foutrelis) - Saturday, 12 January 2019, 17:39 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To No-one
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Chromium requires libgnome-keyring (optional) for being able to unlock its keyring. Otherwise it asks for a password on each first launch, for each new user session.
This task depends upon

Closed by  Evangelos Foutras (foutrelis)
Saturday, 12 January 2019, 17:39 GMT
Reason for closing:  Works for me
Additional comments about closing:  Make sure the keyring gets unlocked on login.
Comment by Alberto Salvia Novella (es20490446e) - Friday, 11 January 2019, 14:57 GMT
Perhaps a better solution is to make chromium dependent of libgnome-keyring and not gnome-keyring, as this second package is already optionally dependent of the first one.
Comment by Evangelos Foutras (foutrelis) - Saturday, 12 January 2019, 09:01 GMT
Chromium uses libsecret so libgnome-keyring is not needed. It sounds like you need to figure out why your keyring isn't unlocked on login.

https://wiki.archlinux.org/index.php/GNOME/Keyring#With_a_display_manager
Comment by Alberto Salvia Novella (es20490446e) - Saturday, 12 January 2019, 17:18 GMT
The keyring unlocks automatically on login, but it seemed to fail from time to time. Nevertheless, for some reason, it isn't happening now.

Loading...