Red Hat Bugzilla – Bug 435573
extended repository check causes error then hard hang
Last modified: 2008-04-22 13:07:33 EDT
Description of problem:
I am getting both an error message and then a hard hang when I do something. I
assume that they are related, but they may not be.
Version-Release number of selected component (if applicable):
100% one machine. This machine works fine with a normal install.
Steps to Reproduce:
1.start a network install (http)
2.get to the part about selecting the type of install
3.at the bottom of the screen is a check box for fedora extras, check this
4.I selected to customize now (but you get a simlar result without this)
You will get a quick to fast to read error box with a cancel next button. It
says something about the repository being corrupt. But even with the next
button there it kind of "nexts" on its own.
Instead of getting the screen for detailed package selection you go right to the
"preparing to install" box.
The mouse turns to a watch and can be moved for a minute or two, then stops.
even waiting an hour will not bring anything else up.
None of the other alt ctrl fx screens show anything, but you can go to them and
then return to the f7 and get the screen with the stuck mouse watch.
going on no hang
The weirdness with buttons being clicked on their own was due to problems with
input drivers which should be fixed up now. Are you still seeing the hang with
the input problems solved?
How would I try this with the new drivers.
Frankly I doubt that this will solve the problem. But I have been wrong
before. It looks to me that it has something to do with it failing to be able
to access "fedora extras"
I did just notice something. The mirror I have been using
(chuck.ucs.indiana.edu) actually has now removed the testing repositories. So
I had to go to a new one, and low and behold a directory which was never on
chuck exists "fedoraextras". I wonder if the nonexistance of this directory
could be part of the problem.
On the other hand the nonexistance or failure to be accessable of a directory
would seem to be a reason for an error message not a hard hang.
OK this now gives a reasonable message. Now the repository seems to be there
on the mirror i am now using, mirrors.reflected.net, but I still get a nasty
message. But that is better than a hard hang. A lot better.
What's the status on this one? If you enter a repo that has troubles, you get
an error message you can recover from and there's no hang?
Still broken on the alpha release --- who cares ;-)
Tried the beta and get a better result.
The repo definitely seems to have problems. But now you do get an error
message, and then everything goes on hunky dorry. So I assume someone fixed
this even if they didn't realize it.
Think we can close this one.
Okay, thanks for the testing.