Description of problem: On boot up ( with the bootup text showing since I removed the splashscreen) the system hangs up waiting for network.service and network-up.service. I notice that just before this Network Manager is started (is this now the default instead of the Network Center), although what comes up once Plasma comes up is NetworkApplet and network enter. Is this a battle between Netowrk Manager and Network Center? Version-Release number of selected component (if applicable): Up to date Mga9. How reproducible: Always. Steps to Reproduce: 1.Boot up 2.Wait 3.
Use one or the other, not both. https://wiki.mageia.org/en/Switching_to_networkmanager It is recommended to switch to networkmanager. Closing as invalid as this is up to you as your own system admin to choose which to use.
Status: NEW => RESOLVEDCC: (none) => davidwhodginsResolution: (none) => INVALID
*** Bug 33141 has been marked as a duplicate of this bug. ***
*** Bug 33142 has been marked as a duplicate of this bug. ***
Created attachment 14514 [details] journalctl reports while my cmputer booot was hung up These are outputs in journalctl -b while waiting to connect. What in the world are all those oceth-s# entries, or the radeth-c# enetries that Network Manager keeps trying to connect to. Where did they come from and what are they? Aha-- there are about 300 entries in /etc/sysconfig/network-scripts of the form ifcfg-oceth-* and ifcfg-radeth-* all of which have contents of the form DEVICE=oceth-s154282 BOOTPROTO=dhcp ONBOOT=yes All with dates either Mar 31 or Jan 14 this year What could have caused this? Was this some sort of attack attempt? Or more likely is it a bug in Mageia?
I did nothing to the system, it seems to have installed NetworkManager on its own. And the huger bunch of ifcfg entries in /etc/sysconfig/network-scripts is certainly NOT a local setup problem. Something was dumping all those script, each of which was a "boot script" telling it to install at boot. I have no idea where I was on Mar 31 or Jan 14 that could have caused this. Ie, Network Manager seems to have gone crazy, which is surely a bug.
Status: RESOLVED => REOPENEDResolution: INVALID => (none)
Your truncated log shows that you have explicitely set your network interface as unmanaged. That means, as already mentioned by Dave, administrator failure…
No, I certainly did not set the system to unmanaged. If it says unmanged then something in the system did it. What happened was that something, certainly not me, put in about 100 ifcfg-????? into /etc/sysconfig/network-scripts, and the machine was going throgh all of them trying to connect with each. Removal of them, and things returned to normal No idea what did it but I suspect Network Manager. Things are working again.
Without knowing at all how all those ifcfg entries in /etc/sysconfig/network-scripts got there, it is clear that they were the root of the problem, and Bill has sorted himself out by removing them.
Status: REOPENED => RESOLVEDResolution: (none) => WORKSFORME