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.
Description of problem:
When I access Global Address List for the first time (i.e. I just created Exchange MAPI account), the contacts are not displayed. It spins in "Searching for Contacts" and I have to preform some action like Search to get the contacts displayed.
I got these warnings from eds's console when GAL is loaded for the first time:
e-data-server-CRITICAL **: e_file_cache_get_object: assertion `key != NULL' failed
libedata-book-WARNING **: found a contact with NULL uid
And also this when I access GAL:
e_book_backend_mapigal_new...
(process:4105): libebook-CRITICAL **: e_contact_field_name: assertion `field_id >= 1 && field_id <= E_CONTACT_FIELD_LAST' failed
(process:4105): libebook-CRITICAL **: e_contact_field_name: assertion `field_id >= 1 && field_id <= E_CONTACT_FIELD_LAST' failed
...
(process:4105): libebook-CRITICAL **: e_contact_field_name: assertion `field_id >= 1 && field_id <= E_CONTACT_FIELD_LAST' failed
=> 0x7f0d28036c10
impl_GNOME_Evolution_Addressbook_Book_open (0x7f0d28036c10)
Loading the summary
Loading the cache
FIXME: Should check for an update in the cache
Version-Release number of selected component (if applicable):
evolution-mapi-0.28.3-7.el6.x86_64
evolution-2.28.3-22.el6.x86_64
evolution-data-server-2.28.3-15.el6
How reproducible:
100%
Steps to Reproduce:
1. Create Exchange MAPI account
2. Go to addressbook and choose a MAPI book GAL
Actual results:
Searching for Contacts ...
Expected results:
Contacts are displayed
Comment 1RHEL Program Management
2011-07-06 00:22:30 UTC
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unfortunately unable to
address this request at this time. Red Hat invites you to
ask your support representative to propose this request, if
appropriate and relevant, in the next release of Red Hat
Enterprise Linux. If you would like it considered as an
exception in the current release, please ask your support
representative.
I just tested this with evoltuion-mapi 0.32.2 and it shows the GAL right after new account configuration. There is a little delay after selecting it in evolution's GUI, which is about connection to the server on the e-addressbook-factory side, and about download of the contacts, but there are no critical warnings on the factory side anymore.
That said, this is addressed by the rebase.
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