ugly error when failed to sign because of wrong password

Bug #1631407 reported by Leo Arias
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Snapcraft
New
Undecided
Unassigned
snapd
Triaged
Low
Unassigned

Bug Description

If I try to sign a snap, but fail the password three times, I get back this error:

error: cannot sign assertion: cannot sign assertion: cannot sign using GPG: /usr/bin/gpg --personal-digest-preferences SHA512 --default-key 0x993DD0E6F134F4FC5EC9498E212D9EBF5179F05F --detach-sign failed: exit status 2 ("gpg: Invalid passphrase; please try again ...\ngpg: Invalid passphrase; please try again ...\ngpg: no default secret key: bad passphrase\ngpg: signing failed: bad passphrase\n")
Failed to sign build assertion for u1test20161006_0.1_all.snap.

To reproduce: snapcraft sign-build test.snap, and enter the wrong password three times.

Tags: store
Leo Arias (elopio)
tags: added: store
Michael Vogt (mvo)
Changed in snappy:
status: New → Triaged
importance: Undecided → Medium
importance: Medium → Low
Michael Vogt (mvo)
affects: snappy → snapd
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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