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 1278701 - missing chunk for initialization of the hash table and a mutex
Summary: missing chunk for initialization of the hash table and a mutex
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: evolution-data-server
Version: 7.2
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Milan Crha
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On: 1254199
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-11-06 08:40 UTC by Tomas Pelka
Modified: 2016-11-04 00:24 UTC (History)
4 users (show)

Fixed In Version: evolution-data-server-3.12.11-25.el7
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-11-04 00:24:57 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
the missing chunk (774 bytes, patch)
2015-11-06 12:00 UTC, Milan Crha 		no flags Details | Diff
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:2206 0 normal SHIPPED_LIVE evolution-data-server bug fix update 2016-11-03 13:23:16 UTC

Description Tomas Pelka 2015-11-06 08:40:41 UTC 
Description of problem:
Folks eds test get stuck, not sure what is wrong but when I try to run the single binary e.g. ./add-contacts-stress-test I can see

** (/home/tpelka2/rpmbuild/BUILD/folks-0.10.1/tests/eds/.libs/lt-add-contacts-stress-test:24317): DEBUG: test-case.vala:138: setting up in transient directory /tmp/folks-test.DlbSZi
Unable to reload configuration: Failed to open "/tmp/g-test-dbus-DHDM7X": No such file or directory
Unable to reload configuration: Failed to open "/tmp/g-test-dbus-DHDM7X": No such file or directory
Unable to reload configuration: Failed to open "/tmp/g-test-dbus-DHDM7X": No such file or directory
Unable to reload configuration: Failed to open "/tmp/g-test-dbus-DHDM7X": No such file or directory
Unable to reload configuration: Failed to open "/tmp/g-test-dbus-DHDM7X": No such file or directory
Unable to reload configuration: Failed to open "/tmp/g-test-dbus-DHDM7X": No such file or directory
Unable to reload configuration: Failed to open "/tmp/g-test-dbus-DHDM7X": No such file or directory
Unable to reload configuration: Failed to open "/tmp/g-test-dbus-DHDM7X": No such file or directory
Unable to reload configuration: Failed to open "/tmp/g-test-dbus-DHDM7X": No such file or directory
Unable to reload configuration: Failed to open "/tmp/g-test-dbus-DHDM7X": No such file or directory
Unable to reload configuration: Failed to open "/tmp/g-test-dbus-DHDM7X": No such file or directory
Unable to reload configuration: Failed to open "/tmp/g-test-dbus-DHDM7X": No such file or directory
Unable to reload configuration: Failed to open "/tmp/g-test-dbus-DHDM7X": No such file or directory
Unable to reload configuration: Failed to open "/tmp/g-test-dbus-DHDM7X": No such file or directory
Unable to reload configuration: Failed to open "/tmp/g-test-dbus-DHDM7X": No such file or directory
Unable to reload configuration: Failed to open "/tmp/g-test-dbus-DHDM7X": No such file or directory
Unable to reload configuration: Failed to open "/tmp/g-test-dbus-DHDM7X": No such file or directory
Unable to reload configuration: Failed to open "/tmp/g-test-dbus-DHDM7X": No such file or directory
Unable to reload configuration: Failed to open "/tmp/g-test-dbus-DHDM7X": No such file or directory
Unable to reload configuration: Failed to open "/tmp/g-test-dbus-DHDM7X": No such file or directory
Unable to reload configuration: Failed to open "/tmp/g-test-dbus-DHDM7X": No such file or directory
Unable to reload configuration: Failed to open "/tmp/g-test-dbus-DHDM7X": No such file or directory
Unable to reload configuration: Failed to open "/tmp/g-test-dbus-DHDM7X": No such file or directory
Unable to reload configuration: Failed to open "/tmp/g-test-dbus-DHDM7X": No such file or directory
Unable to reload configuration: Failed to open "/tmp/g-test-dbus-DHDM7X": No such file or directory
Unable to reload configuration: Failed to open "/tmp/g-test-dbus-DHDM7X": No such file or directory
/AddContactsStressTestTests/stress testing adding (1000) contacts to e-d-s : Activating service name='org.gnome.evolution.dataserver.Sources3'
Successfully activated service 'org.gnome.evolution.dataserver.Sources3'

(evolution-source-registry:24348): GLib-CRITICAL **: g_hash_table_insert_internal: assertion 'hash_table != NULL' failed

(evolution-source-registry:24348): GLib-CRITICAL **: g_hash_table_insert_internal: assertion 'hash_table != NULL' failed

(evolution-source-registry:24348): GLib-CRITICAL **: g_hash_table_insert_internal: assertion 'hash_table != NULL' failed

(evolution-source-registry:24348): GLib-CRITICAL **: g_hash_table_insert_internal: assertion 'hash_table != NULL' failed

(evolution-source-registry:24348): GLib-CRITICAL **: g_hash_table_insert_internal: assertion 'hash_table != NULL' failed

(evolution-source-registry:24348): GLib-CRITICAL **: g_hash_table_insert_internal: assertion 'hash_table != NULL' failed

(evolution-source-registry:24348): GLib-CRITICAL **: g_hash_table_foreach: assertion 'hash_table != NULL' failed

(evolution-source-registry:24348): GLib-CRITICAL **: g_hash_table_destroy: assertion 'hash_table != NULL' failed


Version-Release number of selected component (if applicable):
folks-0.10.1-1.el7

How reproducible:
100%

Steps to Reproduce:
1. rebuild folks
2. make check
3.

Actual results:
see description

Expected results:
should pass, like other tests

Additional info:
Comment 1 Tomas Pelka 2015-11-06 11:31:19 UTC 
Possible bug in eds, Milan partially confirmed.
Comment 2 Milan Crha 2015-11-06 11:53:40 UTC 
I'm moving this to evolution-data-server, where the core issue is. I missed one chunk when backporting a patch for bug #1254199. It's about all those critical warnings from g_hash_table_...() calls.
Comment 3 Milan Crha 2015-11-06 12:00:40 UTC 
Created attachment 1090648 [details]
the missing chunk

for evolution-data-server;

This is the missing chunk; as can be seen, an initialization of the hash table and a mutex had been missing.

From what I read in the glib2 sources, the evolution-source-registry won't crash due to this, the mutex is initialized on demand. The critical warnings about g_hash_table_...() calls are due to the hash_table being a NULL pointer. This can have some side-effects, like in the case of the folks' `make check`, but otherwise no harm like the crash.

The first time there's recognized a source change in the file system it prints the errors, then the missing hash table is created again, thus it starts working as expected after that.
Comment 8 errata-xmlrpc 2016-11-04 00:24:57 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
Note You need to log in before you can comment on or make changes to this bug.