Bug 170286 - kmail checks selected keys forever
Summary: kmail checks selected keys forever
Status: RESOLVED DUPLICATE of bug 169563
Alias: None
Product: kmail
Classification: Unmaintained
Component: encryption (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-09-03 01:44 UTC by S. Burmeister
Modified: 2008-12-09 17:10 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description S. Burmeister 2008-09-03 01:44:01 UTC 
Version:            (using KDE 4.1.0)
OS:                Linux
Installed from:    SuSE RPMs

If I want to set the key for encrypting/signing in the identity settings kmail shows a small window "Retrieving keys" and another "checking slected keys". those windows never disappear.
Comment 1 kde 2008-11-23 20:42:37 UTC 
I encountered the same problem with 4.1.3 on Kubuntu Intrepid.

The following status messages are printed when the retrieving/checking begins:

kmail(14157) Kleo::ProgressBar::fixup: Kleo::ProgressBar::startStopBusyTimer() cur = -1 ; tot = 100 ; real = -1
kmail(14157) Kleo::ProgressBar::fixup: (new value) switch to reset
kmail(14157) Kleo::_detail::ThreadedJobMixin<T_base, T_result>::slotFinished:
kmail(14157) Kleo::_detail::ThreadedJobMixin<T_base, T_result>::doEmitResult:
kmail(14157) Kleo::_detail::ThreadedJobMixin<T_base, T_result>::slotFinished: end
kmail(14157) Kleo::ProgressBar::fixup: Kleo::ProgressBar::startStopBusyTimer() cur = -1 ; tot = 100 ; real = -1
kmail(14157) Kleo::ProgressBar::fixup: (new value) switch to reset
kmail(14157) Kleo::_detail::ThreadedJobMixin<T_base, T_result>::slotFinished:
kmail(14157) Kleo::_detail::ThreadedJobMixin<T_base, T_result>::doEmitResult:
kmail(14157) Kleo::_detail::ThreadedJobMixin<T_base, T_result>::slotFinished: end
Comment 2 kde 2008-11-23 21:15:07 UTC 
Likely a duplicate of bug 169563.
Comment 3 Will Stephenson 2008-12-09 17:10:39 UTC 
Well spotted

*** This bug has been marked as a duplicate of bug 169563 ***