Bug 633923

Do you happen to get any error in ~/.xsession-errors ?

** (nm-applet:4414): WARNING **: get_all_cb: couldn't retrieve system settings properties: (2) The name org.freedesktop.NetworkManagerSystemSettings was not provided by any .service files.
** (nm-applet:4414): WARNING **: fetch_connections_done: error fetching system connections: (2) The name org.freedesktop.NetworkManagerSystemSettings was not provided by any .service files.

Those are the only ones I could find before the NetworkManager restart.

Ok, some more information. It's not really nm-applet.
NetworkManager is not running after boot for whatever reason.
network is obviously included in the runlevel but no NetworkManager process is running and rcnetwork status shows "unused". I couldn't find a good log entry which would explain that.
This is alsow why rcnetwork restart fixes the issue.

Hrm, I'm not sure why it wouldn't be started on boot. My understanding is that the network service should be started on boot if you're going to runlevel 5 anyway...

Can you maybe take a look at the boot log next time you boot, by disabling the boot splash? Just to see if there's something about network there.

ah, sorry, found that a few days ago. 
NetworkManager is not started at boot time if network-remotefs is disabled.
I'm not sure why and if that makes sense but it's an initscript issue if anything.

When the network script start, the FS_FILTER set to localfs, the script will exit like below shows. when use the network-remotefs, the FS_FILTER was set to remotefs, so the NetworkManager will be started. 

And why should we disable the network-remotefs?


if [ "$NETWORKMANAGER" = yes ] ; then
        if [ "$FS_FILTER" = "localfs" ] ; then
                # NetworkManager is not supported without remotefs
                # and will be started later via network-remotefs.
                case $ACTION in
                        (status) exit 3 ;;
                        (start)  exit 0 ;;
                        (stop)          ;;
                        (*)      exit 6 ;;
                esac

(In reply to comment #6)
> When the network script start, the FS_FILTER set to localfs, the script will
> exit like below shows. when use the network-remotefs, the FS_FILTER was set to
> remotefs, so the NetworkManager will be started. 

I believe it does as it's what I've seen but ...
 
> And why should we disable the network-remotefs?

People tend to adopt their configuration. I usually stop services I don't need and as my system doesn't rely on any "remotefs" I had it disabled.
Is NetworkManager depending on it because it has files below /usr ?

Then I'd like to question why and if really needed is there no other way to detect if NetworkManager can be used (aka /usr) is available w/o hardcoding it into network-remotefs?

(In reply to comment #7)
> (In reply to comment #6)
> 
> > And why should we disable the network-remotefs?
> 
> People tend to adopt their configuration. I usually stop services I don't need
> and as my system doesn't rely on any "remotefs" I had it disabled.
> Is NetworkManager depending on it because it has files below /usr ?
There are a lot of files in it, but not sure if it's the reason that let network-remotefs to start NM.

> Then I'd like to question why and if really needed is there no other way to
> detect if NetworkManager can be used (aka /usr) is available w/o hardcoding it
> into network-remotefs?
Sorry I don't know about also. Let me ask Marius.

Marius,

 Do you have any idea about it?

(In reply to comment #8)
> (In reply to comment #7)
> > (In reply to comment #6)
> > 
> > > And why should we disable the network-remotefs?
> > 
> > People tend to adopt their configuration. I usually stop services I don't need
> > and as my system doesn't rely on any "remotefs" I had it disabled.
> > Is NetworkManager depending on it because it has files below /usr ?
> There are a lot of files in it, but not sure if it's the reason that let
> network-remotefs to start NM.

Exactly.
The network-remotefs starts all parts of the network (either NM or in ifup mode
wireless / ppp networks) that are installed in /usr. It's a mandatory requirement.

> > Then I'd like to question why and if really needed is there no other way to
> > detect if NetworkManager can be used (aka /usr) is available w/o hardcoding it
> > into network-remotefs?

I do not see any way with static LSB init dependencies we currently depend on.

See also bug 463439 comment 10.

*** This bug has been marked as a duplicate of bug 463439 ***