Bug#404228: marked as done (kmail's handling of passwords/kdewallet very broken)
Your message dated Mon, 06 Apr 2009 09:28:27 + with message-id e1lql7z-0001hq...@ries.debian.org and subject line Bug#404228: fixed in kdepim 4:4.2.2-1 has caused the Debian Bug report #404228, regarding kmail's handling of passwords/kdewallet very broken 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 this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 404228: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=404228 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: kmail Version: 3.5.5.dfsg.1-2 Kmail's handling of account passwords has a seriously annoying bug. If under account settings you tell kmail to store a POP password, then at some point you answered yes to the dialog box asking to store passwords in kwallet, then later decide you don't want to do that (it is extremely annoying and pops up continuously asking for the password - this is a massive annoyance not a convenience), you will repeatedly get the prompt to open kwallet. There's no way to get rid of it. If you say no to this dialog, you will get another dialog asking if it wants to store the password locally. If you say yes to this (and yes to the warning) you would think that it would do what you want and store the password and get on with it. But no, the very next time you run kmail you must go through this dialog process again - as though it just ignored what you told it to do the last time. Basically at this point I want to never use kdewallet, but it seems as though once kmail becomes tainted by using it even once, you can never get rid of it. ---End Message--- ---BeginMessage--- Source: kdepim Source-Version: 4:4.2.2-1 We believe that the bug you reported is fixed in the latest version of kdepim, which is due to be installed in the Debian FTP archive: akonadi-kde_4.2.2-1_amd64.deb to pool/main/k/kdepim/akonadi-kde_4.2.2-1_amd64.deb akonadi-kde_4.2.2-1_i386.deb to pool/main/k/kdepim/akonadi-kde_4.2.2-1_i386.deb akregator_4.2.2-1_amd64.deb to pool/main/k/kdepim/akregator_4.2.2-1_amd64.deb akregator_4.2.2-1_i386.deb to pool/main/k/kdepim/akregator_4.2.2-1_i386.deb kaddressbook_4.2.2-1_amd64.deb to pool/main/k/kdepim/kaddressbook_4.2.2-1_amd64.deb kaddressbook_4.2.2-1_i386.deb to pool/main/k/kdepim/kaddressbook_4.2.2-1_i386.deb kalarm_4.2.2-1_amd64.deb to pool/main/k/kdepim/kalarm_4.2.2-1_amd64.deb kalarm_4.2.2-1_i386.deb to pool/main/k/kdepim/kalarm_4.2.2-1_i386.deb kdepim-dbg_4.2.2-1_amd64.deb to pool/main/k/kdepim/kdepim-dbg_4.2.2-1_amd64.deb kdepim-dbg_4.2.2-1_i386.deb to pool/main/k/kdepim/kdepim-dbg_4.2.2-1_i386.deb kdepim-doc_4.2.2-1_all.deb to pool/main/k/kdepim/kdepim-doc_4.2.2-1_all.deb kdepim-groupware_4.2.2-1_amd64.deb to pool/main/k/kdepim/kdepim-groupware_4.2.2-1_amd64.deb kdepim-groupware_4.2.2-1_i386.deb to pool/main/k/kdepim/kdepim-groupware_4.2.2-1_i386.deb kdepim-kresources_4.2.2-1_amd64.deb to pool/main/k/kdepim/kdepim-kresources_4.2.2-1_amd64.deb kdepim-kresources_4.2.2-1_i386.deb to pool/main/k/kdepim/kdepim-kresources_4.2.2-1_i386.deb kdepim-strigi-plugins_4.2.2-1_amd64.deb to pool/main/k/kdepim/kdepim-strigi-plugins_4.2.2-1_amd64.deb kdepim-strigi-plugins_4.2.2-1_i386.deb to pool/main/k/kdepim/kdepim-strigi-plugins_4.2.2-1_i386.deb kdepim-wizards_4.2.2-1_amd64.deb to pool/main/k/kdepim/kdepim-wizards_4.2.2-1_amd64.deb kdepim-wizards_4.2.2-1_i386.deb to pool/main/k/kdepim/kdepim-wizards_4.2.2-1_i386.deb kdepim_4.2.2-1.diff.gz to pool/main/k/kdepim/kdepim_4.2.2-1.diff.gz kdepim_4.2.2-1.dsc to pool/main/k/kdepim/kdepim_4.2.2-1.dsc kdepim_4.2.2-1_all.deb to pool/main/k/kdepim/kdepim_4.2.2-1_all.deb kdepim_4.2.2.orig.tar.gz to pool/main/k/kdepim/kdepim_4.2.2.orig.tar.gz kjots_4.2.2-1_amd64.deb to pool/main/k/kdepim/kjots_4.2.2-1_amd64.deb kjots_4.2.2-1_i386.deb to pool/main/k/kdepim/kjots_4.2.2-1_i386.deb kleopatra_4.2.2-1_amd64.deb to pool/main/k/kdepim/kleopatra_4.2.2-1_amd64.deb kleopatra_4.2.2-1_i386.deb to pool/main/k/kdepim/kleopatra_4.2.2-1_i386.deb kmail_4.2.2-1_amd64.deb to pool/main/k/kdepim/kmail_4.2.2-1_amd64.deb kmail_4.2.2-1_i386.deb to pool/main/k/kdepim/kmail_4.2.2-1_i386.deb knode_4.2.2-1_amd64.deb to pool/main/k/kdepim/knode_4.2.2-1_amd64.deb knode_4.2.2-1_i386.deb to pool/main/k/kdepim/knode_4.2.2-1_i386.deb knotes_4.2.2-1_amd64.deb to pool/main/k/kdepim/knotes_4.2.2-1_amd64.deb knotes_4.2.2-1_i386.deb to pool/main/k/kdepim/knotes_4.2.2-1_i386.deb kode_4.2.2-1_amd64.deb to pool/main/k/kdepim/kode_4.2.2-1_amd64.deb kode_4.2.2-1_i386.deb to pool/main/k/kdepim/kode_4.2.2-1_i386.deb konsolekalendar_4.2.2-1_amd64.deb to
Bug#404228: marked as done (kmail's handling of passwords/kdewallet very broken)
Your message dated Thu, 17 Apr 2008 16:34:07 +0530
with message-id [EMAIL PROTECTED]
and subject line Done: kmail's handling of passwords/kdewallet very broken
has caused the Debian Bug report #404228,
regarding kmail's handling of passwords/kdewallet very broken
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)
--
404228: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=404228
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
---BeginMessage---
Package: kmail
Version: 3.5.5.dfsg.1-2
Kmail's handling of account passwords has a seriously annoying bug. If
under account settings you tell kmail to store a POP password, then at
some point you answered yes to the dialog box asking to store passwords
in kwallet, then later decide you don't want to do that (it is extremely
annoying and pops up continuously asking for the password - this is a
massive annoyance not a convenience), you will repeatedly get the prompt
to open kwallet. There's no way to get rid of it. If you say no to
this dialog, you will get another dialog asking if it wants to store the
password locally. If you say yes to this (and yes to the warning) you
would think that it would do what you want and store the password and
get on with it. But no, the very next time you run kmail you must go
through this dialog process again - as though it just ignored what you
told it to do the last time.
Basically at this point I want to never use kdewallet, but it seems as
though once kmail becomes tainted by using it even once, you can never
get rid of it.
---End Message---
---BeginMessage---
Package: kmail
Version: 4:3.5.9-2
--- Please enter the report below this line. ---
Fixed-upstream.
See: https://bugs.kde.org/show_bug.cgi?id=95615
and KDE SVN commit 675974
--
Cheers,
Kartik Mistry | 0xD1028C8D | IRC: kart_
Blogs: {ftbfs,kartikm}.wordpress.com
It'll be a nice world if they ever get it finished.
---End Message---
