Bug 1022406 - evolution is stuck on downloading new messages
Summary: evolution is stuck on downloading new messages
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: evolution
Version: 19
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Matthew Barnes
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-10-23 08:39 UTC by Tomas Tomecek
Modified: 2013-10-24 07:26 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-10-24 07:26:21 UTC
Type: Bug

Attachments (Terms of Use)
evolution run from gdb (109.92 KB, text/plain)
2013-10-23 08:39 UTC, Tomas Tomecek 		no flags Details
gdb attached to running evo (18.40 KB, text/plain)
2013-10-23 08:40 UTC, Tomas Tomecek 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Tomas Tomecek 2013-10-23 08:39:22 UTC 
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):
evolution-3.8.5-2.fc19.x86_64

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 08:40:05 UTC 
Created attachment 815273 [details]
gdb attached to running evo
Comment 2 Tomas Tomecek 2013-10-24 07:26:21 UTC 
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.