Comment 3 for bug 705435

Lee Hyde <email address hidden> writes:

> Greetings *Kalle*

Hi Lee,

> 1. I am *not* using DHCP (it is disabled on my router), I have manually
> set all IP addresses.

Ah, this is the key. I use dhcp myself and that's why I had missed this.

This can be reproduced at least like this:

1. configure a wired connection to use manual ip
2. suspend
3. resume
4. connmand now crashes
5. restart connmand (normally happens automatically)
6. the wired connection doesn't have gateway anymore

I was able to reproduce with current upstream git and I'll report this
forward to the connman project.

The stacktrace:

#0 0x000000000079e5bb in ?? ()
#1 0x000000000041cfba in method_call_reply (call=0x6f0a00,
    user_data=<value optimized out>) at gsupplicant/dbus.c:386
#2 0x00007ffff78c553a in complete_pending_call_and_unlock (
    connection=0x674620, pending=0x6f0a00, message=<value optimized out>)
    at dbus-connection.c:2311
#3 0x00007ffff78c81af in dbus_connection_dispatch (connection=0x674620)
    at dbus-connection.c:4596
#4 0x000000000040cd08 in message_dispatch (data=<value optimized out>)
    at gdbus/mainloop.c:80
#5 0x00007ffff7b3ab1b in g_timeout_dispatch (source=0x754200,
    callback=0x7fffffffe1d0, user_data=0x7ffff6e69298)
    at /build/buildd/glib2.0-2.26.0/glib/gmain.c:3585
#6 0x00007ffff7b3a342 in g_main_dispatch (context=0x673120)
    at /build/buildd/glib2.0-2.26.0/glib/gmain.c:2149
#7 g_main_context_dispatch (context=0x673120)
    at /build/buildd/glib2.0-2.26.0/glib/gmain.c:2702
#8 0x00007ffff7b3e2a8 in g_main_context_iterate (context=0x673120,
    block=<value optimized out>, dispatch=<value optimized out>,
    self=<value optimized out>)
    at /build/buildd/glib2.0-2.26.0/glib/gmain.c:2780
#9 0x00007ffff7b3e7b5 in g_main_loop_run (loop=0x6722e0)
    at /build/buildd/glib2.0-2.26.0/glib/gmain.c:2988

ipv4 configuration in step 6:

  IPv4 = { Netmask=255.255.255.0 Method=manual Address=192.168.1.232 }
  IPv4.Configuration = { Netmask=255.255.255.0 Method=manual Address=192.168.1.232 }

> (Does connman even support IPv6 yet?)

It does, but the support in indicator-network is not yet implemented. It
will be implemented soon.

See bug #686354 and bug #686356 for more.

> 4. I can't really say for sure, but I would estimate that the issue
> reared its head approximately 1-2 weeks ago (~10th Jan. 2010). I wish I
> had taken notes when I first noticed the issue, but alas I am a fool!

That's good to know. In case we need to start bisecting the patch which
broke this it's good to know when this started happening. Saves our time :)

> I hope that is of some assistance too your good self (although I doubt
> it). If there's anything else I can do, please do let me know.

This is more than enough and we can start working on the bug now.

Lee, thank you very much for reporting the issue.

--
Kalle Valo