The following was filed automatically by anaconda: anaconda 13.42 exception report Traceback (most recent call first): File "/usr/lib/python2.6/site-packages/dbus/connection.py", line 630, in call_blocking message, timeout) File "/usr/lib/python2.6/site-packages/dbus/proxies.py", line 140, in __call__ **keywords) File "/usr/lib/python2.6/site-packages/dbus/proxies.py", line 68, in __call__ return self._proxy_method(*args, **keywords) File "/usr/lib/anaconda/isys.py", line 338, in getDeviceProperties device_interface = str(device_props_iface.Get(NM_MANAGER_IFACE, "Interface")) File "/usr/lib/anaconda/network.py", line 277, in __init__ devhash = isys.getDeviceProperties(dev=None) File "/usr/sbin/anaconda", line 546, in network self._network = network.Network() File "/usr/lib/anaconda/iw/network_gui.py", line 82, in getNext self.anaconda.network.hostname = hostname File "/usr/lib/anaconda/gui.py", line 1309, in nextClicked rc = self.currentWindow.getNext () DBusException: org.freedesktop.DBus.Error.AccessDenied: Interface "org.freedesktop.NetworkManager" isn't exported (or may not exist), can't access property "Interface"
Created an attachment (id=442443) Attached traceback automatically from anaconda.
I testing the anaconda installer in a kickstart build using the following packages (per Bug # 623237) with SELinux in PERMISSIVE mode. python-slip-0.2.13-1.fc13.noarch python-slip-dbus-0.2.13-1.fc13.noarch python-slip-gtk-0.2.13-1.fc13.noarch After the installer has me select a drive it dumps the attached error messages.
Is NetworkManager even running? You can check on tty2. Also is this the F13 GA, or is it a rebuild with the GA anaconda?
"service NetworkManager status" reports it is running and I see the icon on the toolbar. This is a rebuild via kickstart. # rpm -qa | grep anaconda anaconda-13.42-1.fc13.i686 anaconda-yum-plugins-1.0-5.fc12.noarch Thank you. Dave
This looks to be because NM has been updated in F13 and has changed some piece of API such that released anaconda no longer works with it. Fantastic. Insert rant about Fedora update policy here.
*** This bug has been marked as a duplicate of bug 626780 ***