You are not logged in.

#1 2015-04-13 17:48:56

Gerd093
Member
Registered: 2015-03-06
Posts: 12

gnome 3.16 seahorse does not show gpg keys anymore

After upgrading to gnome 3.16 seahorse does not list any gpg keyys anymore.
Not only does it not list the specific keys, the complete gpg section is gone

Anyone else having this problem?

Offline

#2 2015-04-13 21:02:22

pauldcox
Member
Registered: 2011-08-19
Posts: 8

Re: gnome 3.16 seahorse does not show gpg keys anymore

Completely gone for me as well.

Offline

#3 2015-04-13 23:28:11

pezz
Member
From: Geelong, Australia
Registered: 2010-05-23
Posts: 53

Re: gnome 3.16 seahorse does not show gpg keys anymore

It's not unlocking my ssh keys either.

Offline

#4 2015-04-14 01:12:59

pezz
Member
From: Geelong, Australia
Registered: 2010-05-23
Posts: 53

Re: gnome 3.16 seahorse does not show gpg keys anymore

Found this in my journal, wonder if it's related?

Apr 14 09:35:29 mybox gnome-keyring-daemon[1462]: couldn't register in session: The name org.gnome.SessionManager was not provided by any .service files

Offline

#5 2015-04-14 04:18:00

bulletmark
Member
From: Brisbane, Australia
Registered: 2013-10-22
Posts: 441

Re: gnome 3.16 seahorse does not show gpg keys anymore

pezz wrote:

It's not unlocking my ssh keys either.

Pezz, I had this problem a couple of days ago (after the update to 3.16) and I found that my SSH_AUTH_SOCK variable was pointing to /tmp/ssh-xxxxxxx/agent.NNN. It should have been pointing to /run/user/1000/keyring/ssh. I then rebooted and have not seen the problem again, i.e. I have rebooted a few times since and SSH_AUTH_SOCK has always been correct. Maybe there is a bug/race condition which does this? Echo $SSH_AUTH_SOCK to check.

Offline

#6 2015-04-14 04:20:05

Scimmia
Bug Wrangler
Registered: 2012-09-01
Posts: 7,326

Re: gnome 3.16 seahorse does not show gpg keys anymore

Offline

#7 2015-04-14 07:23:04

pezz
Member
From: Geelong, Australia
Registered: 2010-05-23
Posts: 53

Re: gnome 3.16 seahorse does not show gpg keys anymore

Thanks bulletmark, I'll check tomorrow (it's my work machine with the problem).

I just updated my laptop to 3.16 at home and it's unlocking fine.

Offline

#8 2015-04-14 14:47:51

lazork
Member
Registered: 2008-11-12
Posts: 30

Re: gnome 3.16 seahorse does not show gpg keys anymore

bulletmark wrote:
pezz wrote:

It's not unlocking my ssh keys either.

Pezz, I had this problem a couple of days ago (after the update to 3.16) and I found that my SSH_AUTH_SOCK variable was pointing to /tmp/ssh-xxxxxxx/agent.NNN. It should have been pointing to /run/user/1000/keyring/ssh. I then rebooted and have not seen the problem again, i.e. I have rebooted a few times since and SSH_AUTH_SOCK has always been correct. Maybe there is a bug/race condition which does this? Echo $SSH_AUTH_SOCK to check.

I'm experiencing this exact issue, except the problem persists even after several reboots.
Here are some additional (possibly relevant) entries from journalctl:

Apr 14 16:31:23 arche /usr/lib/gdm/gdm-x-session[804]: /etc/gdm/Xsession: Setup done, will execute: /usr/bin/ssh-agent -- gnome-session
...
Apr 14 16:31:24 arche gnome-keyring-daemon[801]: couldn't register in session: The name org.gnome.SessionManager was not provided by any .service files
...
Apr 14 16:31:24 arche gnome-session[811]: SSH_AUTH_SOCK=/run/user/10011/keyring/ssh
Apr 14 16:31:24 arche gnome-session[811]: SSH_AUTH_SOCK=/run/user/10011/keyring/ssh
Apr 14 16:31:24 arche gnome-session[811]: SSH_AUTH_SOCK=/run/user/10011/keyring/ssh
Apr 14 16:31:24 arche gnome-session[811]: GPG_AGENT_INFO=/run/user/10011/keyring/gpg:0:1
Apr 14 16:31:24 arche gnome-session[811]: SSH_AUTH_SOCK=/run/user/10011/keyring/ssh
Apr 14 16:31:24 arche gnome-session[811]: GPG_AGENT_INFO=/run/user/10011/keyring/gpg:0:1

Echoing SSH_AUTH_SOCK always shows it equal to "/tmp/ssh-xxxxxxx/agent.NNN".
Has anyone got any idea of what might be going on?

Offline

#9 2015-04-15 06:03:13

blufinney
Member
Registered: 2014-08-26
Posts: 47

Re: gnome 3.16 seahorse does not show gpg keys anymore

bulletmark wrote:
pezz wrote:

It's not unlocking my ssh keys either.

Pezz, I had this problem a couple of days ago (after the update to 3.16) and I found that my SSH_AUTH_SOCK variable was pointing to /tmp/ssh-xxxxxxx/agent.NNN. It should have been pointing to /run/user/1000/keyring/ssh. I then rebooted and have not seen the problem again, i.e. I have rebooted a few times since and SSH_AUTH_SOCK has always been correct. Maybe there is a bug/race condition which does this? Echo $SSH_AUTH_SOCK to check.

I had the same issue at some point after upgrading to gnome 3.16, this fixed the issue for me - thanks!

Offline

#10 2015-04-15 10:53:30

bulletmark
Member
From: Brisbane, Australia
Registered: 2013-10-22
Posts: 441

Re: gnome 3.16 seahorse does not show gpg keys anymore

blufinney wrote:

I had the same issue at some point after upgrading to gnome 3.16, this fixed the issue for me - thanks!

That wasn't a suggested fix! That SSH_AUTH_SOCK variable is supposed to be set automatically for you at login. All I know is that since GNOME 3.16 it is randomly getting set to that /tmp/ssh-xxxx value sometimes. It happened to me again today. Of course you can temporarily fix it by exporting that variable to the correct value but we will have to wait for the GNOME guys to work out what is going wrong and fix it properly.

Offline

#11 2015-04-16 01:59:32

lmello
Member
From: Brazil
Registered: 2012-11-06
Posts: 300

Re: gnome 3.16 seahorse does not show gpg keys anymore

seahorse doesn't support gnupg 2.1 yet.

request upstream at https://bugzilla.gnome.org/show_bug.cgi?id=745843


Fundamental Axiom of the Universe (aka Murphy's Law): Whatever can go wrong, will go wrong.
First Digital Deduction: Nothing obeys Murphy's Law so well as computers.
Second Digital Deduction: Everything go wrong at least once.
Third Digital Deduction: Things go wrong even when there's absolutely no possibility of anything go wrong.

Offline

#12 2015-11-12 04:31:33

bulletmark
Member
From: Brisbane, Australia
Registered: 2013-10-22
Posts: 441

Re: gnome 3.16 seahorse does not show gpg keys anymore

This bug went away for about 3 months for me but has come back with a vengeance in the last 3 weeks or so. I'd say SSH_AUTH_SOCK is not set correctly about every 5th time I reboot.:(

Offline

#13 2015-12-16 21:27:33

trunneml
Member
From: Germany Stuttgart
Registered: 2010-02-09
Posts: 21

Re: gnome 3.16 seahorse does not show gpg keys anymore

Anything new here? On my PC it works on my laptop not?

On my Laptop also is this message (which is not on my PC):
The name org.gnome.SessionManager was not provided by any .service files

Any idea?

Offline

#14 2015-12-16 21:30:29

ijanos
Member
From: Budapest, Hungary
Registered: 2008-03-30
Posts: 443
Website

Re: gnome 3.16 seahorse does not show gpg keys anymore

Same thing happens to me

The bug appears on one laptop but does not on another.

Offline

#15 2015-12-16 21:44:21

trunneml
Member
From: Germany Stuttgart
Registered: 2010-02-09
Posts: 21

Re: gnome 3.16 seahorse does not show gpg keys anymore

May be it has something to do with networkmanager and wifi. Should be interessting to try it without the networkmanager installed. :-?

Offline

#16 2015-12-16 21:46:32

ijanos
Member
From: Budapest, Hungary
Registered: 2008-03-30
Posts: 443
Website

Re: gnome 3.16 seahorse does not show gpg keys anymore

I have identical installations on the two machines.

Offline

#17 2015-12-17 19:36:38

trunneml
Member
From: Germany Stuttgart
Registered: 2010-02-09
Posts: 21

Re: gnome 3.16 seahorse does not show gpg keys anymore

Found the problem: https://bugs.debian.org/cgi-bin/bugrepo … bug=804703

There is also a patch. I created a patch version of gnome-keyring. You can find the pkg and PKGBUILD here:

https://www.dropbox.com/sh/uudpqc61hs79 … -MYDa?dl=0

Hope it helps.

Offline

Board footer

Powered by FluxBB