Hi All, In both Leap & Tumbleweed we currently have the following logic for choosing which tool manages your network after installation "IF laptop AND NetworkManager is being installed THEN use NetworkManager, ELSE wicked" I've noticed an increasing trend that this can lead to confusion. Many users from other distributions expect NetworkManager on their desktops regardless of whether they are using a laptop or a desktop. GNOME expects NetworkManager by default and shows a rather unpleasant error when loading up the settings screen without it.[1] There are certainly classes of hardware where NetworkManager might be wanted that will never match "IF laptop" - eg. my personal Inter Compute Stick. And "IF laptop" is dependant on YaST correctly detecting you're using a laptop, which isn't 100% accurate, so occasionally even laptops might end up with wicked unexpectedly. I would like to propose a possible solution. It looks like we should be able to pin the choice of network tool to specific system role. I would like to propose that the installation options KDE and GNOME therefore always have NetworkManager by default Server & Transactional will always have wicked by default Custom will keep the current "autodetect" behaviour, because we cant be sure that the environment that the user is installing has support for NetworkManager in this case. Whatever is setup "by default" during installation will be able to be changed in YAST after the installation, just like it is today. What do we all think? If there is strong support for this idea I think Ludwig is prepared to let me try and slip it in as a late feature for Leap 15, so please let your opinions be heard loudly and quickly either way. Regards, Richard [1] http://paste.opensuse.org/33301696 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org