** Description changed: Reproduce: Use the API to change an active connection. What happens: I'm fairly sure we need to re-connect after changing e.g. a user name or a password or a certificate. This means the API consumer is forced to infer from the “activatable” and “active” whether or not the re-connection attempt was successful or not. What should happen: A signal called “activationFailed” would help. Emitting this when trying to establish (going from active = False to active = True) a connection, could be sufficient. + Alternatively: The Connectivity API itself detects the changes and + applies them by re-connecting the connection. + Rationale: Changing routes is something that is very likely to be changed when the connection is active.
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1550283 Title: Connectivity VPN API, hard to change active connection To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1550283/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
