[Bug 1185524] Changing to NetworkManager via Yast Network throws an internal error
![](https://seccdn.libravatar.org/avatar/a895f78a81a109471893519443e4d933.jpg?s=120&d=mm&r=g)
https://bugzilla.suse.com/show_bug.cgi?id=1185524 https://bugzilla.suse.com/show_bug.cgi?id=1185524#c5 Knut Alejandro Anderssen Gonz�lez <kanderssen@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |CONFIRMED Flags|needinfo?(kanderssen@suse.c | |om) | --- Comment #5 from Knut Alejandro Anderssen Gonz�lez <kanderssen@suse.com> --- (In reply to Steffen Winterfeldt from comment #4)
Knut, is this a known issue?
It is not a problem with NM but with YaST. Since https://github.com/yast/yast-network/pull/1149, YaST is able to translate the current configuration to NetworkManager. The problem described is a is a problem with the Desktop augeas lens when a '#' is used as a value. We chose the Desktop lens because a problem when writing the config but it seems it has the same problem it was fixed in the NetworkManger lens https://github.com/hercules-team/augeas/commit/bf25803ba4b3aa4e81feefb8fc217... Lets try to move this issue https://github.com/hercules-team/augeas/issues/719 forward -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@suse.com