seahorse takes forever to start up because it's checking signatures for all keys in the gpg keyring

Bug #876813 reported by Steve Langasek
26
This bug affects 5 people
Affects Status Importance Assigned to Milestone
seahorse
Fix Released
Medium
seahorse (Ubuntu)
Fix Released
High
Ken VanDine
Oneiric
Fix Released
High
Unassigned
Precise
Fix Released
High
Ken VanDine

Bug Description

When I try to launch seahorse from the commandline, it takes forever to run because it's trying to check signatures on each key in my public keyring one by one using commands like this:

vorlon 25930 24.0 0.0 30892 2024 pts/2 RL 12:55 0:00 gpg --use-agent --batch --no-sk-comment --lc-messages en_US.UTF-8 --lc-ctype en_US.UTF-8 --status-fd 21 --no-tty --charset utf8 --enable-progress-filter --display :0 --ttyname /dev/pts/2 --ttytype xterm --with-colons --fixed-list-mode --with-fingerprint --with-fingerprint --check-sigs -- 85B99075C2910E41

This is a completely unacceptable regression that makes seahorse unusable for what I actually *want* to use it for. I have over 1500 public keys in my local gpg keyring, and I don't need seahorse's help with any of them, thankyouverymuch. What I need is a tool that can be used to manage *secret* keys; both the in-memory cache of gpg keys, as well as network passwords and the like. seahorse can no longer be used for this because of its unreasonable start-time checks.

ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: seahorse 3.2.0-0ubuntu1
ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
Uname: Linux 3.0.0-12-generic x86_64
ApportVersion: 1.23-0ubuntu3
Architecture: amd64
Date: Mon Oct 17 12:54:22 2011
InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100816.1)
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: seahorse
UpgradeStatus: Upgraded to oneiric on 2011-09-23 (23 days ago)

Revision history for this message
Steve Langasek (vorlon) wrote :
Changed in seahorse (Ubuntu):
status: New → Triaged
importance: Undecided → High
assignee: nobody → Ubuntu Desktop (ubuntu-desktop)
tags: added: regression-release
Revision history for this message
Steve Langasek (vorlon) wrote :

The timing of this behavior change in oneiric makes me suspect an upstream regression sometime between 3.1.91 and 3.2.0.

Revision history for this message
Sebastien Bacher (seb128) wrote :

The git logs (http://git.gnome.org/browse/seahorse/log/) don't show lot of code changes since 3.1.91, nothing that seems really suspicious...

Changed in seahorse (Ubuntu Oneiric):
importance: Undecided → High
Changed in seahorse (Ubuntu Precise):
assignee: Ubuntu Desktop (ubuntu-desktop) → Canonical Desktop Team (canonical-desktop-team)
Revision history for this message
Sebastien Bacher (seb128) wrote :

it's a duplicate of bug #874949 but since the new one has been triaged and the other one didn't have extra infos let's duplicate it the other way around rather

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in seahorse (Ubuntu Oneiric):
status: New → Confirmed
Revision history for this message
Benjamin Halbrock (kontakt-bennis-blog) wrote :

On bug #874949 i was told to report it upstream - would be great if one of you could do it :)

Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thank you for your bug report. This bug has been reported to the developers of the software. You can track it and make comments at:
https://bugzilla.gnome.org/show_bug.cgi?id=662088

Changed in seahorse (Ubuntu Oneiric):
status: Confirmed → Triaged
Changed in seahorse:
importance: Undecided → Unknown
status: New → Unknown
Changed in seahorse:
importance: Unknown → Medium
status: Unknown → New
Revision history for this message
Pedro Villavicencio (pedro) wrote :

A fix was commited to http://git.gnome.org/browse/seahorse/commit/?id=0cb0d5abe4af9160bafe753296ff1dca46e54866 ; But upstream has another questions, could somebody check and comment here or in the upstream report? Question:
"Please provide information for at what point the above command line is being
executed. It doesn't seem the sort of command line listed on start up."

Thanks all.

Changed in seahorse:
status: New → Incomplete
Revision history for this message
Steve Langasek (vorlon) wrote :

Information provided in the upstream report.

If the referenced change is specific to gnupg2, then it doesn't look related to the problem.

Revision history for this message
Sebastien Bacher (seb128) wrote :
Changed in seahorse (Ubuntu Precise):
assignee: Canonical Desktop Team (canonical-desktop-team) → Ken VanDine (ken-vandine)
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package seahorse - 3.2.2-0ubuntu1

---------------
seahorse (3.2.2-0ubuntu1) precise; urgency=low

  * New upstream release.
    * Don't load PGP signatures unless showing key properties (LP: #876813)
    * Fix crash, issues adding key servers
 -- Ken VanDine <email address hidden> Mon, 14 Nov 2011 11:29:30 -0500

Changed in seahorse (Ubuntu Precise):
status: Triaged → Fix Released
Revision history for this message
Chris Halse Rogers (raof) wrote :

There's some Uploaders: churn in debian/control that doesn't need to be there, but that's ok.

Changed in seahorse (Ubuntu Oneiric):
status: Triaged → Fix Committed
tags: added: verification-needed
Revision history for this message
Chris Halse Rogers (raof) wrote : Please test proposed package

Hello Steve, or anyone else affected,

Accepted seahorse into oneiric-proposed, the package will build now and be available in a few hours. Please test and give feedback here. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you in advance!

Revision history for this message
Benjamin Halbrock (kontakt-bennis-blog) wrote :

The proposed seahorse-package fixed this bug for me.

Martin Pitt (pitti)
tags: added: verification-done
removed: verification-needed
Revision history for this message
Steve Langasek (vorlon) wrote :

I can also confirm that seahorse 3.2.2 fixes this, both in oneiric-proposed and in precise.

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package seahorse - 3.2.2-0ubuntu0.1

---------------
seahorse (3.2.2-0ubuntu0.1) oneiric-proposed; urgency=low

  * New upstream release.
    * Don't load PGP signatures unless showing key properties (LP: #876813)
    * Fix crash, issues adding key servers
 -- Ken VanDine <email address hidden> Mon, 14 Nov 2011 11:44:04 -0500

Changed in seahorse (Ubuntu Oneiric):
status: Fix Committed → Fix Released
Changed in seahorse:
status: Incomplete → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.