Bug 1151187 - after network down/up evolution stop receiving new messages and couldn't close
Summary: after network down/up evolution stop receiving new messages and couldn't close
Keywords:
Status: CLOSED DUPLICATE of bug 1148293
Alias: None
Product: Fedora
Classification: Fedora
Component: evolution
Version: 21
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Milan Crha
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-10-09 18:20 UTC by Mikhail
Modified: 2014-10-13 10:36 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-10-13 10:36:38 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)
backtraces of evolution (5.44 KB, application/x-gzip)
2014-10-09 18:20 UTC, Mikhail 		no flags Details
screenshot of evolution (251.14 KB, image/png)
2014-10-09 18:21 UTC, Mikhail 		no flags Details
View All

Description Mikhail 2014-10-09 18:20:33 UTC 
Created attachment 945423 [details]
backtraces of evolution

Description of problem:
after network down/up evolution stop receiving new messages and couldn't close
Comment 1 Mikhail 2014-10-09 18:21:06 UTC 
Created attachment 945424 [details]
screenshot of evolution
Comment 2 Milan Crha 2014-10-13 10:36:38 UTC 
Thanks for a bug report. This is a similar issue as at bug #1148293 thus I mark this as a duplicate of it. The thing is that evolution doesn't quit till there are any pending activities, which usually show themselfs in the status bar. Your screenshot shows "Fetching summary information for new messages in ..." there. The thing is that this job is ongoing, but the underlying code doesn't process it at all, the job is only waiting till it'll be processed, despite the job queue being empty (in a sense that no other job is being processed).

*** This bug has been marked as a duplicate of bug 1148293 ***
Note You need to log in before you can comment on or make changes to this bug.