Red Hat Bugzilla – Bug 1002487
bug occurs when I change the installation source
Last modified: 2013-09-04 09:01:56 EDT
Description of problem:
Do a default install,change the installation source twice,bug occurs.Actually,
I thought maybe this version of anaconda is too brittle(as it's alpha Tc2) ,so I click into and out"INstallation destination",but unfortunately or fortunately,no bug occurs.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.Do a default install
2.change the install source to "http://download.fedoraproject.org/...",click"Done"
3.after the error checking ,change install source again,and click"Done",bug occurs
no bug occurs,even change "installation source" many times.
Created attachment 791677 [details]
Created attachment 791678 [details]
Created attachment 791679 [details]
Created attachment 791680 [details]
Can you be more specific? What bug occurs? Is there a traceback? Can you attach the traceback data to this bug?
As,you can see in the attachment,anaconda crashed.I thought the logs and my specific description would be enough，sorry for the time. To help you figure out the problem,I attach the step-by step sreen shots here.
Created attachment 792018 [details]
Created attachment 792019 [details]
Created attachment 792020 [details]
Created attachment 792021 [details]
Created attachment 793348 [details]
lnie, the log files you attached do not contain information about the crash. When anaconda crashes, the crash data is written to a file named /tmp/anaconda-tb-*. I've attached the traceback from a crash that I was able to create. Is this the same bug you are seeing? You can also see the crash data by clicking on the "More Info" link in the window you see in Step 4. If this is the same crash, you should see the message, "AttributeError: 'FC3_Cdrom' object has no attribute 'noverifyssl'". If not, please attach the anaconda-tb file in /tmp.
If this crash is the same as the one I encountered, it is fixed by the fix for bug 1001081.
David,they are the same.I cann't believe that I forgot to attach that important one!I should sent myself to face the wall right now,so see you in next bug,haha.
No problem, glad we could get it worked out