Red Hat Bugzilla – Bug 101687
rhn_register segfaults on submitting RHN login information
Last modified: 2007-07-26 20:16:53 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030703
Description of problem:
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Start either rhn_register or up2date --register
2. Click Forward at the Welcome screen
3. Click Forward at the Privacy Statement
4. Either specify an existing account or a new account at the Step 2:Login page
5. Click Forward
Actual Results: rhn_register sits for 5-6 seconds, then exits with the error:
It does not give any additional error information, even when using the -v or
This also occurs with up2date-nox --register
Expected Results: rhn_register should have proceeded with the registration process.
This is a fresh install of stock Severn beta 1, default Gnome workstation
does this still occur with current versions (3.9.2x or so?)
I updated rhnlib and up2date from the latest versions in rawhide:
rhn_register still bombs out without any error message. I tried launching:
up2date -> no error, crash on submitting login
up2date -v -> ditto
rhn_register -> ditto
up2date-nox -> crash on submitting login, but this gave me a GTK dialog box that
said "Unknown error occured"
FWIW, I did a fresh install on a second system -- stock Severn beta 1 up2date
worked without a hitch, so this is definitely isolated to my first system.
I hope everyone at RH remains safe and sound during the hurricaine!
I just wiped out my Severn1 install and did a fresh Severn2 install. up2date
--register and up2date-nox --register still crash without any error messages or
log entries explaining why.
Watching the network monitor shows that the system does receive back some
packets from RHN right before up2date --register goes down.
I also tried updating up2date with the latest Rawhide release
The only odd thing I can identify with my system is that I'm using a PPPD script
to dial out on a GPRS modem instead of using the RedHat networking GUI tools.
Could this be the source of the problem?
I can confirm that in Fedora Core 1, running 'up2date --register' or
'up2date-nox --register' does not do anything.
Red Hat Linux is no longer supported by Red Hat, Inc. If you are still running
Red Hat Linux, you are strongly advised to upgrade to a current Fedora Core
release or Red Hat Enterprise Linux or comparable. Some information on which
option may be right for you is available at
Red Hat apologizes that these issues have not been resolved yet. We do want to
make sure that no important bugs slip through the cracks. Please check if this
issue is still present in a current Fedora Core release. If so, please change
the product and version to match, and check the box indicating that the
requested information has been provided. Note that any bug still open against
Red Hat Linux by the end of 2006 will be closed as 'CANTFIX'. Thanks again for
Closing as CANTFIX.