Bug 550190

Summary:	[gnome-overlay] app-crypt/seahorse-3.16.0/ gnome-keyring-3.16 have runtime issues
Product:	Gentoo Linux	Reporter:	Harris Landgarten <harrisl>
Component:	[OLD] GNOME	Assignee:	Gentoo Linux Gnome Desktop Team <gnome>
Status:	RESOLVED FIXED
Severity:	normal	CC:	esigra
Priority:	Normal
Version:	10.1
Hardware:	All
OS:	Linux
See Also:	https://bugzilla.gnome.org/show_bug.cgi?id=742094 https://bugs.gentoo.org/show_bug.cgi?id=547456
Whiteboard:
Package list:		Runtime testing required:	---
Bug Depends on:
Bug Blocks:	545082

Description Harris Landgarten 2015-05-22 20:00:05 UTC

I downgraded gnupg so I can install and test seahorse-3.16

I am seeing some very odd runtime issues.

First I have enabled autologin in gdm (not auto password) so it would run.

After logging in and running seahorse, I see my login keyring is uplocks as it should be. The default keyring is locked. If I try to manually unlock it nothing happens, no prompt for password. One time a tried to unlock it and my machine temporarily locked up and I was thrown to VT 1. I switched back to VT 7 and my gnome-session was still running. I have not run seahorse since.

I also noticed that the ssh agent in seahorse is not working. The default ssh-agent is. That is not necessarily bad as the gnome ssh-agent doesn't work with ellipical keys.

Anyway, there is something not right. Could be serious. Others should downgrade gnupg and give it a try.

Comment 1 Rafał Mużyło 2015-05-22 20:40:35 UTC

...most likely what you're seeing is a Gnome bug, not one on the side of gnupg.

IIRC, I've seen a discussion about it on desktop-devel Gnome list, though they've painted that a bit differently.

Comment 2 Harris Landgarten 2015-05-22 20:56:15 UTC

I have only seen these issue since I installed seahorse-3.16. I only downgraded gnupg to 2.0 series because seahorse requires it and from what I have read it really doesn't work properly with 2.1 gnupg.

Comment 3 Rafał Mużyło 2015-05-26 08:55:18 UTC

...for some reason, I can't find the discussion that has led me to the bug (which IIRC had quite a bit more info), but the bug itself is gnome #742094.

Comment 4 Pacho Ramos gentoo-dev

2015-06-20 09:15:06 UTC

I cannot reproduce this issues... can you retest with latest versions in the tree for gnome-keyring and seahorse?

Thanks

Comment 5 Harris Landgarten 2015-06-20 13:04:22 UTC

Ever since I got gdm working properly, gnome-keyring has been working as expected. I cannot reproduce any of the oddities I found before.

Comment 6 Pacho Ramos gentoo-dev

2015-06-20 13:13:37 UTC

Thanks a lot for feedback