Description of problem: boot, acepted fate, switched to closest mirror too quicly (this similar tho another bug) Version-Release number of selected component: anaconda-18.14 Additional info: libreport version: 2.0.14 cmdline: /usr/bin/python /sbin/anaconda kernel: 3.6.1-1.fc18.x86_64 description: :The following was filed automatically by anaconda: :anaconda 18.14 exception report :Traceback (most recent call first): : File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 617, in doPluginSetup : raise RuntimeError(_("plugins already initialised")) : File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 373, in _getConfig : startupconf.pluginconfpath,disabled_plugins,enabled_plugins) : File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 1013, in <lambda> : conf = property(fget=lambda self: self._getConfig(), : File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 675, in _getRepos : self.conf # touch the config class first : File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 1005, in <lambda> : repos = property(fget=lambda self: self._getRepos(), : File "/usr/lib64/python2.7/site-packages/pyanaconda/packaging/yumpayload.py", line 352, in repos : return self._yum.repos.repos.keys() : File "/usr/lib64/python2.7/site-packages/pyanaconda/packaging/yumpayload.py", line 363, in baseRepo : if repo_name in self.repos and \ : File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/spokes/software.py", line 137, in status : if threadMgr.get("AnaPayloadMDThread") or self.payload.baseRepo is None: : File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/hubs/__init__.py", line 198, in _updateCompleteness : spoke.selector.set_property("status", spoke.status) : File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/hubs/__init__.py", line 255, in _update_spokes : self._updateCompleteness(spoke) :RuntimeError: plugins already initialised
Created attachment 624418 [details] File: anaconda-tb
Created attachment 624419 [details] File: product
Created attachment 624420 [details] File: type
Created attachment 624421 [details] File: ifcfg.log
Created attachment 624422 [details] File: storage.log
Created attachment 624423 [details] File: version
Created attachment 624424 [details] File: environ
Created attachment 624425 [details] File: anaconda.log
Created attachment 624426 [details] File: syslog
Created attachment 624427 [details] File: hashmarkername
Created attachment 624428 [details] File: packaging.log
Created attachment 624429 [details] File: cmdline_file
Created attachment 624430 [details] File: release
Created attachment 624431 [details] File: program.log
Could you expand upon your steps for reproducing this? It sounds highly timing-dependent.
Yes, it looks that timing is key here. The following must be performed as fast as possible. 1- select default language (leave as engish) in the WELCOME screen 2- accept your fate 3- enter INSTALATION SOURCE and select ON THE NETWORK and NEAREST MIRROR and return to the main hub. Notes: * Changing the nameserver before trying does not prevent the issue. * Waiting in the WELCOME screen does not prevent the issue. * By just waiting some seconds after entering INSTALLATION SOURCE, the issue is avoided. * Waiting for GNOME dependencies to be resolved before entering INSTALLATION SOURCE also prevents the issue from happening. So, it appears that swiching the INSTALLATION SOURCE while GNOME dependencies are being resolved from DVD to NEAREST MIRROR can cause this issue. Nevertheless, anaconda should not crash. Maybe it is not 100% safe to switch INSTALLATION SOURCE while dependencies are being resolved. And lastly, my 'NEAREST MIRROR' will not be the same for other people? After all, it is a mirror. What if there is some issue there?
Take a look at 867591, it is the inverse problem (switching from CLOSEST MIRROR to DVD while resolving dependencies).
I believe Jesse's fix for bug 867591 will fix this issue too, though, because you will be prevented from doing step #3 above - you will not be able to enter the source spoke while dep checking progresses.
This bug looks to have been fixed for many anaconda builds now but missed being closed. If you find you are still experiencing it with Fedora 18 Beta (RC1) or later, please re-open the bug.