Comment # 9 on bug 1038403 from David Diaz

Hi!

> (In reply to Knut Alejandro Anderssen Gonz�lez from comment #7)
> > (In reply to Jonathan Kang from comment #6)
> > > Looks like the systemd preset "conflicts" with Yast. Yast has a set of rules
> > > to
> > > determine which network service to use(desktop environment makes a
> > > defference).
> >
> > It really conflicts with YaST?, I mean, each backend should conflict with
> > each other, that is, both should not be running at the same time.
> >
> 
> A bit explaination about this bug, with systemd presets, NetworkManager is
> enabled all the time. In a tumbleweed with xfce as the desktop environment,
> NetworkManager and wicked are both installed. And when users open yast
> network,
> no dialog pops up saying that network is controlled by NetworkManager.
> 
> I meant the way systemd preset enables NetworkManager conflicts with how yast
> network module choose to enable which service(wicked or NetworkManager). And
> sure, they should conflict with each other. But there should be a central
> place
> to manage this.
> 
> I'm thinking about either
> 1. Not implementing the systemd preset for NetworkManager at all.
> 2. yast network module should disable NetworkManager and start wicked at
> certain
> circumstances, for example in xfce, wicked is preferred as the network
> manager.

As Knut said in comment #7, we at YaST team only can take care about

> show a warning and could ask the user if wanted to disable the service that is not linked to network.service

I linked our Trello card for this purpose.

Thanks!