We noticed during tests triggered by a user question regarding difficulties to restore a key, that Kleopatra gives an unhelpful error message "Failed to restore any secret keys." in the case of

a) trying to import a printed backup of a key were the secret key is already in the keyring and
b) trying to import the printed backup of another key (i.e. the wrong import file was selected).

a) could be addressed by greying out the action "Restore printed backup" in case the secret key is there

What can we do in case of b?
Paperkey on the cli does not give an error message in that case.
Therefore I guess the best possible (and easiest) solution would be to add more info to the default error message.
Maybe "Did you choose the right import file? Check the fingerprint in the first (commented) line."
(The person seeking advice did delete the commented lines, thinking they might interfere.)

If we want to go over the top, we could maybe display the import file and check for the fingerprint and/or format errors (e.g. missing whitespaces)…