From Bugzilla Helper: User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; NetCaptor 7.0.2 Final) Description of problem: Fresh install of RedHat 9 (Shrike), I tried to use up2date (command line) to register using an existing account and up2date dies with 'Segmentation fault'. The same result when using 'rhnreg_ks'. If you could provide me with some directions to solve this problem, I would greatly appreciate it. Thanks, Dan Version-Release number of selected component (if applicable): up2date-3.1.23-1 How reproducible: Always Steps to Reproduce: 1. up2date --register 2. 3. Actual Results: Segmentation fault Additional info:
I am having the exact same problem
I have the same problem. I have re-installed the system as desktop, server, etc. all with the same result. If using gnome and clicking on the update alert icon, you do not see an error message. I have had a weeks correspondence with RH support before being directed to report it as a bug. Net result, I am now registered on rhn but no registered system to update.
I have this problem as well. I did a "Everything" install. Booted first time ok, then used the Up2date tool, and after reboot I could not start in Gnome. I receive about 10-15 segmentation errors for Gnome processes. Any news/updates/recommendations? It looks like this was originally reported about 2 months ago.
I was having this problem, but I was able to fix it by forcing a re-install of python: rpm --force -Uvh python-2.2.2-26.i386.rpm I suspect that my python install got messed up.
Bill, I have tried your suggestion, unfortunatelly it didn't solve my problem. I must have some other package messed up...
I need to know what command was invoked, and what the output was on runs that segfault. If it's possible to get the output of `strace -o /tmp/up2date.strace up2date` for a run that segfaults, that would be helpful as well. I'd also verify the package involved: rpm -V python rpm up2date up2date-gnome (attach the output if you want, but the main thing to look for is either modified libs or bins)
Created attachment 94473 [details] up2date.strace.gz
Adrian, thanks for addressing the problem. Please see the attached strace. > rpm -V python rpm up2date up2date-gnome SM5....T c /etc/sysconfig/rhn/up2date S.5....T c /etc/sysconfig/rhn/up2date-uuid SM5....T /usr/share/rhn/up2date_client/up2dateUtils.pyc package up2date-gnome is not installed > rpm -q python rpm up2date up2date-gnome python-2.2.2-26 rpm-4.2-0.69 up2date-3.1.23.2-1 package up2date-gnome is not installed
Has anything been determined on this front? I am having the same problem: up2date throws a Segmentation fault when I attempt to register a machine that has been newly built from scratch with Shrike. Following Adrian's suggestions above, I verified the packages: [root@dhcppc2 /tmp]# rpm -V python rpm up2date up2date-gnome SM5....T c /etc/sysconfig/rhn/up2date S.5....T c /etc/sysconfig/rhn/up2date-uuid .M.....T /usr/share/rhn/RHNS-CA-CERT SM5....T /usr/share/rhn/up2date_client/up2dateUtils.pyc [root@dhcppc2 /tmp]# rpm -q python rpm up2date up2date-gnome python-2.2.2-26 rpm-4.2-0.69 up2date-3.1.23.2-1 up2date-gnome-3.1.23.2-1 From what I can tell, everything is up to date (no pun intended). Any insights would be greatly appreciated.
I'm showing the exact same results as Dan and Mark. Default installation of Red Hat Linux 9 with up2date version 3.1.23.2. I know up2date was working flawlessly prior to the update to 3.1.23.2. After receiving the notification to update for the new SSL cert, the seg fault error started. (I also tried to re-install python.)
In any case, up2date is no longer shipped with Fedora Core; its functionality has been replaced by pup, found in the pirut package. The only fixes likely to be made to up2date in RedHat Linux and earlier Fedora Core versions are security fixes by Fedora Legacy. This does not seem to be a security bug, so I'm closing it. If the problem is appropriate to RHEL and occurs to a user there, it can be filed as such.