Seems like network-manager 1.0.4-0ubuntu5.1 fixed this bug. That makes this like duplicate of LP: #1512749
Seems like network-manager 1.0.4-0ubuntu5.1 fixed this bug. That makes this like duplicate of LP: #1512749