After today's update, nm-applet can't find my wireless device. This shows up in /var/log/messages:
Jan 28 10:33:41 xyz NetworkManager: <WARNING> nm_dbus_get_networks_cb (): nm-dbus-nmi.c:527 (nm_dbus_get_networks_cb): error received: org.freedesktop.DBus.Error.AccessDenied - An SELinux policy prevents this sender from sending this message to this recipient (rejected message had interface "org.freedesktop.NetworkManagerInfo" member "getNetworks" error name "(unset)" destination "org.freedesktop.NetworkManagerInfo").
Anyone know a workaround? I disabled selinux and it works fine.
thanks, Brian
On 1/28/06, Brian C. huffman huffman@graze.net wrote:
After today's update, nm-applet can't find my wireless device. This shows up in /var/log/messages:
Jan 28 10:33:41 xyz NetworkManager: <WARNING> nm_dbus_get_networks_cb (): nm-dbus-nmi.c:527 (nm_dbus_get_networks_cb): error received: org.freedesktop.DBus.Error.AccessDenied - An SELinux policy prevents this sender from sending this message to this recipient (rejected message had interface "org.freedesktop.NetworkManagerInfo" member "getNetworks" error name "(unset)" destination "org.freedesktop.NetworkManagerInfo").
Anyone know a workaround? I disabled selinux and it works fine.
thanks, Brian
Looks like NetworkManager 'moved' to /usr/sbin.
'chcon -t NetworkManger_exec_t /usr/sbin/NetworkManager' will help, but appears to be one more 'misconnect'.
Running in permissive mode (e.g., booting with 'enforcing=0') should work until this gets fixed.
tom -- Tom London
Brian C. huffman wrote:
After today's update, nm-applet can't find my wireless device. This shows up in /var/log/messages:
Jan 28 10:33:41 xyz NetworkManager: <WARNING> nm_dbus_get_networks_cb (): nm-dbus-nmi.c:527 (nm_dbus_get_networks_cb): error received: org.freedesktop.DBus.Error.AccessDenied - An SELinux policy prevents this sender from sending this message to this recipient (rejected message had interface "org.freedesktop.NetworkManagerInfo" member "getNetworks" error name "(unset)" destination "org.freedesktop.NetworkManagerInfo").
Anyone know a workaround? I disabled selinux and it works fine.
thanks, Brian
Updating policy and restarting messagebus should clear this up.