I just upgraded to gutsy and this annoying bug has also bitten me. Fortunately I found a simple workaround somewhere else (can't remember where =( ) that worked for me, and only messes with the real culprit AFAICS: if you disable NetworkManager's "roaming mode" and force "Automatic configuration (DHCP)" autofs starts up just fine when the system boots.
HTH
Andre
PS: to edit NetorkManager's properties, just go to System > Administration > Network, choose "Wired connection" on the "Connections" tab and then click on "Properties".
PPS: of course these instructions assume you use a wired connection.
Hi,
I just upgraded to gutsy and this annoying bug has also bitten me. Fortunately I found a simple workaround somewhere else (can't remember where =( ) that worked for me, and only messes with the real culprit AFAICS: if you disable NetworkManager's "roaming mode" and force "Automatic configuration (DHCP)" autofs starts up just fine when the system boots.
HTH
Andre
PS: to edit NetorkManager's properties, just go to System > Administration > Network, choose "Wired connection" on the "Connections" tab and then click on "Properties".
PPS: of course these instructions assume you use a wired connection.