Red Hat Bugzilla – Bug 871176
[abrt] sssd-1.9.2-1.fc18: get_naming_context: Process /usr/libexec/sssd/sssd_be was killed by signal 11 (SIGSEGV)
Last modified: 2012-12-06 23:20:52 EST
Description of problem:
Version-Release number of selected component:
libreport version: 2.0.17
cmdline: /usr/libexec/sssd/sssd_be --domain default --debug-to-files
:Thread no. 1 (10 frames)
: #0 get_naming_context at src/providers/ldap/sdap.c:749
: #1 sdap_set_config_options_with_rootdse at src/providers/ldap/sdap.c:819
: #2 sdap_cli_use_rootdse at src/providers/ldap/sdap_async_connection.c:1509
: #3 sdap_cli_rootdse_done at src/providers/ldap/sdap_async_connection.c:1469
: #4 sdap_get_rootdse_done at src/providers/ldap/sdap_async.c:943
: #5 sdap_get_generic_done at src/providers/ldap/sdap_async.c:1558
: #6 sdap_get_generic_ext_done at src/providers/ldap/sdap_async.c:1407
: #7 sdap_process_message at src/providers/ldap/sdap_async.c:366
: #8 sdap_process_result at src/providers/ldap/sdap_async.c:209
: #9 tevent_common_loop_timer_delay at ../tevent_timed.c:254
Created attachment 635167 [details]
Created attachment 635168 [details]
Created attachment 635169 [details]
Created attachment 635170 [details]
Created attachment 635171 [details]
Created attachment 635172 [details]
Created attachment 635173 [details]
Created attachment 635174 [details]
Created attachment 635175 [details]
Created attachment 635176 [details]
Created attachment 635177 [details]
Created attachment 635178 [details]
Created attachment 635179 [details]
sssd-1.9.2-2.fc18 has been submitted as an update for Fedora 18.
sssd-1.9.2-3.fc18 has been submitted as an update for Fedora 18.
* should fix your issue,
* was pushed to the Fedora 18 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing sssd-1.9.2-2.fc18'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
sssd-1.9.2-3.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report.