Hi,
On Tue, 2013-01-15 at 16:25 +0100, Daniel Wagner wrote:
Seems to help. Not sure if there is still a bug hidden. Following
steps
lead to a non-autoconnect behavior.
...
- disconnect ethernet
When you do a disconnect via D-Bus, this action will be remembered as
long as the
Hi,
Same patch as before but splitted.
Tomasz Bursztyka (2):
network: Move up code about set_connected() and set_disconnected
network: Do not report any error when removing a connecting network
src/network.c | 1255 +
1 file changed,
Useful for next patch
---
src/network.c | 1252 +
1 file changed, 627 insertions(+), 625 deletions(-)
diff --git a/src/network.c b/src/network.c
index 0e64c35..ac4608b 100644
--- a/src/network.c
+++ b/src/network.c
@@ -122,6 +122,633 @@
When connecting a network, if it's related technology is disabled, this network
will raise an error through the agent. Leading to a possible retry request from
the user, then to a crash if the user does so.
Thus, we prevent any error to be raised in such situation and silently
disconnect
the
On Tue, 2013-01-15 at 16:11 +0200, Jukka Rissanen wrote:
Disabling IPv6 in lower up causes problems in IPv6 connectivity.
The interface IPv6 status can stay in disabled state because of
races. So this patch reverts the commit 4ce90440a70abce7de53
and lets service IPv6 state go to READY
On Tue, 2013-01-15 at 16:47 +0200, Jukka Rissanen wrote:
---
src/service.c | 3 +++
1 file changed, 3 insertions(+)
Applied, thanks!
Patrik
___
connman mailing list
connman@connman.net
http://lists.connman.net/listinfo/connman
On Wed, 2013-01-16 at 12:57 +0200, Tomasz Bursztyka wrote:
Hi,
Same patch as before but splitted.
Tomasz Bursztyka (2):
network: Move up code about set_connected() and set_disconnected
network: Do not report any error when removing a connecting network
Both patches applied, thanks1
