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.

Bug 1367455

Summary: No contacts are displayed until search is started
Product: Red Hat Enterprise Linux 7 Reporter: Jiri Koten <jkoten>
Component: evolution-mapiAssignee: Milan Crha <mcrha>
Status: CLOSED ERRATA QA Contact: Desktop QE <desktop-qa-list>
Severity: medium Docs Contact:
Priority: low    
Version: 7.3CC: mcrha
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: evolution-mapi-3.12.10-5.el7 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-11-04 00:26:04 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:

Description Jiri Koten 2016-08-16 12:57:20 UTC
Description of problem:
No contacts are displayed in Contacts addressbook on Exchange 2007 server using MAPI backend. I have to invoke search to get the contacts to show up. After that the contacts are shown until next evolution start.
 
$ evolution
openjdk version "1.8.0_102"
OpenJDK Runtime Environment (build 1.8.0_102-b14)
OpenJDK 64-Bit Server VM (build 25.102-b14, mixed mode)

(evolution:27702): eab-widgets-CRITICAL **: ea_minicard_view_get_name: assertion 'E_IS_BOOK_CLIENT (book_client)' failed


Version-Release number of selected component (if applicable):
evolution-3.12.11-21.el7
evolution-data-server-3.12.11-34.el7
evolution-mapi-3.12.10-4.el7

How reproducible:
100%

Steps to Reproduce:
1. Create MAPI account
2. Go to Contacts view and choose Contacts addressbook on exchange server.


Actual results:
No contacts are displayed, until search is started

Expected results:
Contacts should be visible right away

Additional info:

Comment 1 Milan Crha 2016-08-16 15:30:48 UTC
Thanks for a bug report and a good catch. It requires to have the book marked for offline, though I realized that the offline state wasn't recognized before the book was opened, which caused this misbehaviour also for the books marked for offline. I fixed it upstream for 3.21.91+:
https://git.gnome.org/browse/evolution-mapi/commit/?id=7b30258

Comment 5 errata-xmlrpc 2016-11-04 00:26:04 UTC
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-2016-2206.html