Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Cause: Implement Refresh of WebDAV books
Consequence: server-side changes are not recognized for WebDAV books automatically, without polling the server, which can be resource expensive
Fix: let the user Refresh the WebDAV book manually, when also a reconnect to the server is tried
Result: any server-side WebDAV book changes can be read earlier than after an update period on the backend side elapses.
Created attachment 1014017[details]
screenshot of the name of the addressbook
When I change the contact via the web interface of my ownCloud server Evolution doesn't pick up the change.
Status line shows the connected status, and next to the name of the addressbook are two arrows (I guess showing the connected status). However, when i search for the contact, I always get the old cached values. The only way how to persuade Evolution to actually check the status of the remote calendar is `pkill -f evolution-addressbook` which doesn't feel like a good user interface to me ;).
Would it be possible to tell EDS that when it feels like being off-line and search happens than it should ALWAYS try connecting just to be sure?
Using evolution-data-server-3.12.10-1.el7.x86_64
Created attachment 1014877[details]
backported eds patch
Finally not so hard, the only chunk was that yours, which I misunderstood. I at least tested that this works fine also in 3.12.11.
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.
https://rhn.redhat.com/errata/RHBA-2015-2226.html
Created attachment 1014017 [details] screenshot of the name of the addressbook When I change the contact via the web interface of my ownCloud server Evolution doesn't pick up the change. Status line shows the connected status, and next to the name of the addressbook are two arrows (I guess showing the connected status). However, when i search for the contact, I always get the old cached values. The only way how to persuade Evolution to actually check the status of the remote calendar is `pkill -f evolution-addressbook` which doesn't feel like a good user interface to me ;). Would it be possible to tell EDS that when it feels like being off-line and search happens than it should ALWAYS try connecting just to be sure? Using evolution-data-server-3.12.10-1.el7.x86_64