I would like to confirm that this is now resolved with the newest version of network-manager (1.4.2-1). You can close this bug.