Bugzilla – Bug 806993
System is configured for NetworkManager, but behaves as "ifup"
Last modified: 2013-09-27 07:20:38 UTC
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:19.0) Gecko/20100101 Firefox/19.0 This is for 12.3 RC2. I installed from the 32 bit DVD image (written to a USB). I disabled "automatic configuration" for the install. During the final configuration steps of install, my only changes were to the hostname and domain. The network never came up. According to the configuration, it should have been using NetworkManager. However, NetworkManager was not running. The logs indicated that "dhcpcd" was in use, which should only happen with "ifup". I switched to "ifup". I changed the ethernet to "cable connect". I configured the WiFi. Finally, the network came up. I later switched the settings back to NetworkManager. However, it is clear that it is really running as "ifup" rather than with NetworkManager. This is likely a problem in the final change-over from sysv-init to systemd. I see this as a show stopper. It needs to be fixed before the general release of 12.3 Reproducible: Always Steps to Reproduce: 1. 2. 3.
I installed on another system, this time using KDE. That system is currently configured to use "ifup" but is actually still using "NetworkManager". The people who are building the iso file for the distribution are evidently able to switch between "ifup" and "NetworkManager". But Yast is not making the appropriate change. It is leaving us stuck with what we got from the iso.
This Network Manager issue is a most unwelcome change in RC2. I did fresh default KDE installs of the 32-bit DVD iso for 12.3 Milestone 1, Milestone 2, beta1, RC1, and RC2 on a ThinkPad X-41 using a wired ethernet connection. In the first three cases, networking did not connect during installation, but was OK afterwards. With RC1 and after some router and modem changes, during installation the network connection test succeeded, and the on-line update worked. After installation, NetworkManager was in the tray, and easily set up secure wireless connection to a hidden access point. During the RC2 installation, the network connection test failed, but the subsequent on-line update worked (?!?) After installation finished, NetworkManager had all the troubles others have described elsewhere. ifup did get a wired connection working. I used the procedure in the release notes, section 4.1, to activate NetworkManager. That was not needed in MS1, MS2, beta1, or RC1. What changed between RC1 and RC2 to make such a mess?
Similar issues here. I installed 12.3 RC2 from the DVD image on a USB stick. I chose the XFCE desktop installation. Yast during installation asked for the details of my network (wifi), but the test failed, and the details box was empty. The configuration was that of ifup mode. When I finally booted the system, I could not login as user (xfce). This has an update that corrects it, but I had no network to install it. Had to login as root. YaST network module said that the configuration was handled by network manager, but there was no applet in sight. I switched to ifup mode, and all the data I had entered during config was there. I accepted, then YaST said that it had to install smpppd, and failed because there was no network - of course. This smpppd package should have been installed earlier from the DVD, if it is necesary. It is absurd that to configure network you have to install a package that requires network. Checking, I did have network running, but there was no default route set, so no access to Internet. No matter if I clicked to obtain route from dhcp or manually in YaST, it was ignored. However, a manual restart of "rcnetwork" succeeded and I got Internet. Then, YaST network module also succeeded to install smpppd, and setup default route as well. And the update repaired XFCE access as user, too. Several people are reporting very similar issues in the forum and the mail list. View this thread: <http://forums.opensuse.org/showthread.php?t=483726> IMHO, this issue is a stopper.
Just installed opensuse 12.3 RC2 64 bit and run into the same issue. Workaround described in [1] worked for me. [1]: http://forums.pcpitstop.com/index.php?/topic/201029-networkmanager-opensuse-123-rc2/
I see the same. This is very confusing and absolutely not good to be released. Network manager does not work at all. The only thing I was able to achieve is to get some sort of connectivity in "ifup" mode, even though it screams "These packages need to be installed: smpppd" when I choose it. And by the way, I cannot install that package as obviously there is no network at that time. ------ Another annoyance: when I try switching it to "User Controlled with NetworkManager", I see this message: "Applet needed NetworkManager is controlled by desktop applet ... Be sure it's running and if not, start it manually." This is all fine, but a) new users will have absolutely no idea what this is all about. b) experienced users will know, but they will still be annoyed that the system does not make such basics sorted automatically. Then, after clicking "OK" it does something and at the step "Update configuration" it says: "Error No network running" This is very bad indeed. ------ Then I installed "smpppd". The behaviour changed. While it screamed that no network running, the NetworkManager applet was able to see the WiFi. I chose the hot spot, entered the password. It asked me to set up kwallet. So I did. However, it said that the whole thing failed while the network was actually up (NetworkManger was showing that connection as being up). When I disconnected from the hot spot and tried to re-connect, I was asked for a password to kwallet. Upon entering it it said that the connection failed. This time it has failed for sure. And currently I see to way of fixing it as it does not even allow me to re-enter the password.
duplicate to bug 610322 *** This bug has been marked as a duplicate of bug 610322 ***