Okular: No error on signature with wrong passphrase
Closed, ResolvedPublic

Assigned To
Authored By
timegrid
Jan 6 2026, 2:28 PM

Description

Found by testing T7285: Okular: Improvement of error messages regarding signatures

To reproduce:

  1. Kill gpg agent to make sure, there's no session open
  2. Open and save a (smime or pgp) signed pdf file
  3. Enter a wrong passphrase in pinentry 3 times ->
    • there's no error message
    • okular still shows "finish signing":
    • the file was written but has a broken signature:

Details

Version
gpg4win-5.0.0-beta479 @ win11

Event Timeline

timegrid created this object with edit policy "Contributor (Project)".
werner triaged this task as Normal priority.Jan 7 2026, 12:04 PM
werner added a project: Bug Report.
svuorela changed the task status from Open to Testing.Jan 13 2026, 2:36 PM

Fixed upstream with https://invent.kde.org/graphics/okular/-/merge_requests/1301 - not yet in our packaging

svuorela removed a project: test on hold.
timegrid claimed this task.

Looks not pretty, but good to me on gpg4win-5.1.0-beta653 @ win11:

Note:

  • The duplicated Bad passphrase feedback hidden behind the collapsed Details is not exactly user friendly. It would be better to hide the Details in cases, in which they are not helpful (I'll create another low/wishlist prio ticket for that)
timegrid edited projects, added gpd5x (gpd-5.1.0); removed gpd5x.

seems to me, that the details here are no details and could be dropped completely. I'm i overlooking something?
And wouldn't "Could not sign: Wrong passphrase" be better? Or even better: "Signature failed: Wrong passphrase"?
In Kleopatra we have: "Signing failed: %1"

In T8018#219988, @ebo wrote:

seems to me, that the details here are no details and could be dropped completely.

With "hide" i meant removing it, so i agree

In T8018#219988, @ebo wrote:

seems to me, that the details here are no details and could be dropped completely. I'm i overlooking something?
And wouldn't "Could not sign: Wrong passphrase" be better? Or even better: "Signature failed: Wrong passphrase"?
In Kleopatra we have: "Signing failed: %1"

the "Details" is the message we get out of gpg as the error. First part of the message is something we maybe better can control.

I guess we can special case the bad passphrase a bit further.