Bugzilla – Bug 220499
NetworkManager doesn't start on beta 2.
Last modified: 2008-05-22 18:18:39 UTC
I installed beta 2 and chose to use NetworkManager. However when I start up the desktop (gnome) I don't see NetworkManager in the notification area, and I also didn't have internet connectivity. I had to revert back to the ifup ifdown method to get my network connection up and running.
Created attachment 105000 [details] network manager log
Joe, from the log it looks like something kills the NetworkManager process as it receives the signal SIGTERM. Is it really starting up the desktop which causes NetworkManager to quit? Can you please check whether you have a connection before logging into X?
After a reboot it started. So it only happened after the initial install.
I'm not sure what I can do here - something sent SIGTERM to NetworkManager, it doesn't look like a NetworkManager problem. We need to figure out what kills it and why.
By Joe's last comment I suspect this is being resolved, once bug #213249 is fixed. The currently used killproc and checkproc replacements are not sufficient. I saw a similar bug on Andreas' system yesterday (it ended up with autoip). Maybe we should also investigate why we're running 'rcnetwork restart' after installation. Andreas? Any idea?
This is AFAIK part of the "Get a clean system after install" where we go from YaST installation to runlevel 5. Jiri might be able to tell you more.
I'm not aware of any changes since 10.1 in this area on the YaST side. AFAIK, the way system is started after installation hasn't changed at all... Sorry, but I cannot help here...
Yeah, looks a lot like a duplicate. Please reopen if it still occurs with RC1. *** This bug has been marked as a duplicate of bug 213249 ***