Bug 65752
Summary: | impossible to reach final update summary screen using GUI | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | colin redfern <redhat_bugzilla> |
Component: | up2date | Assignee: | Adrian Likins <alikins> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Jay Turner <jturner> |
Severity: | medium | Docs Contact: | |
Priority: | low | ||
Version: | 7.2 | CC: | gafton, jmd, mihai.ibanescu, srevivo |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
URL: | redhat_bugzilla@trancecode.co.uk | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2003-02-14 15:39:24 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: |
Description
colin redfern
2002-05-31 09:23:44 UTC
what version of the client is this? [root@bob root]# rpm -q up2date up2date-2.7.61-7.x.2 I get this same thing. Two of my last three updates have crashed with the exact error the reporter gives after installation is 100%. I have to ^C up2date and I worry it may be doing Bad Things to my RPM db. up2date-2.7.61-7.x.2 (Red Hat 7.2) This never happened before... I've done up2date every day an update was available since 7.2 was released. There were new up2date packages some time ago... eaither that, or some different network input for an enhanced client in 7.3? I just got this exact same error on another machine. on a completely fresh RH7.2 install I ran up2date for the first time and updated only some selected essentials from the available list. Those that i can remember were all assosciated with up2date and libc/glibc the next day I run up2date and get the error. once again $rpm -q up2date up2date-2.7.61-7.x.2 ugh, yeah. Fixed in all current code bases. I belive this fix has made it into all errata as well (2.8.39 for that platform) Fix confirmed with latest released code. |