Bug 854271 - evolution stuck again
Summary: evolution stuck again
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: evolution
Version: 17
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: 2012-09-04 14:35 UTC by Mikhail
Modified: 2012-09-05 08:53 UTC (History)
3 users (show)

Fixed In Version: evolution-ews-3.5.92
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-09-05 08:53:25 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
Evolution screenshot (396.09 KB, image/png)
2012-09-04 14:35 UTC, Mikhail
no flags Details
backtrace evolution (36.04 KB, text/plain)
2012-09-04 14:36 UTC, Mikhail
no flags Details
backtrace evolution (36.04 KB, text/plain)
2012-09-04 14:37 UTC, Mikhail
no flags Details

Description Mikhail 2012-09-04 14:35:38 UTC
Created attachment 609704 [details]
Evolution screenshot

$ rpm -qa | grep evolution | sort
evolution-3.4.4-1.fc17.i686
evolution-data-server-3.4.4-2.fc17.i686
evolution-data-server-debuginfo-3.4.4-2.fc17.i686
evolution-debuginfo-3.4.4-1.fc17.i686
evolution-ews-3.4.4-1.2.fc17.i686
evolution-ews-debuginfo-3.4.4-1.2.fc17.i686
evolution-exchange-3.4.4-2.fc17.i686
evolution-exchange-debuginfo-3.4.4-2.fc17.i686
evolution-mapi-3.4.4-1.fc17.i686
evolution-mapi-debuginfo-3.4.4-1.fc17.i686
evolution-NetworkManager-3.4.4-1.fc17.i686

Description of problem:

1. Switch to another network interface (exchange in unavailable) 
2. Click on non recieved messages (in bottom see progress bar)
3. Repeat step 2 until the whole botton panel was occupied by a progress indicator
4. Press "Send / Receive" button
5. Try to cantel

Evolution now hangs

Comment 1 Mikhail 2012-09-04 14:36:18 UTC
Created attachment 609705 [details]
backtrace evolution

Comment 2 Mikhail 2012-09-04 14:37:13 UTC
Created attachment 609706 [details]
backtrace evolution

Comment 3 Milan Crha 2012-09-05 08:47:01 UTC
Thanks for a bug report. I see from the backtrace what is going on, but it is not fixable in 3.4.x that easily. The 3.5.91 contains improvements which makes this easier. I checked the upstream code and I see that it still can happen there, thus I'm fixing it there.

Comment 4 Milan Crha 2012-09-05 08:53:25 UTC
Created commit d049ef2 in ews master (3.5.92+)


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