Bug 108403
Summary: | up2date crashed when alternate download directory specified, libraries now broken | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Craig McCluskey <craigm> |
Component: | up2date | Assignee: | Bret McMillan <bretm> |
Status: | CLOSED WONTFIX | QA Contact: | Fanny Augustin <fmoquete> |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | 9 | CC: | craigm, gafton, mihai.ibanescu |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i686 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2006-04-22 14:59:12 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: | 120092 |
Description
Craig McCluskey
2003-10-29 00:27:52 UTC
Since submitting the bug report, I have logged out of the system with the up2date problem. It has sat for over half-an-hour with a light blue screen with a blinking and rotating hour-glass for the mouse pointer. Typing ctrl-alt-backspace causes the screen to go black for about 3 seconds and then the blue screen with the hour-glass mouse pointer re-appears. Thus, the system is totally unusable with X. I can still log in via one of the alternate consoles, however, and scp does work (so I can copy files from my RHL9 laptop). I hope I don't have to re-install. The rpm and glibc errors would seem to be unrelated to up2date (especially since it didnt actually install any packages from your description). So I'm not sure what could be causing that problem. I'll take a look at the "storageDir" problem. I assume you mean "/var/spool/up2date" not "/var/log/up2date". Yes, I do mean /var/log/up2date. I reinstalled RHL9 on my system (fortunately I have a separate partition for /usr/local) and everything is working properly now. When I ran up2date on the re-installed system, I was careful to use the ... button to specify the alternate file storage location and up2date ran successfully. Okay, I'm confused. I'm not sure what "/var/log/up2date" has to do with this, since thats the up2date logfile, and is not the default package download path (thats "/var/spool/up2date"). Am I correct in understanding that adding a download path in the graphical configuration dialog in the "Package Storage Directory" caused problems where using the file selector dialog did not? > Okay, I'm confused. Boy, did I ever make a mistake! I really meant to type, "Yes, I do mean /var/spool/up2date," the default package download path. ^^^^^ I really did. Honest. :-) > Am I correct in understanding that adding a download path in the > graphical configuration dialog in the "Package Storage Directory" > caused problems where using the file selector dialog did not? If I understand what you're saying, yes. I executed up2date --configure and got a window entitled "Red Hat Configuration" which has three tabs. Clicking on the middle tab, Retrieval/Installation, will bring up a window which has at its bottom, Package storage directory. Typing my new storage path in the window caused the problem. Clicking on the button with the three dots just to the right and navigating to my new storage location works properly. up2date is no longer shipped with Fedora Core; it's 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. |