Bug 1397086 - seahorse: cannot unlock my keyring
Summary: seahorse: cannot unlock my keyring
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: seahorse
Version: 25
Hardware: x86_64
OS: Linux
unspecified
urgent
Target Milestone: ---
Assignee: Matthias Clasen
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-11-21 14:53 UTC by Yaniv Kaul
Modified: 2017-12-12 10:28 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-12-12 10:28:33 UTC
Type: Bug


Attachments (Terms of Use)

Description Yaniv Kaul 2016-11-21 14:53:56 UTC
Description of problem:
I'm pretty sure I did not have this issue in the past, until I upgraded to Fedora 25. Now, I cannot unlock my keyring. I'm seeing multiple errors:
נוב 21 16:50:34 ykaul.tlv.redhat.com gnome-shell[2490]: remove_mnemonics: assertion 'label != NULL' failed
נוב 21 16:50:29 ykaul.tlv.redhat.com chronyd[1014]: Source 2001:418:3ff::53 replaced with 2400:8500:1301:1051:157:7:153:56
נוב 21 16:50:27 ykaul.tlv.redhat.com audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=sysstat-collect comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
נוב 21 16:50:27 ykaul.tlv.redhat.com audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=sysstat-collect comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
נוב 21 16:50:27 ykaul.tlv.redhat.com systemd[1]: Started system activity accounting tool.
נוב 21 16:50:27 ykaul.tlv.redhat.com systemd[1]: Starting system activity accounting tool...
נוב 21 16:49:47 ykaul.tlv.redhat.com org.gnome.seahorse.Application[2397]: Created new window in existing browser session.
נוב 21 16:49:35 ykaul.tlv.redhat.com seahorse[7032]: (gtkicontheme.c:2226):gtk_icon_theme_choose_icon_for_scale: runtime check failed: ((flags & GTK_ICON_LOOKUP_GENERIC_FALLBACK) == 0)
נוב 21 16:49:35 ykaul.tlv.redhat.com seahorse[7032]: (gtkicontheme.c:5493):gtk_icon_theme_lookup_by_gicon_for_scale: runtime check failed: ((flags & GTK_ICON_LOOKUP_GENERIC_FALLBACK) == 0)
נוב 21 16:49:35 ykaul.tlv.redhat.com seahorse[7032]: (gtkicontheme.c:2226):gtk_icon_theme_choose_icon_for_scale: runtime check failed: ((flags & GTK_ICON_LOOKUP_GENERIC_FALLBACK) == 0)
נוב 21 16:49:35 ykaul.tlv.redhat.com seahorse[7032]: (gtkicontheme.c:5493):gtk_icon_theme_lookup_by_gicon_for_scale: runtime check failed: ((flags & GTK_ICON_LOOKUP_GENERIC_FALLBACK) == 0)
נוב 21 16:49:34 ykaul.tlv.redhat.com seahorse[7032]: catalog.vala:193: couldn't add ui defintion for action group: KeyringBackend: "<ui>
                                                                                <popup name='SeahorseGkrBackend'>
                                                                                        <menuitem action='keyring-new'/>
                                                                                </popup>
                                                                        </ui>



Version-Release number of selected component (if applicable):
[ykaul@ykaul ~]$ rpm -qa |grep seahorse
seahorse-3.20.0-1.fc25.x86_64
[ykaul@ykaul ~]$ rpm -qa |grep keyring
gnome-keyring-pam-3.20.0-1.fc25.x86_64
libgnome-keyring-3.12.0-7.fc25.x86_64
gnome-keyring-3.20.0-1.fc25.x86_64

Comment 1 Christian Klomp 2017-01-10 19:48:46 UTC
I had the same problem after upgrading. In my case it seemed to be related to autologin (which for some reason always starts the Wayland session, not sure if that is also related). It just kept saying the password is incorrect unless I disabled autologin. Obviously all keys stored in the login keyring were unavailable which made GOA quirky.

It now works again after disabling autologin, a manual login after reboot, unlocking the keyring, then re-enabling autologin. I also manually removed and recreated the login keyring (via seahorse) but I don't think that matters because afterwards it happened again.

Comment 2 Christian Klomp 2017-01-10 21:38:47 UTC
Nope, the problem came back after a while and I am not able to unlock it any more. The annoying prompt pops up a lot less though when all gnome online accounts are deleted.

Comment 3 Christian Klomp 2017-01-12 13:44:11 UTC
I looked at it a bit more closely and I don't think the error messages are significant.
In my case https://bugzilla.redhat.com/show_bug.cgi?id=1406509 provides a good explanation of what might cause it.

Comment 4 Fedora End Of Life 2017-11-16 19:28:03 UTC
This message is a reminder that Fedora 25 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 25. 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 '25'.

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 25 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 5 Fedora End Of Life 2017-12-12 10:28:33 UTC
Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 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.