[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#143478: marked as done (kmail: kmail locks under heavy gpg key batching then duplicates emails on next pop check.)

Your message dated Fri, 21 Apr 2006 15:03:32 +0200
with message-id <200604211503.53103.debian@pusling.com>
and subject line kmail: kmail locks under heavy gpg key batching then duplicates emails on next pop check
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message --- 
Package: kmail
Version: 4:2.2.2-14
Severity: grave
Justification: causes non-serious data loss


Open kmail and do a pop3 run on your mailbox. Now, with either a digest 
form or other multiply embedded gpg signature carrying email, attempt to 
highlight that email. kmail will go directly to GPG batch mode for decryption, 
then lock up it's entire interface. In these instances it would cause total
and complete lack of response to any keyboard or mouse interactions also causing
it to fail to refresh itself on the screen. Next, you will have to use either 
ksysguard or other means to kill it. Upon the next pop3 run, after
restarting kmail, kmail will have duplicated mails for every email it
grabbed during the last run, OR **IMPORTANT**  OR it _deletes_ them!!

I am using UIDLs. I do not know if this is because kmail is not updating the 
UIDL list before attempting batch key decryptions or if it's doing so but failing to
compare the UIDL list with the mail server on the next run because it
thinks those emails were previously saved or, in the case of the
deletions, it thinks they were marked for deletion and therefore informs
the mail server to delete them there as well. It's a little confusing as
to which one it's doing since it flip flops. But it is consistent in the
treatment if not the manner in which it treats them. (AKA I may not know that if
I do the above steps repeatedly whether I'll be either out of mail or have dupes
and triplicates of all my mail, but I know it'll screw up in either of
the two ways.)

Because of the data loss (emails) either through kmail deleting it, or
me because I'm unsure of which ones are the original emails, (it also
likes to jumble the threads when it does this as well) I have marked
this as grave.


-- System Information
Debian Release: 3.0
Architecture: i386
Kernel: Linux elendryl.codecastle.com 2.4.18-bf2.4-xfs-prmpt #2 Tue Apr 16 16:02:15 PDT 2002 i686
Locale: LANG=en_US.ISO-8859-1, LC_CTYPE=en_US.ISO-8859-1

Versions of packages kmail depends on:
ii  kdelibs3                      4:2.2.2-13 KDE core libraries (runtime files)
ii  libc6                         2.2.5-4    GNU C Library: Shared libraries an
ii  libfam0                       2.6.6.1-4  client library to control the FAM 
ii  libjpeg62                     6b-5       The Independent JPEG Group's JPEG 
ii  libkdenetwork1                4:2.2.2-14 Common libraries needed for KDE ne
ii  libmimelib1                   4:2.2.2-14 mime libraries needed for some KDE
ii  libpng2                       1.0.12-3   PNG library - runtime
ii  libqt2                        3:2.3.1-22 Qt GUI Library (runtime version).
ii  libstdc++2.10-glibc2.2        1:2.95.4-7 The GNU stdc++ library
ii  procmail                      3.22-4     Versatile e-mail processor.
ii  xlibs                         4.1.0-16   X Window System client libraries
ii  zlib1g                        1:1.1.4-1  compression library - runtime

--- End Message ---
--- Begin Message --- 
This bug have been tagged moreinfo for several years without any action other 
than a message that all this part of kgpg/kmail have been rewritten, and this 
problem probably not exist anymore.

Closing this bug.

/Sune

Attachment: pgpIr3dr5haZr.pgp
Description: PGP signature


--- End Message ---
Reply to: