Hide Forgot
Description of problem: I just started install to hard drive from thedesktop on the final-TC3 live games spin. It happened before I had any interaction with anaconda. Version-Release number of selected component: anaconda-20.25.11-1.fc20.i686 The following was filed automatically by anaconda: anaconda 20.25.11-1 exception report Traceback (most recent call first): File "/usr/lib/python2.7/site-packages/gi/overrides/Gio.py", line 171, in __call__ None) File "/usr/lib/python2.7/site-packages/pyanaconda/nm.py", line 835, in _update_settings proxy.Update(settings.get_type_string(), new_settings) File "/usr/lib/python2.7/site-packages/pyanaconda/nm.py", line 799, in nm_update_settings_of_device return _update_settings(settings_path, new_values) File "/usr/lib/python2.7/site-packages/pyanaconda/network.py", line 295, in dumpMissingDefaultIfcfgs nm.nm_update_settings_of_device(devname, [['connection', 'id', devname, None]]) File "/usr/lib/python2.7/site-packages/pyanaconda/network.py", line 1189, in networkInitialize devnames = dumpMissingDefaultIfcfgs() File "/sbin/anaconda", line 1060, in <module> networkInitialize(ksdata) GError: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: Method "Update" with signature "a{sa{sv}}" on interface "org.freedesktop.NetworkManager.Settings.Connection" doesn't exist Additional info: cmdline: /usr/bin/python /sbin/anaconda --liveinst --method=livecd:///dev/mapper/live-base cmdline_file: initrd=initrd0.img root=live:CDLABEL=Fedora-Live-Games-i686-20-TC3 rootfstype=auto ro rd.live.image quiet rhgb rd.luks=0 rd.md=0 rd.dm=0 BOOT_IMAGE=vmlinuz0 executable: /sbin/anaconda hashmarkername: anaconda kernel: 3.11.9-300.fc20.i686 other involved packages: pygobject3-base-3.10.2-1.fc20.i686 product: Fedora release: Fedora release 20 (Heisenbug) type: anaconda version: 20
Created attachment 830799 [details] File: anaconda-tb
Created attachment 830800 [details] File: anaconda.log
Created attachment 830801 [details] File: environ
Created attachment 830802 [details] File: journalctl
Created attachment 830803 [details] File: lsblk_output
Created attachment 830804 [details] File: nmcli_dev_list
Created attachment 830805 [details] File: os_info
Created attachment 830806 [details] File: program.log
Created attachment 830807 [details] File: storage.log
Created attachment 830808 [details] File: ifcfg.log
I didn't see this when I did an install to hard drive using a TC4 image. So for now, I'll assume it was a bug that was fixed between TC3 and TC4.