Red Hat Bugzilla – Bug 463278
Incorrect D-Bus system bus user ID in system.conf
Last modified: 2015-01-07 19:16:38 EST
Description of problem:
I'm not sure is this is NetworkManager, dbus, or something else, but after updating to the 20080919.2 Client tree today (via 'yum update') my wireless is no longer working. The ipw3945d service is working just fine but the wireless device never shows up in the NM applet.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Load up a 5.3-candidate tree on a box with wireless, see if it works after enabling NetworkManager and disabling the network service
benl is seeing the same behavior with an ipw2200 card. The only thing which appears in syslog is:
Sep 22 15:55:17 haring NetworkManager: <info> Trying to start the supplicant...
Sep 22 15:55:17 haring NetworkManager: <info> Trying to start the system settings daemon...
Sep 22 15:55:17 haring setroubleshoot: SELinux is preventing dbus-daemon (system_dbusd_t) "execute_no_trans" to /lib/dbus-1/dbus-daemon-launch-helper (lib_t). For complete SELinux messages. run sealert -l 7d323053-21fe-498b-b952-0db027210767
which points back to bug 463267 so that might be at the heart of the issue. The odd thing is that I'm having this problem in permissive as well as with selinux completely disabled, which seems odd for a denial.
Some additional information. Got the dbus selinux issues resolved, loaded up the new NetworkManager (0.7.0-0.11.svn4088.el5) and here's what I get when restarting NM (picking just the stuff related to eth0, the wireless interface):
Sep 23 14:30:40 haring NetworkManager: <info> eth0: driver is 'ipw3945'.
Sep 23 14:30:40 haring NetworkManager: <info> eth0: driver does not support SSID scans (scan_capa 0x00).
Sep 23 14:30:40 haring NetworkManager: <info> Found new 802.11 WiFi device 'eth0'.
Sep 23 14:30:40 haring NetworkManager: <info> (eth0): exported as /org/freedesktop/Hal/devices/net_00_13_02_4a_10_55
Sep 23 14:30:40 haring NetworkManager: <info> Trying to start the supplicant...
Sep 23 14:30:44 haring NetworkManager: <info> (eth0): device state change: 1 -> 2
Sep 23 14:30:44 haring NetworkManager: <info> (eth0): bringing up device.
Sep 23 14:30:44 haring kernel: ADDRCONF(NETDEV_UP): eth0: link is not ready
Sep 23 14:30:44 haring NetworkManager: <info> (eth0): preparing device.
Sep 23 14:30:44 haring NetworkManager: <info> (eth0): deactivating device.
Sep 23 14:30:44 haring NetworkManager: supplicant_interface_acquire: assertion `mgr_state == NM_SUPPLICANT_MANAGER_STATE_IDLE' failed
The last entry is quite interesting, as that's new with the NM rebase and might be the cause of the problems.
After NM gets launched, is a wpa_supplicant process running? Should be something like:
/usr/sbin/wpa_supplicant -c /etc/wpa_supplicant/wpa_supplicant.conf -u -f /var/log/wpa_supplicant.log
Very strange. No, there's not a wpa_supplicant process. In fact, the wpa_supplicant service is chkconfig'd off for all runlevels.
The good news is that after configuring and starting the service manually, appears things are working. Appears that NM is no longer handling the initiation of wpa_supplicant correctly. Let me know what other information I can provide.
Ok, that means we have issues with D-Bus service activation, probably due to the SELinux stuff. You shouldn't need to chkconfig the supplicant service on because it should be started on-demand by NM via dbus service activation.
If you chkconfig wpa_supplicant off again, and set selinux to permissive mode, then reboot, does you get the supplicant process?
Issue appears to be an incorrect user ID in the dbus system bus configuration. Will build dbus-1.1.2-10.el5 to fix.
1.1.2-10.el5 makes things lots happier.
dbus-1.1.2-10.el5 included in 20080930.0 candidate trees.
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.