On Wed, 2008-04-09 at 11:28 +0800, alex z wrote:
>
> nm_dhcp_manager_handle_event() never gets called, or is it not
> getting
> down to handle_options?
>
> nm_dhcp_manager_handle_event() never gets called.
> But, the same code works on my mips device. So, I think it's not
> nm_dhcp_manager_handle_event() never gets called, or is it not getting
> down to handle_options?
nm_dhcp_manager_handle_event() never gets called.
But, the same code works on my mips device. So, I think it's not a NM's bug,
maybe DBUS's in ubuntu 7.10. :)
Alex
_
debugged, I found that the reason is nm-dhcp-manager.c cannot
> receive the dbus signal 'Event' from nm-dhcp-client-action.c.
> nm_dhcp_manager_handle_event() never be called, so it will be timeout
> after 45s.
>
> I use the command to monitor dbus-bus:
Why not parse /var/run/dhclient-*.lease to find the dhclient result insteal
of getting it from DBUS? :)
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list
Hi All,
I meet the same issue with this thread:
http://mail.gnome.org/archives/networkmanager-list/2007-November/msg00119.html
my environment is:
NM-0.7-svn rev 3507, ubuntu 7.10, dbus 1.1.1
After I debugged, I found that the reason is nm-dhcp-manager.c cannot
receive the dbus signal '
