Description of problem: Gnome DE. when attempting to set up wifi through *settings menu*, the *oops, something has gone wrong.please contact your software vendor. NetworkManager needs to be running* message is displayed. I then chose to connect via drakroam. Version-Release number of selected component (if applicable): Mageia-9-alpha1-i586.iso DATE.txt: Sat Oct 22 09:09:13 PM CEST 2022 How reproducible: Steps to Reproduce: 1.install Gnome only DE from above .iso. do not set up wifi at configuration page. 2.login and then attempt to connect via *settings* 3.
Summary: network manager not running at login => oops: network manager not running at login
I think our NM package is set not start automatically (it's not enabled under systemd) because we didn't want it running under KDE. Do a "systemctl status NetworkManager" to see. If it's not enabled, then "systemctl enable NetworkManager" and "systemctl start NetworkManager".
CC: (none) => ftg
(In reply to Frank Griffin from comment #1) > I think our NM package is set not start automatically (it's not enabled > under systemd) because we didn't want it running under KDE. Do a "systemctl > status NetworkManager" to see. If it's not enabled, then "systemctl enable > NetworkManager" and "systemctl start NetworkManager". thanks for that info. should network manager be enabled for a Gnome only DE install?
(In reply to Ben McMonagle from comment #2) > (In reply to Frank Griffin from comment #1) > > I think our NM package is set not start automatically (it's not enabled > > under systemd) because we didn't want it running under KDE. Do a "systemctl > > status NetworkManager" to see. If it's not enabled, then "systemctl enable > > NetworkManager" and "systemctl start NetworkManager". > > thanks for that info. > > should network manager be enabled for a Gnome only DE install? we do on live medias, but not on CI installs. the problem is that no-one has worked on drakx tools to properly integrate NetworkManager support, so it's a bit stuck in limbo ...
What is the status of NM versus drakx ? I thought that the ifcfg-rh plugin (which our NM enables) was supposed to tell NM to keep its hands off of any interface for which an /etc/sysconfig/network-scripts/ifcfg* file existed ? In any case, I've been running for years with ifcfg-rh disabled and the drakx interface(s) removed on a variety of laptops with a variety of wifi hardware with no problems. Is anyone still having problems with NM and just the keyfile plugin enabled ?
Network manager does not support bridged networks which are required for things like xen.
CC: (none) => davidwhodgins
(In reply to Thomas Backlund from comment #3) > (In reply to Ben McMonagle from comment #2) > > should network manager be enabled for a Gnome only DE install? > we do on live medias, but not on CI installs. Could we also do this with the Classic Installer where at the desktop choice screen, the user choses the 'Gnome' option? (In reply to Frank Griffin from comment #4) > What is the status of NM versus drakx ? [tmb] "the problem is that no-one has worked on drakx tools to properly integrate NetworkManager support, so it's a bit stuck in limbo" This has been a thorn for years, with the unhappy consequence that our desktops with task bars always show a NM icon saying misleadingly "Networking disabled" as well as the functional netwok icon (Ethernet or WiFi). Apparently getting rid of this icon where it is not needed (mostly?) is not easy.
CC: (none) => lewyssmith
(In reply to Dave Hodgins from comment #5) > Network manager does not support bridged networks which are required for > things like xen. Is this still valid as other distributions support bridged connections with nm-connection-Editor? See as example the description from Red Hat: https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/networking_guide/sec-configure_network_bridging_using_a_gui
Thanks for the correction. It now does have bridge support.
Can we convert this into an enhancement request: Classic Installer, if at the desktop choice screen the user choses the GNOME option, Network Manager gets enabled as per the Live installers? And the point looks good for Release Notes, if someone can propose a technically correct text.
Keywords: (none) => FOR_RELEASENOTES9
CC: (none) => bequimao.de
(In reply to Thomas Backlund from comment #3) > the problem is that no-one has worked on drakx tools to properly integrate > NetworkManager support, so it's a bit stuck in limbo ... Actually Jani fixed the main problems before Mageia 8 was released, and AFAICT the drakx tools coexist quite happily with NM on the Live ISOs. (In reply to Frank Griffin from comment #1) > I think our NM package is set not start automatically (it's not enabled > under systemd) because we didn't want it running under KDE. Do a "systemctl > status NetworkManager" to see. If it's not enabled, then "systemctl enable > NetworkManager" and "systemctl start NetworkManager". You should also stop and disable the "network" service. See https://wiki.mageia.org/en/Switching_to_networkmanager (In reply to Frank Griffin from comment #4) > What is the status of NM versus drakx ? I thought that the ifcfg-rh plugin > (which our NM enables) was supposed to tell NM to keep its hands off of any > interface for which an /etc/sysconfig/network-scripts/ifcfg* file existed ? No, it tells NM to store and use the configuration in the ifcfg* files. That's why you can still use the drakx tools to configure the network connections when using NM in place of the legacy network service. Note that when using the legacy network service, you find this message in the system logs: network[824]: You are using 'network' service provided by 'network-scripts', which are now deprecated. network[738]: WARN : [network] 'network-scripts' will be removed from distribution in near future. network[827]: 'network-scripts' will be removed from distribution in near future. network[738]: WARN : [network] It is advised to switch to 'NetworkManager' instead for network management. network[830]: It is advised to switch to 'NetworkManager' instead for network management. The Plasma Live was the last live ISO to still be using the legacy network service, and I have switched it over to NM for Mageia 9.
CC: (none) => mageia
(In reply to Martin Whitaker from comment #10) > The Plasma Live was the last live ISO to still be using the legacy network > service, and I have switched it over to NM for Mageia 9. Does this mean that this bug "network manager not running at login" will be resolved? That - I recall a choice about it during network configuration - if it is ticked, it will be enabled without further ado? Are we about to migrate to NM after years of debate about it? And will this still be true henceforth?: [Frank] > I think our NM package is set not start automatically (it's not enabled > under systemd) because we didn't want it running under KDE. > Do a "systemctl > status NetworkManager" to see. If it's not enabled, then "systemctl enable > NetworkManager" and "systemctl start NetworkManager". And this? [Martin]? > You should also stop and disable the "network" service
Just to be clear, for years I do my cauldron installs specifying all desktops and all package categories. NM is always installed as a result, but I'm not sure whether this is because GNOME is one of the DEs or if it would be there if I just installed Plasma (which is what I mostly use). As part of my installs, I delete ifcfg-rh in NM.conf, enable NM, and use nmtui to activate my interfaces. I also use MCC drakconnect to delete any interface created during install. The result always works perfectly, including when I travel and use other wifi. I'm not sure why I took to using nmtui for initial activation; it was needed at some time in the past, but may not be any more. I have done this with several laptops over the years, and never had a problem. I have also run several VBox VMs, Windows and Linux, using bridged adapters, again with no problems. I see no reason not to make NM the default.
(In reply to Frank Griffin from comment #12) > I see no reason not to make NM the default. Read the thread starting here https://ml.mageia.org/l/arc/dev/2020-07/msg00348.html and continued here https://ml.mageia.org/l/arc/dev/2020-08/msg00002.html (the threading seems to be broken) There are several Mageia devs who are dead against this. Removing the ifcfg-rh plugin would stop the drakx tools working, so there would be even more resistance to that. (In reply to Lewis Smith from comment #11) > Does this mean that this bug "network manager not running at login" will be > resolved? That - I recall a choice about it during network configuration - > if it is ticked, it will be enabled without further ado? > Are we about to migrate to NM after years of debate about it? So I think the answer to both questions is no :-( As things stand, it will only be the Live ISOs (and systems installed using them) that will be using NM by default.
(In reply to Martin Whitaker from comment #13) > (In reply to Frank Griffin from comment #12) > > I see no reason not to make NM the default. > > Read the thread starting here > > https://ml.mageia.org/l/arc/dev/2020-07/msg00348.html > > and continued here > > https://ml.mageia.org/l/arc/dev/2020-08/msg00002.html > > (the threading seems to be broken) > > There are several Mageia devs who are dead against this. > There's a difference between making NM the default and removing drakx-net. drakx-net already has a toggle that enables or disables NM, no ?
Thanks Martin for your further clarification comment 13. Résumé ? > it will only be the Live ISOs (and systems installed using them) > that will be using NM by default > The Plasma Live was the last live ISO to still be using the legacy > network service, and I have switched it over to NM for Mageia 9. All Live ISOs & their installed systems will default to use NetworkManager; which will be running at login. Classic installs will use the Mageia network tools initially at least, but this is not appropriate for a Gnome-only installation. This wiki shows how to migrate TO NetworkManager (already noted by Martin): https://wiki.mageia.org/en/Switching_to_networkmanager But to go the other way FROM NetworkManager? Either we leave the situation as-is, with a Release Note about it. Or we fiddle the Classic installer to recognise a Gnome-only install, and like the Live ISOs, continue to configure NetworkManager. Before assigning this, I would like opinion of this summary. Never having met NM (or needing to), this always perplexes me.
(In reply to Lewis Smith from comment #15) > But to go the other way FROM NetworkManager? > systemctl stop NetworkManager systemctl disable NetworkManager then use drakconnect/MCC to (re)define your interfaces ?
(In reply to Frank Griffin from comment #14) > There's a difference between making NM the default and removing drakx-net. I never suggested otherwise. But those who are resistant to change are also resistant to changing defaults, > drakx-net already has a toggle that enables or disables NM, no ? Not really. It has an option to flag individual network configurations as for use by NM only or for use by the legacy network scripts only, but nothing more.
(In reply to Martin Whitaker from comment #17) > (In reply to Frank Griffin from comment #14) > > drakx-net already has a toggle that enables or disables NM, no ? > Not really. It has an option to flag individual network configurations as > for use by NM only or for use by the legacy network scripts only, but > nothing more. I thought this option allowed, rather than obliged, the connection to be managed by NM; and that you can use both NM & traditional tools. See below. (In reply to Martin Whitaker from comment #10) > (In reply to Thomas Backlund from comment #3) > > the problem is that no-one has worked on drakx tools to properly integrate > > NetworkManager support, so it's a bit stuck in limbo ... > Actually Jani fixed the main problems before Mageia 8 was released, and > AFAICT the drakx tools coexist quite happily with NM on the Live ISOs. If the different tools can co-exist, can they each manage a same connection? Or is the rule that you use either one or the other for any one connection? (I fish for the Release Note). Assigning to MageiaTools, since this seems to be a Classic Installer issue, already fixed or the Live ISOs. If this is wrong, it can be re-assigned within devs.
Assignee: bugsquad => mageiatoolsComponent: RPM Packages => Installer
Status?
CC: (none) => fri
I see its use mentioned on Live is already announced at https://wiki.mageia.org/en/Mageia_9_Release_Notes#Live_ISO What to write in errata for the problems on an installed system? (if anything?)
Keywords: FOR_RELEASENOTES9 => FOR_ERRATA9, IN_RELEASENOTES9