Bug 814241 - imapx doesn't recover after network outage
imapx doesn't recover after network outage
Product: Fedora
Classification: Fedora
Component: evolution (Show other bugs)
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Matthew Barnes
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2012-04-19 08:54 EDT by Petr Schindler
Modified: 2012-04-20 04:56 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2012-04-20 04:56:24 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
GNOME Bugzilla 667875 None None None Never

  None (edit)
Description Petr Schindler 2012-04-19 08:54:25 EDT
Description of problem:
When I turn off network connection and then turn it on again my Gmail don't recover. When I try to get new mails it freezes on updating box. It can't be cancelled so I have to kill evolution from terminal and start it again. It happens only with gmail account with imapx set up by gnome-shell's Online accounts. Another mailbox works fine with imap.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Turn network off and on again
2. Try to get new massages from imapx mailbox
Actual results:
It freezes and no mails are downloaded

Expected results:
It should recover and work properly after network outage

Additional info:
Comment 1 Milan Crha 2012-04-20 04:56:24 EDT
Thanks for a bug report. There is filled a similar upstream bug [1], thus I'm moving this there. Please see [1] for any further updates. If possible, please CC yourself there, in case upstream developers will have additional questions.

[1] https://bugzilla.gnome.org/show_bug.cgi?id=667875

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