Description of problem: Applied updates.img with commits for bug 1025029 (among others). Fails when you click Continue on the welcome screen. Version-Release number of selected component: anaconda-20.25.6-1 The following was filed automatically by anaconda: anaconda 20.25.6-1 exception report Traceback (most recent call first): File "/tmp/updates/pyanaconda/ui/gui/__init__.py", line 203, in __init__ self.builder.add_objects_from_file(self._findUIFile(), self.builderObjects) File "/tmp/updates/pyanaconda/ui/gui/spokes/__init__.py", line 32, in __init__ GUIObject.__init__(self, data) File "/tmp/updates/pyanaconda/ui/gui/spokes/__init__.py", line 78, in __init__ Spoke.__init__(self, data) File "/tmp/updates/pyanaconda/ui/gui/spokes/datetime_spoke.py", line 351, in __init__ NormalSpoke.__init__(self, *args) File "/tmp/updates/pyanaconda/ui/gui/hubs/__init__.py", line 176, in _createBox spoke = spokeClass(self.data, self.storage, self.payload, self.instclass) File "/tmp/updates/pyanaconda/ui/gui/hubs/__init__.py", line 380, in refresh self._createBox() File "/tmp/updates/pyanaconda/ui/gui/__init__.py", line 740, in _on_continue_clicked nextAction.refresh() File "/tmp/updates/pyanaconda/ui/gui/spokes/__init__.py", line 68, in _on_continue_clicked cb() File "/tmp/updates/pyanaconda/ui/gui/spokes/welcome.py", line 317, in _on_continue_clicked StandaloneSpoke._on_continue_clicked(self, cb) File "/tmp/updates/pyanaconda/ui/gui/spokes/__init__.py", line 72, in <lambda> self.window.connect("continue-clicked", lambda *args: self._on_continue_clicked(cb)) GError: Duplicate object ID 'regions' on line 78 (previously on line 29) Additional info: cmdline: /usr/bin/python /sbin/anaconda cmdline_file: initrd=initrd.img inst.stage2=hd:LABEL=Fedora\x2020-Beta\x20x86_64 updates=http://updates.notae.us/updates.img BOOT_IMAGE=vmlinuz executable: /sbin/anaconda hashmarkername: anaconda kernel: 3.11.6-301.fc20.x86_64 product: Fedora release: Cannot get release name. type: anaconda version: 20-Beta
Created attachment 821815 [details] File: anaconda-tb
Created attachment 821816 [details] File: anaconda.log
Created attachment 821817 [details] File: environ
Created attachment 821818 [details] File: lsblk_output
Created attachment 821819 [details] File: nmcli_dev_list
Created attachment 821820 [details] File: os_info
Created attachment 821821 [details] File: program.log
Created attachment 821822 [details] File: storage.log
Created attachment 821823 [details] File: syslog
Created attachment 821824 [details] File: ifcfg.log
Created attachment 821825 [details] File: packaging.log
Patch removing the duplicate definition pushed to the f20-branch. Unfortunately without the bug number.
Same problem, but with regionCompletion now. You'd think glade would prevent this.
(In reply to Brian C. Lane from comment #13) > Same problem, but with regionCompletion now. > > You'd think glade would prevent this. It might do, but this is the result of merging things from master to f20-branch. Because on master, we have all the glade files saved with the new Glade, so porting these changes mean manually modifying the XML files. Which I obviously suck at doing. :)
A patch with two more changes pushed to f20-branch. I've tested it and everything seems okay now.
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.