Bug 971621
Summary: | Book factory stuck waiting on WebDAV backend view stop | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | Red Hat Enterprise Linux 6 | Reporter: | David Jaša <djasa> | ||||||
Component: | evolution-data-server | Assignee: | Matthew Barnes <mbarnes> | ||||||
Status: | CLOSED ERRATA | QA Contact: | Desktop QE <desktop-qa-list> | ||||||
Severity: | medium | Docs Contact: | |||||||
Priority: | unspecified | ||||||||
Version: | 6.4 | CC: | jkoten, lnovich, mcrha, tpelka | ||||||
Target Milestone: | beta | ||||||||
Target Release: | --- | ||||||||
Hardware: | Unspecified | ||||||||
OS: | Unspecified | ||||||||
Whiteboard: | |||||||||
Fixed In Version: | evolution-data-server-2.32.3-5.el6 | Doc Type: | Bug Fix | ||||||
Doc Text: | Story Points: | --- | |||||||
Clone Of: | Environment: | ||||||||
Last Closed: | 2013-11-21 05:14:10 UTC | Type: | Bug | ||||||
Regression: | --- | Mount Type: | --- | ||||||
Documentation: | --- | CRM: | |||||||
Verified Versions: | Category: | --- | |||||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
Cloudforms Team: | --- | Target Upstream Version: | |||||||
Embargoed: | |||||||||
Attachments: |
|
Description
David Jaša
2013-06-07 00:20:31 UTC
Created attachment 758179 [details]
evolution backtrace
Created attachment 758192 [details]
e-addressbook-factory backtrace
It looks that evo blocks on getting information from WebDAV addressbook. If the function names are to be trusted to describe what happens, main thread of evolution is getting synchronously autocompletion data from addressbook from main thread... I'm moving this to eds, because the issue is there. Evolution only tries to create a new book view, a DBus object, which should be pretty quick, but because of the addressbook factory being stuck and waiting on the end of a previous book view object from the webdav book, it cannot respond. A solution (and a good rule) is to not block factory's UI for a long/unpredictable time. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHSA-2013-1540.html |