by havoc

the whole thing you’re doing
(figuring out what to start) is not intended to exist – the norm would
be that the daemon starts automatically in the init script, and GNOME
autostarts the tray icon. But I believe the RPM doesn’t autostart stuff yet
because it’s all beta/experimental/dorks-only and it breaks on certain
kernel modules or wireless cards.

It’s not a complicated architecture. NM daemon controls the
kernel, and the UI for it is a GNOME tray icon or applet. You start
the two halves. At least as of the previous network manager, this is
what you had to launch:

$ su -
# service NetworkManager start
# exit
$ /usr/libexec/nm-applet &
$ bg; disown

In an on-by-default NM the init.d script would be in runlevels 3/5 and
nm-applet would be in the GNOME session, nothing to do manually.

Your log error looks like either dbus isn’t reloading the security config
post-install of NM, or NM daemon simply isn’t running.

That said, NM doesn’t work for me either, but it’s the fault of the
kernel drivers. The airo module with whatever version of the firmware
I have gets into a wedged state where it just prints debug spam over
and over and doesn’t work. Whatever race condition or sequence of
syscalls causes the wedging doesn’t happen often when just doing “ifup” and
“ifdown” rather than NetworkManager’s scanning etc. I have triggered
it from the command line before though usually in a “trying to find a
network” case where I’m running iwlist and bringing things up and down
much as NM would do.

Dan kindly documented

kernel problems discovered
in the course of hacking on NetworkManager.

(This post was originally found at

My Twitter account is @havocp.
Interested in becoming a better software developer? Sign up for my email list and I'll let you know when I write something new.