(*** This bug was imported into bugs.kde.org ***) Package: kmail Version: 1.2 (using KDE 2.1.0 ) Severity: normal Installed from: SuSE Compiler: Not Specified OS: Linux 2.2.14 i686 OS/Compiler notes: Not Specified My kmail hung/was deadlocked when i tried to test the encryption support in kmail my pgp ver is 2.6.3i I did the following: composed an empty message said kmail to encrypt & sign it. sent it! and kmail went busy and never returned and did not complain it turned out that pgp needed a new random seed as it never had been used for encryption on this host before. IF i get the command line from executing 'ps axfwww' and remove +BATCHMODE i can see that after suppling the text and passphrase pgp wanted another input the random keystrokes. so i think it is a deadlock because kmail fails to supply that keystrokes and does wait indefinitly for pgp to complete. so Kmail shall try to detect if external programms do not behave like it expects them to an give the user useful feedback on that simply deadlocking is not an option!! Deadlock: two syncronized processes waiting indefinitly for eachother to complete (Submitted via bugs.kde.org) (Called from KBugReport dialog. Fields Compiler manually changed)
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi thanks for your bug report and my humble apologies for replying so late. On Saturday 31. March 2001 14:56 MIC.Hostettler@t-online.de wrote: > Package: kmail > Version: 1.2 (using KDE 2.1.0 ) > Severity: normal > Installed from: SuSE > Compiler: Not Specified > OS: Linux 2.2.14 i686 > OS/Compiler notes: Not Specified > > My kmail hung/was deadlocked > when i tried to test the encryption support in kmail > my pgp ver is 2.6.3i > I did the following: > composed an empty message > said kmail to encrypt & sign it. > sent it! > and kmail went busy and never returned and did not complain > > it turned out that pgp needed a new random seed as it never had been > used for encryption on this host before. > > IF i get the command line from executing 'ps axfwww' and remove > +BATCHMODE i can see that after suppling the text and passphrase pgp > wanted another input the random keystrokes. > > so i think it is a deadlock because kmail fails to supply that > keystrokes and does wait indefinitly for pgp to complete. > > so > Kmail shall try to detect if external programms do not behave like it > expects them to an give the user useful feedback on that simply > deadlocking is not an option!! > > > Deadlock: two syncronized processes waiting indefinitly for eachother > to complete IMHO it's pgp's fault. In batch mode it's obviously not possible to provide random keystrokes. Therefore pgp should have exited with an error message. Nonetheless deadlocking should really be avoided. Regards Ingo -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE7K8vpGnR+RTDgudgRAtjsAJ4225W0FUpPkoaMBvE7xm/CNH/E9wCeLcYa Na3l7thEPBVx1MH4V8JA590= =/mQd -----END PGP SIGNATURE-----
Reporter: Do you still experience this?
Thank you for your feature request. Kmail1 is currently unmaintained so we are closing all wishes. Please feel free to reopen a feature request for Kmail2 if it has not already been implemented. Thank you for your understanding.
Instead of creating a new feature request, please confirm here if the wishlist is still valid for kmail2.