Bug 1477067 - Gnome Keyring no more unlocked at session startup
Summary: Gnome Keyring no more unlocked at session startup
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: sddm
Version: 26
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Jiri Eischmann
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On: 1467734
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-08-01 07:43 UTC by Julien HENRY
Modified: 2018-05-29 11:53 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-05-29 11:53:20 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Julien HENRY 2017-08-01 07:43:14 UTC
Hi,

Since I migrated to Fedora 26, Gnome Keyring is no more unlocked when starting my session. I don't see any related log in `journalctl`.

Manually opening `seahorse` and unlocking the "vault" works.

I noticed in seahorse that there are 2 password "vaults": "Connection" and "default". All my passwords are in the "default" one (and it is really marked as the default one). I don't remember if it was the case previously to have the "Connection" one. The tooltip on "Connection" says "A wallet that is automatically unlocked at login time". But this one is also not unlocked anyway.


Version-Release number of selected component (if applicable):
SDDM 0.14.0.10.fc26

How reproducible:
This seems to be 100% reproducible. 

Steps to Reproduce:
1. Start computer
2. Login in SDDM
3. Open `seahorse`

Actual results:
no "vault" unlocked

Expected results:
default vault unlocked

Additional info:
There is this bug report that seems related: https://bugzilla.redhat.com/show_bug.cgi?id=1467734

Comment 2 Fedora End Of Life 2018-05-03 08:28:49 UTC
This message is a reminder that Fedora 26 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 26. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '26'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 26 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Comment 3 Fedora End Of Life 2018-05-29 11:53:20 UTC
Fedora 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26
is no longer maintained, which means that it will not receive any
further security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.