Red Hat Bugzilla – Bug 971621
Book factory stuck waiting on WebDAV backend view stop
Last modified: 2014-01-02 04:07:16 EST
Description of problem:
evolution UI blocks for several seconds after the at sign '@' is typed for the first time into recipients fields of new message.
I've got two auto-completion "accounts" set up: caldav and ldap. I tried to disable one of them at time but no apparent change of behaviour happened so I can't tell if any of them is the culprit or if the behaviour is reproducible regardless of the account type.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. have auto-completion configured
2. type an email address fluently
once you type '@' character, evo UI stops responding for a while for few seconds, if you continue typing without feedback, few shorter blocks will follow.
All the characters entered while the UI doesn't respond will be printed once the UI starts responding again.
Evolution UI never blocks, any IO should be performed in a separate thread.
Optimally user should be notified somehow (in this case by appearing of drop-down menu with a spinning wheel)
Created attachment 758179 [details]
Created attachment 758192 [details]
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.