Public bug reported:
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.
Rationale:
Changing routes is something that is very likely to be changed when the
connection is active.
** Affects: indicator-network (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to indicator-network in
Ubuntu.
https://bugs.launchpad.net/bugs/1550283
Title:
Connectivity VPN API, hard to change active connection
Status in indicator-network package in Ubuntu:
New
Bug description:
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.
Rationale:
Changing routes is something that is very likely to be changed when the
connection is active.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1550283/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
