Bug 1022406 - evolution is stuck on downloading new messages
evolution is stuck on downloading new messages
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: 2013-10-23 04:39 EDT by Tomas Tomecek
Modified: 2013-10-24 03:26 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2013-10-24 03:26:21 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)
evolution run from gdb (109.92 KB, text/plain)
2013-10-23 04:39 EDT, Tomas Tomecek
no flags Details
gdb attached to running evo (18.40 KB, text/plain)
2013-10-23 04:40 EDT, Tomas Tomecek
no flags Details

  None (edit)
Description Tomas Tomecek 2013-10-23 04:39:22 EDT
Created attachment 815272 [details]
evolution run from gdb

Description of problem:
Recently evolution is getting stuck on "Downloading new messages for offline mode". It spawns a lot of tasks (~15) and they get stuck (GUI is accessible, but no messages are being downloaded). I have to kill it (several times) and then after several hours it "starts to work somehow". This happens when I resume my laptop from suspend state.

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

Additional info:
I am providing 2 backtraces.
evo_running_bt.log -- is a backtrace from running evolution
evo_from_gdb.log -- is a backtrace from evolution run from gdb (this one has variables ((gdb) t a a bt full))
Comment 1 Tomas Tomecek 2013-10-23 04:40:05 EDT
Created attachment 815273 [details]
gdb attached to running evo
Comment 2 Tomas Tomecek 2013-10-24 03:26:21 EDT
I made an update this morning and the problem disappeared. I think that the real issue was in gnome-online-accounts.

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