Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
Seahorse
Seahorse
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 192
    • Issues 192
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 5
    • Merge Requests 5
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • GNOME
  • SeahorseSeahorse
  • Issues
  • #160

Closed
Open
Opened May 14, 2017 by bugzilla-migration@bugzilla-migrationReporter

First attempt to sign a key fails with General Error

Submitted by Kjo Hansi Glaz

Link to original bug (#782612)

Description

When I open seahorse, I select a key and I try to sign that key, then I get a "General Error" the first time. When I try again to sign the same key then everything goes fine.

Seahorse version is 3.20.0-3.1 (that is upstream seahorse 3.20.0 with cdfc5b29 applied)

Seahorse output:

(seahorse:10389): seahorse-CRITICAL **: file pgp/seahorse-gpgme-key-op.c: line 551 (sign_transit): should not be reached

I think that a part of the fix for the new status line KEY_CONSIDERED introduced in gpg 2.1.13 is still missing.

Version: 3.20.x

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: GNOME/seahorse#160