Bug#294169: kmail should handle disconnection gracefully
Package: kmail
Version: 4:3.3.2-1
Severity: normal
Hi!
When I start kmail (or kontact) when there is no network connection
(on my notebook, I start them on demand depending on where I am),
it tries to connect to my configured IMAP servers and displays
error messages for each that the server could not be reached.
after this, I have to exit kmail (or kontact) and manually kill
every kio_newimap(s) process and restart kmail, If I am lucky,
I can get a connection.
Please add a little "terminate all IMAP/whatever connection" to
kmail, maybe in the status bar where the "cancel operation" button
is. Or am I overlooking something?
Thanks
Martin Emrich
-- System Information:
Debian Release: 3.1
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.9
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to de_DE.UTF-8)
Versions of packages kmail depends on:
ii kdelibs4 4:3.3.2-1 KDE core libraries
ii libc6 2.3.2.ds1-20 GNU C Library: Shared libraries an
ii libgcc1 1:3.4.3-7 GCC support library
ii libice6 4.3.0.dfsg.1-10 Inter-Client Exchange library
ii libkcal2a 4:3.3.2-1 KDE calendaring library
ii libkdenetwork2 4:3.3.2-1 KDE Network library
ii libkdepim1 4:3.3.2-1 KDE PIM library
ii libkleopatra0a 4:3.3.2-1 KDE GnuPG interface libraries
ii libkpimidentities1 4:3.3.2-1 KDE PIM user identity information
ii libksieve0 4:3.3.2-1 KDE mail/news message filtering li
ii libmimelib1a 4:3.3.2-1 KDE mime library
ii libpng12-0 1.2.8rel-1 PNG library - runtime
ii libqt3c102-mt 3:3.3.3-8 Qt GUI Library (Threaded runtime v
ii libsm6 4.3.0.dfsg.1-10 X Window System Session Management
ii libstdc++5 1:3.3.5-8 The GNU Standard C++ Library v3
ii libx11-6 4.3.0.dfsg.1-10 X Window System protocol client li
ii libxext6 4.3.0.dfsg.1-10 X Window System miscellaneous exte
ii perl 5.8.4-6 Larry Wall's Practical Extraction
ii xlibs 4.3.0.dfsg.1-10 X Keyboard Extension (XKB) configu
ii zlib1g 1:1.2.2-4 compression library - runtime
-- no debconf information
Reply to: