IMAP connections sometimes break and kmail must be closed to fix

Bug #50686 reported by Mark Florian
20
This bug affects 1 person
Affects Status Importance Assigned to Milestone
KDE PIM
Fix Released
Medium
kdepim (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: kmail

I can't reliably reproduce this bug. But if the connection is interrupted somehow with an IMAP mail store, clicking "Check Mail In" seems to fail. I'll attach a screenshot which might describe what happens better.

I'll try and get more info on this next time it happens.

Revision history for this message
Mark Florian (markrian) wrote : Screenshot of problem.

This is what I see after selecting a different mail folder (say local inbox) and then selecting the IMAP inbox. KMail is still responsive, but I cann't refresh the IMAP inbox view without restarting KMail.

Revision history for this message
Rocco Stanzione (trappist) wrote :

I've had this bug for some time, but I couldn't figure out how to word a bug report. I haven't yet figured out a cause.

Changed in kdepim:
status: Unconfirmed → Confirmed
Revision history for this message
Albert Cardona (cardona) wrote :

I have this bug too. Dapper updated to latest. This is how I can reproduce it:

- set kmail to check email every 10 minutes
- leave it open for a while (20-30 minutes)
- put the powerbook to sleep
- wake up the powerbook: kmail is stuck checking the "deleted messages" folder of my IMAP accounts

If I push "get new mail", sometimes POP mail gets fetched and sometimes not. But IMAP mail never, it's stuck.

Restarting kmail fixes the problem immediately.

Revision history for this message
Albert Cardona (cardona) wrote :

Bug https://launchpad.net/distros/ubuntu/+source/kdepim/+bug/19896 and its upstream http://bugs.kde.org/show_bug.cgi?id=104956 seems related to this, since there is a problem with synchronization and suspending to RAM.

Kenny Duffus (kduffus)
Changed in kdepim:
importance: Undecided → Medium
Revision history for this message
Rocco Stanzione (trappist) wrote :

I think the suspend-to-ram problem is a separate bug (and there is a separate bug filed). I've had this problem on three machines which were never suspended and only one of which was a laptop. As far as I can tell, it just fails occasionally to do an imap folder listing, and when it does, it can't recover, even to do a listing on another mailbox. It would be great to identify and fix the failure, but I'd be pretty happy with a workaround where it can give up on that task if I select another mailbox, and do a listing on that one (and presumably try again from the beginning if I reselect the failed folder).

Revision history for this message
Alex Midgley (alex-tapdancinggoats) wrote :

I still have this bug in Feisty. If I expand the progress bars in the lower right corner and try to manually cancel the frozen transfer, the progress bar for that transfer jumps to 50% and progress messages reads "{account name}/Sent completed" then gets stuck there. Kmail seems to be able to check other mail accounts, because the progress bars will show up and complete, but it won't show me mail in any folders, even local ones.

Revision history for this message
Michael Gorven (mgorven) wrote :

I have this bug in Gutsy (and have had it for ages). If the connection dies (which also happens when resuming from suspend) Kmail cannot reconnect properly. Sometimes I can get Kmail to reconnect and display a subfolder on the IMAP server, but still cannot get it to display the top level INBOX. Killing the kio_imap4 process doesn't help either -- Kmail has to be restarted completely.

This may have something to do with the IMAP server though. The IMAP server is a Novell GroupWise server. I'm also running a local IMAP server with dovecot, and I don't have a problem with that -- I can kill the kio_imap4 process and Kmail will reconnect to dovecot without a problem.

Revision history for this message
P (p92) wrote :

same problem in gutsy with kdelibs 4:3.5.8-0ubuntu3.1 and kmail 4:3.5.7enterprise20070926-0ubuntu2
my imap server is cyrus-imapd 2.2

related to http://bugs.kde.org/show_bug.cgi?id=76872

Revision history for this message
P (p92) wrote :

and yes, it is reproducible if you do a suspend to disk and then start again after a certain time (certainly equivalent to receiving a connection reset on the imap socket).

kmail cannot read the inbox, but can read any other imap box.

level
ii kdelibs 4:3.5.8-0ubuntu3.2
ii kmail 4:3.5.7enterprise20070926-0ubuntu2

Revision history for this message
P (p92) wrote :

seems to be fixed in hardy beta

Revision history for this message
Kenny Duffus (kduffus) wrote :

i still experience this in hardy. always when my net connection dies and quite often when my connection is slow (presumably causing time outs)

i can't change to a different mailbox all i get is the kmail splash in the message list/message frame and the list of checking folders never finishes. quiting and restarting fixes it even if my connection is still slow

Revision history for this message
P (p92) wrote : Re: [Bug 50686] Re: IMAP connections sometimes break and kmail must be closed to fix

Hello,

Did you try on hardy with a completely clean kde user ?

PascalLe Thursday 27 March 2008 13:45:33 Kenny Duffus, vous avez écrit :
> i still experience this in hardy. always when my net connection dies and
> quite often when my connection is slow (presumably causing time outs)
>
> i can't change to a different mailbox all i get is the kmail splash in
> the message list/message frame and the list of checking folders never
> finishes. quiting and restarting fixes it even if my connection is
> still slow

Revision history for this message
Lydia Pintscher (lydia-pintscher) wrote :

added upstream bug report

Changed in kdepim:
status: Unknown → Fix Released
Revision history for this message
Kenny Duffus (kduffus) wrote :

its not a dimap issues as i use imap and it sounds like the others do aswell

Changed in kdepim:
status: New → Unknown
Changed in kdepim:
status: Unknown → Fix Released
Changed in kdepim:
status: Fix Released → New
Changed in kdepim:
status: New → Fix Released
Revision history for this message
Kenny Duffus (kduffus) wrote :

i don't remember experiencing this recently on hardy with 3.5.10 (vague i know sorry)

Revision history for this message
Harald Sitter (apachelogger) wrote :

Ok, let's mark the report Incomplete.

If someone still experiences this issue in 3.5.10 or 4.1.x, please report.

Changed in kdepim:
status: Confirmed → Incomplete
Revision history for this message
Jonathan Thomas (echidnaman) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in kdepim:
status: Incomplete → Invalid
Revision history for this message
Alex Midgley (alex-tapdancinggoats) wrote :

I still have this problem in Kubuntu 8.10. It was only happening sporadically in 8.04, but after upgrading it happens every time the computer wakes up.

Changed in kdepim:
importance: Unknown → Medium
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.