What | Removed | Added |
---|---|---|
Status | NEW | RESOLVED |
Resolution | --- | DUPLICATE |
Flags | needinfo?(jreidinger@suse.com) |
It is caused by change in yast2-network. I see that in logs is yast2-network-4.5.15 and fixed version is 4.5.16. See changelog entry https://github.com/yast/yast-network/blob/master/package/yast2-network.changes#L4 So already fixed and just waiting to be in the latest leap. *** This bug has been marked as a duplicate of bug 1207968 ***