Bug 71387
Summary: | up2date-nox will always fail. | ||
---|---|---|---|
Product: | [Retired] Red Hat Public Beta | Reporter: | Ivo Sarak <ivo> |
Component: | up2date | Assignee: | Adrian Likins <alikins> |
Status: | CLOSED WORKSFORME | QA Contact: | Jay Turner <jturner> |
Severity: | high | Docs Contact: | |
Priority: | medium | ||
Version: | limbo | CC: | gafton, mihai.ibanescu, srevivo |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2002-08-16 23:35:33 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 67217 |
Description
Ivo Sarak
2002-08-12 21:41:28 UTC
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 |