Bug 635613

Summary: NetworkManager does not start at system boot
Product: [openSUSE] openSUSE 11.3 Reporter: Henning Schnoor <henning.schnoor>
Component: NetworkAssignee: Bin Li <bili>
Status: RESOLVED WONTFIX QA Contact: E-mail List <qa-bugs>
Severity: Normal    
Priority: P5 - None CC: henning.schnoor
Version: Final   
Target Milestone: ---   
Hardware: i686   
OS: openSUSE 11.3   
Whiteboard:
Found By: --- Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---

Description Henning Schnoor 2010-08-30 18:33:03 UTC
User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.8) Gecko/20100723 SUSE/3.6.8-1.3 Firefox/3.6.8

After booting, NetworkManager is not running (no connections available, ps -A does not find the process). When I execute "service network restart," NetworkManager starts and establishes the connection.





Reproducible: Always

Steps to Reproduce:
1. Start system
2. try to access network
3. use ps -A | grep Man
Actual Results:  
No network, no process showing

Expected Results:  
Network connectivity, process running

NetworkManager does not show up in /var/log/boot.msg
Comment 1 Henning Schnoor 2010-08-30 18:44:08 UTC
Some additional comments:

- this happens on a lenovo Thinkpad with wired network plugged in
- happens after reboot, didn't try suspend mode, so this is probably different from similar bugs.

Let me know if I can provide any additional details.
Comment 2 Bin Li 2010-08-31 03:01:59 UTC
Take care of it.
Comment 3 Bin Li 2010-08-31 03:17:01 UTC
First do you use the 'NetworkManager' not 'ifup' management in the YaST?
Although without the NM running, does the network works fine? Just try to ping some public URL, such as www.google.com.
Comment 4 Henning Schnoor 2010-08-31 07:22:55 UTC
Yes, YaST ist configured to use NetworkManager.

After boot, there is no network connectivity, ping gives "unknown host".
Comment 5 Henning Schnoor 2010-09-09 05:25:10 UTC
I now found the cause of the problem: When booting, nfs services are started before NetworkManager. So when I log into KDE while nfs is trying to connect, NetworkManager is not started yet, since nfs is trying to find the connection (which it can't without NM). 

So the problem is that by default, nfs is started before NM; it should be the other way round since NM needs network connectivity to work.

Took me so long to find this since I can't see the output of the text console due to some issue with the graphics driver.
Comment 6 Bin Li 2012-11-16 05:59:25 UTC
11.3 is dead. I will close... please open
a new bug if it happens against 12.2 (current stable)