Created attachment 612294 [details] anaconda.log Description of problem: In the anaconda network setup screen, I can select a wireless interface and even select the network I want to connect to from the drop-down box, but the Configure... button does nothing, so I can't actually use the network. (This network requires both a password and manual IP address selection, and I can't enter either.) Version-Release number of selected component (if applicable): whatever is in TC6 How reproducible: 100% Steps to Reproduce: see above Additional info: There is a similar bug being discussed at bz #852792, but I was told to file this separately on the grounds of seeing different messages in VT1. What I'm seeing is ** (anaconda:655): WARNING **: Device activation failed: (1) Creating object for path '/org/freedesktop/NetworkManager/ActiveConnection/0' failed in libnm-glib. as well as three occurrences of ** (anaconda:655): WARNING **: async_got_type: could not read properties for /org/freedesktop/NetworkManager/ActiveConnection/0: Method "Get" with signature "ss" on interface "org.freedesktop.DBus.Properties" doesn't exist and then the same for .../ActiveConnection/1, and if I let it sit then another set of the same messages will pop up every few minutes, with increasing connection numbers /2, /3, etc. I'm attaching some log files as requested in https://bugzilla.redhat.com/show_bug.cgi?id=852792#c14 ... but note that these are taken from a trial with the pre-rc3 compose mentioned in https://bugzilla.redhat.com/show_bug.cgi?id=852792#c24, not TC6. The behavior doesn't seem to have changed any :-(
Created attachment 612295 [details] ifcfg.log
Created attachment 612296 [details] syslog
https://bugzilla.redhat.com/show_bug.cgi?id=851207 had that same 'get with signature ss' message. May not be related otherwise, but felt worth noticing. Tom, could you confirm you still have trouble with RC3 (Alpha final)?
(In reply to comment #3) > Tom, could you confirm you still have trouble with RC3 (Alpha final)? I pulled down the 18-Alpha-RC3.1 netinst.iso, which seems to be a little bit newer, and it still acts just the same. The anaconda line number is 668 now, but the messages look the same otherwise. Poking at it a bit more, I discovered that I *could* pull up the configuration dialog for the wired-Ethernet port --- it's just wireless that's no go. So that makes it possibly a hardware-specific problem. I'm testing on a ThinkPad T510 (standard Red Hat corporate issue from a couple years back). The network hub setup page reports that wlan0 is "Intel Corporation Centrino Ultimate-N 6300". I've not seen any problems with this gear in the last several Fedora releases.
I said RC3 for a reason. RC3.1 is a dead spin, we are not shipping it. But this test should be valid with both, IIRC what's in RC3.1.
It is not hw dependent, marking as a duplicate of bug #855526 which is proposed for Beta Blocker. Thank you for the logs. *** This bug has been marked as a duplicate of bug 855526 ***