Bug 379871 - kmail does not handle connection loss gracefully
Summary: kmail does not handle connection loss gracefully
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: kdepim
Version: 5.1
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
: ---
Assignee: Lukáš Tinkl
QA Contact: desktop-bugs@redhat.com
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2007-11-13 12:50 UTC by Patrick C. F. Ernzer
Modified: 2015-07-13 17:36 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-12-16 19:05:56 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
backtrace (2.42 KB, text/plain)
2007-11-13 12:50 UTC, Patrick C. F. Ernzer
no flags Details

Description Patrick C. F. Ernzer 2007-11-13 12:50:12 UTC
Description of problem:
kmail will crash sometimes if connectivity is lost at the wrong moment. This is
really annoying for users who are on a flaky link (say UMTS on a train).

Version-Release number of selected component (if applicable):
kdepim-3.5.4-4.fc6

How reproducible:
takes a while but will eventually crash

Steps to Reproduce:
1. start kmail
2. make sure you have an IMAP server configured
3. set the check mail interval to 2 minutes
4. run the following in a root sheel to simulate flaky link
# while true; do echo down;ifdown eth0;sleep 15;echo up;ifup eth0; sleep
30;date;done
  
Actual results:
eventually kmail will crash, I've had runs where this reproducer crashed in less
than 10 minutres and runs where it took > 30 minutes (at which point I went home
for the night to find it crashed in the morning)


Expected results:
A mail user agent needs to be able to deal with connectivity loss without crashing

Additional info:
I've installed kdepim-debuginfo-3.5.4-4.fc6.i386.rpm to get a decent backtrace
from the kde crash tool. Do tell if you want further tests run.

Comment 1 Patrick C. F. Ernzer 2007-11-13 12:50:12 UTC
Created attachment 256811 [details]
backtrace


Note You need to log in before you can comment on or make changes to this bug.