From Bugzilla Helper: User-Agent: Mozilla/5.0 Galeon/1.2.5 (X11; Linux i686; U;) Gecko/20020712 Description of problem: Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: Register, Entitle this machine and run up2date-nox. Actual Results: [root@machine root]# up2date-nox -u creating readOnlyTransaction Fetching package list for channel: redhat-beta-limbo-i386... ######################################## Fetching Obsoletes list for channel: redhat-beta-limbo-i386... ######################################## Testing package set / solving RPM inter-dependencies... [root@machine root]# or additional 'Segmentation Fault' message at the end. Expected Results: Proper update. Additional info: rpm -qa|grep up2date up2date-2.9.33-7.x.9 up2date-gnome-2.9.33-7.x.9
can you get a strace of that?
I seem to recall you can get a segmentation fault by running /usr/sbin/up2date -l directly (rather than via /usr/bin/up2date) with this broken version of up2date.
Hmm, seems to work for me with 2.9.40'ish code. No idea how running it as /usr/sbin/up2date would cause a segfault. I have seen weirder things though...
I can 'strace' it but what script I should run?
strace /usr/sbin/up2date -u should do it
Sorry but I already made a upgrade to newer rpm&up2date from RawHide and up2date does not crash for me anymore. [root@machine up2date]# rpm -qa|grep rpm- rpm-4.1-0.77 rpm-build-4.1-0.77 rpm-python-4.1-0.77 rpm-devel-4.1-0.77 gnorpm-0.96-14 [root@machine up2date]# rpm -qa|grep up2date up2date-2.9.40-7.x.9 up2date-gnome-2.9.40-7.x.9 [root@machine up2date]#
> can you get a strace of that? Adrian, the 2.9.33 version is the one from Limbo beta2 upgrades. It has been reported earlier that this version would terminate _silently_ upon checking dependencies. No traceback at all. There have been other bug reports about this.
Hence it is most likely a duplicate of bug #70871 (CLOSED because it works again with 2.9.38) and probably also bug #71047 (still open).
seems to be working now, closing