Red Hat Bugzilla – Bug 667363
rhn-setup-1.0.0-38.el6: __strncmp_ssse3: Process /usr/bin/python was killed by signal 11 (SIGSEGV)
Last modified: 2014-01-12 19:13:11 EST
Description of problem:
cmdline: /usr/bin/python /usr/sbin/rhn_register
reason: Process /usr/bin/python was killed by signal 11 (SIGSEGV)
Version-Release number of selected component (if applicable):
release: Red Hat Enterprise Linux Server release 6.0 (Santiago)
Steps to Reproduce:
1. Login as root
2. start rhn_register
3. enter valid user name/password and click next
rhn_register should not crash
Created attachment 471844 [details]
Created attachment 471845 [details]
This one is the same as bug #596264. A fix is proposed there for RHEL5.6.
Just a little double check, which version of python-dmidecode is RHEL6 shipping with?
Rhel6 has a python-dmidecode-3.10.12-1.el6.x86_64
See bug #596264 and especially attachment #472083 [details] for more a solution. All patches in the attachment have been sent upstream already and is needed in python-dmidecode-3.10.12.
Fixed in python-dmidecode-3.10.13-1.el6
Technical note added. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
Prior to this update, when running the rhn_register utility, providing a valid user name and password, and clicking the Forward button, the tool terminated unexpectedly with a segmentation fault. This was caused by the dmi_processor_id() function not checking whether the version pointer was NULL. This update adds additional checks for NULL values, fixing the problem.
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.