Bugzilla – Bug 726823
No NetworkManager on first boot of installed system
Last modified: 2021-03-09 12:11:15 UTC
User-Agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); en-US; rv:184.108.40.206) Gecko/20100611 SUSE/3.6.4-6.1 Firefox/3.6.4
In 12.1 RC1, KNetworkManager does not work at all. There is no icon on the bar for it. It does run on the Live CD. However, even with the Live CD, it doesn't work with WiFi.
This is on a ThinkPad E520 type 1143-3BU
Steps to Reproduce:
No KNetworkManager on bar
Are you referring to KNetworkManager (no longer used) or the plasmoid-networkmanagement applet?
Assuming the latter, does "12.1 RC1" mean an installed system from the DVD image or from the Live CD?
When I was referring to plasmoid-networkmanagement on the install. However, since resolving the problem with getting WiFi to work, the network manager also works.
Created attachment 459242 [details]
See NM shutdown at 22:25. what could have killed it?
NetworkManager is enabled in sysconfig
Will, I don't understand your attachment and the comments - and how they are related to the bugreport.
Please add some more comments and then assign it to the proper person, please.
A comment got lost due to a midair collision.
In my installed systems NetworkManager is not running after the first boot. The log shows that it started but closed itself down on request.
Last tested with openSUSE-DVD-x86_64-Build0005-Media.iso from dist
I had seen that issue a while ago, but I can't reproduce this with my live image of rc1.
Is this after installation, or even on the live image? Any idea what happened at the time when it closed itself on request?
This has come up since RC1. Same happens with ifup networking - the network is stopped after yast phase2. Coolo and Bernard are looking into it.
On second boot of Build0010 (regular reboot after installation has completed), NetworkManager is running but neither NetworkManager nor ip/ifconfig etc see any network interfaces.
it stopped seconds after yast finished 2nd stage configuration. This looks like a systemd problem really. NM is asked to stop - assigning to the Navigator as default blame target :)
Vuntz, this is a DVD problem as it's related to the 2nd stage of Yast. I'm 99% sure of that.
/usr/lib/YaST2/startup/Second-Stage/09-cleanup is the one calling rcnetwork stop
Yast 2nd stage assumes it has setup the network and wants to shut down network itself.
I would say YaST2-Second-Stage.service needs to be Before=network.target
*** Bug 726435 has been marked as a duplicate of this bug. ***
If it was only rcnetwork stop, why is the kernel not reporting any network interfaces to the command line tools? I'd expect them to be there, but down. Does yast 2nd stage do something to make udev locate network interfaces in the final installed system?
AFAIK, yast2 second stage is supposed to be started before network is up (this is how I'm reading /etc/init.d/boot ), so YaST2 second stage .service is following the same dependencies.
Ohh, I misread.. Indeed, there is nothing preventing systemd to start network before YaST2.
but adding Before=network.target wouldn't prevent network to be started.
if we want to ensure both NM and network initscript aren't started before YaST2 Second stage, we need :
Before=network.service NetworkManager.service in YaST2 second stage .service
*** Bug 724151 has been marked as a duplicate of this bug. ***
Ignore comment #16, this was due to a botched install.
On first boot of Build0010 I see this:
linux-zow9:~ # rcnetwork status
network.service - LSB: Configure the localfs depending network interfaces
Loaded: loaded (/etc/init.d/network)
Active: inactive (dead) since Wed, 02 Nov 2011 14:07:54 +0100; 1min 23s ago
Process: 4802 ExecStop=/etc/init.d/network stop (code=exited, status=0/SUCCESS)
fix committed in yast svn,
please release a new yast-installation package
*** Bug 726003 has been marked as a duplicate of this bug. ***
Jiri, can you submit this to Factory?
I tested openSUSE 12.1-RC2 on my notebook but the problem still exists, at least for non-dhcp network settings. The network cable was connected to the laptop.
The install went as expected but during the 1st manual system configuration I set up the networkcard configuration (I suppose via Yast) with the required ip-addresses, but the network failed during test in getting updated releasenote.
After logging in the system the was no network icon in the taskbar while Yast/network devices/network settings say that the network was at that moment controlled via networkmanager. There was no connection to the network in Firefox.
After logging out and in again the taskbar showed the network icon and I had to setup the wired network again, no data from earlier entered (1st manual system configuration) was available. After the setup wired network functioned normally.
I've submitted yast2-installation with the changes from Frederic (thanks!), it's yast2-installation-2.21.28. So before you reopen next time, check your version first.
(I'm sick, that's why I have not seen it earlier)
This is an autogenerated message for OBS integration:
This bug (726823) was mentioned in
https://build.opensuse.org/request/show/90211 Factory / yast2-installation
*** Bug 728557 has been marked as a duplicate of this bug. ***
*** Bug 728849 has been marked as a duplicate of this bug. ***
*** Bug 728327 has been marked as a duplicate of this bug. ***
Well, this hit the released version, or at least Bug 726003 did. I did a network install (media free method) and after the install, the network was not enabled. rcnetwork restart or going through yast network settings didn't change a thing. A reboot solved it.
BTW, it is not obvious KNetworkManager is not used anymore as yast is still referring to it.
*** Bug 728381 has been marked as a duplicate of this bug. ***
I am running into this problem with the final DVD. I did a clean install in a VM and need to use the network manager for VPN access. I am running KDE and I do not see the network manager. In the KDE control panel (kcm) the icon is showing a blank page with a question mark on it (i.e. icon missing). I am able to set up the VPN settings there.
However, no icon appears in the bar at the bottom of the screen. When I get a list of widgets to add I see Network Management with the same missing icon. If I drag it to the bar it does not show up.
I have installed all the latest updates.
I might add that I used Yast to configure the network to use the network management and have double checked in /etc/sysconfig/network/config that this is the case.
The original fix was from Frederic, therefor reassigning.
However, comment 32 does not imply at all that it might be related to YaST. Does your problem happen really only right after installation or also after next reboots?
No, the problem happens all the time. The only way I can get the network manager to display is to issue the command:
plasmoidviewer org.kde.networkmanagement on the command line.
Note that I did a clean install and installed all the updates and still see the same problem.
(In reply to comment #35)
> No, the problem happens all the time.
So, please open a different bug report and do not reopen this one which is related to YaST.
New bug filed.
let's close this bug, then.