Bug 332508 - kmail2 is no more able to use any of the gpg key
Summary: kmail2 is no more able to use any of the gpg key
Status: RESOLVED FIXED
Alias: None
Product: kmail2
Classification: Applications
Component: crypto (show other bugs)
Version: 4.13 Pre
Platform: openSUSE Linux
: NOR major
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-03-24 14:18 UTC by Bruno Friedmann
Modified: 2014-03-25 09:16 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Bruno Friedmann 2014-03-24 14:18:31 UTC
Since the beta3, I'm no more able to sign or encrypt a message in kmail2 (even if nothing has changed between beta2 and beta3)


Reproducible: Always

Steps to Reproduce:
1. Setup your identity and crypto prefs with your own key
2. Try to write an email to yourself 
3. click sign & encrypt
4. Get error message
Actual Results:  
You have requested to sign this message, but no valid signing keys have been configured for this identity.

Expected Results:  
gpg selected and mail sended encrypted

Extract of .xsession-error ( kmail & co have been placed in debug mode )

akonadiserver(2855) SearchPlugin::search: no terms added 
akonadiserver(2855) SearchPlugin::search: no terms added 
QAbstractSocket::waitForBytesWritten() is not allowed in UnconnectedState
QAbstractSocket::waitForBytesWritten() is not allowed in UnconnectedState
QAbstractSocket::waitForBytesWritten() is not allowed in UnconnectedState
QAbstractSocket::waitForBytesWritten() is not allowed in UnconnectedState
QAbstractSocket::waitForBytesWritten() is not allowed in UnconnectedState
QAbstractSocket::waitForBytesWritten() is not allowed in UnconnectedState
QAbstractSocket::waitForBytesWritten() is not allowed in UnconnectedState
QAbstractSocket::waitForBytesWritten() is not allowed in UnconnectedState
QAbstractSocket::waitForBytesWritten() is not allowed in UnconnectedState
QAbstractSocket::waitForBytesWritten() is not allowed in UnconnectedState
QAbstractSocket::waitForBytesWritten() is not allowed in UnconnectedState
QAbstractSocket::waitForBytesWritten() is not allowed in UnconnectedState
QAbstractSocket::waitForBytesWritten() is not allowed in UnconnectedState
QAbstractSocket::waitForBytesWritten() is not allowed in UnconnectedState
QAbstractSocket::waitForBytesWritten() is not allowed in UnconnectedState
QAbstractSocket::waitForBytesWritten() is not allowed in UnconnectedState
QAbstractSocket::waitForBytesWritten() is not allowed in UnconnectedState
QAbstractSocket::waitForBytesWritten() is not allowed in UnconnectedState
QAbstractSocket::waitForBytesWritten() is not allowed in UnconnectedState
QAbstractSocket::waitForBytesWritten() is not allowed in UnconnectedState
QAbstractSocket::waitForBytesWritten() is not allowed in UnconnectedState
QAbstractSocket::waitForBytesWritten() is not allowed in UnconnectedState
akonadiserver(2855) SearchPlugin::search: no terms added 
kmail2(25412) Sonnet::Highlighter::slotRehighlight: Highlighter::slotRehighlight()
kmail2(25412) Sonnet::Highlighter::slotRehighlight: Highlighter::slotRehighlight()
kmail2(25412) Sonnet::Highlighter::slotRehighlight: Highlighter::slotRehighlight()
libpng warning: iCCP: known incorrect sRGB profile
kmail2(25412) KMKernel::instanceStatusChanged: A Resource started to synchronize, starting a mail check.
kmail2(25412) CodecAction::mimeCharsets: current item 0 "Default"
kmail2(25412) MessageComposer::ComposerViewBase::send: Plain text
kmail2(25412) MessageComposer::ComposerViewBase::readyForSending: Entering readyForSending
kmail2(25412) MessageComposer::ComposerViewBase::generateCryptoMessages: filling crypto info
kmail2(25412) MessageComposer::ComposerViewBase::generateCryptoMessages: false true
kmail2(25412) Kleo::KeyResolver::lookup: ( " "7E289CA4C83EEE56050095F2D5C9B751C4653227" ", false )
kmail2(25412) Kleo::KeyResolver::lookup:  returned 0 keys
kmail2(25412) Kleo::KeyResolver::lookup: ( " "7E289CA4C83EEE56050095F2D5C9B751C4653227" ", true )
kmail2(25412) Kleo::KeyResolver::lookup:  returned 0 keys
kmail2(25412) KMKernel::slotProgressItemCompletedOrCanceled: Last resource finished syncing, mail check done
libpng warning: iCCP: known incorrect sRGB profile
kmail2(25412) CodecAction::mimeCharsets: current item 0 "Default"
kmail2(25412) MessageComposer::ComposerViewBase::autoSaveMessage: Autosaving message
kmail2(25412) MessageComposer::Util::selectCharset: Chosen charset "utf-8"
kmail2(25412) MessageComposer::MainTextJobPrivate::encodeTexts: Done.
kmail2(25412) MessageComposer::MainTextJob::doStart: Making text/plain
kmail2(25412) MessageComposer::ContentJobBasePrivate::doNextSubjob: Calling process.
kmail2(25412) MessageComposer::SinglepartJobPrivate::chooseCTE: Settled on encoding "quoted-printable"
kmail2(25412) MessageComposer::ContentJobBase::slotResult: A subjob finished. 0 more to go.
kmail2(25412) MessageComposer::ContentJobBasePrivate::doNextSubjob: Calling process.
kmail2(25412) MessageComposer::ComposerPrivate::contentJobFinished: composing final message
kmail2(25412) MessageComposer::ComposerViewBase::slotAutoSaveComposeResult: NoError.
kmail2(25412) MessageComposer::ComposerViewBase::writeAutoSaveToDisk: Writing message to disk as "/home/bruno/.kde4/share/apps/kmail2/autosave/{21c1efbd-8032-455c-9aed-be170f4d131d}"
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
kmail2(25412) KIO::DataProtocol::~DataProtocol:
libpng warning: iCCP: known incorrect sRGB profile
kmail2(25412) MessageComposer::ComposerViewBase::generateCryptoMessages: determineWhetherToSign: failed to resolve keys! oh noes
file:///usr/share/kde4/apps/plasma/plasmoids/org.kde.notifications/contents/ui/main.qml:139:9: QML Flickable: Possible anchor loop detected on fill.
file:///usr/share/kde4/apps/plasma/plasmoids/org.kde.notifications/contents/ui/main.qml:139:9: QML Flickable: Possible anchor loop detected on fill.
Comment 1 Bruno Friedmann 2014-03-25 09:16:17 UTC
Removing all openPGP/smime information on my main identity and setting them up again fixes the issue ?

Why it has failed or work after settings again the same value is unknown.