After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 712983 - Replay queue not closing on connection hang or drop
Replay queue not closing on connection hang or drop
Status: RESOLVED FIXED
Product: geary
Classification: Other
Component: engine
0.2
Other All
: High normal
: ---
Assigned To: Jim Nelson
Geary Maintainers
Depends on:
Blocks:
 
 
Reported: 2012-05-30 02:53 UTC by Jim Nelson
Modified: 2013-05-01 06:49 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
hang.log (38.83 KB, text/x-log)
2012-05-30 14:53 UTC, Jim Nelson
Details

Description Charles Lindsay 2013-11-21 20:17:37 UTC


---- Reported by jim@yorba.org 2012-05-30 07:53:00 -0700 ----

Original Redmine bug id: 5321
Original URL: http://redmine.yorba.org/issues/5321
Searchable id: yorba-bug-5321
Original author: Jim Nelson
Original description:

This morning Geary wouldn't open a message when I clicked on it. It reported
that Inbox was closed.

Looking over the debug trace, it appears the problem is due to the replay
queue not closing. I suspect this has to do with a replay operation hanging
and not allowing the close command to complete.

UPDATE: Several reports have come in similar to this one. We should implement
a command timeout to ensure that outstanding commands are cancelled after a
reasonable amount of time and the connection goes into a closed state. This
should cause all queued commands to immediately fail. See also #5340.

Related issues:
related to geary - 5357: IMAP connection retry too aggressive (Fixed)
related to geary - 5358: Crash when archiving and no connection available (Open)
related to geary - 5340: Connection timeout should be five minutes (Fixed)



---- Additional Comments From geary-maint@gnome.bugs 2013-05-01 11:49:00 -0700 ----

### History

####

#1

Updated by Jim Nelson over 1 year ago

  * **Subject** changed from _INBOX not opened after connection dropped_ to _Replay queue not closing on connection hang or drop_
  * **Description** updated (diff)
  * **Assignee** set to _Jim Nelson_

####

#2

Updated by Jim Nelson over 1 year ago

  * **Status** changed from _Open_ to _5_
  * **Resolution** set to _fixed_

10599a5a42c6f34f0b4a536c32af74c21c60baf0

There are still problems if the user attempts to use Geary when no connection
is available (#5357, #5358, probably others), but this I believe this will
close the connection and reestablish if the connection hangs or a server-side
close occurs.

####

#3

Updated by Charles Lindsay 7 months ago

  * **Status** changed from _5_ to _Fixed_



--- Bug imported by chaz@yorba.org 2013-11-21 20:18 UTC  ---

This bug was previously known as _bug_ 5321 at http://redmine.yorba.org/show_bug.cgi?id=5321
Imported an attachment (id=260541)

Unknown milestone "unknown in product geary. 
   Setting to default milestone for this product, "---".
Setting qa contact to the default for this product.
   This bug either had no qa contact or an invalid one.