On Tue, 2007-01-23 at 20:55 +1300, Simon Geard wrote:
> Trying to get the current NM code to work on my LFS system, with some
> custom code to support LFS. I've hit a couple of bugs which I've logged
> in Bugzilla.
> 
> http://bugzilla.gnome.org/show_bug.cgi?id=394956
> 
> http://bugzilla.gnome.org/show_bug.cgi?id=399292
> 
> The first, 393956, I've included a patch for - I'd appreciate it if
> someone could review the change and commit it.
> 
> 
> The second I'm trying to investigate, and wondering if someone can offer
> some advice on where to look. Basically, nm-applet fails shortly after
> startup, killed due to libdbus asserting against an invalid parameter.
> 
> The D-Bus call in question is getProperties on the interface
> org.freedesktop.NetworkManager.Devices. Monitoring D-Bus, I see three
> calls to this method, using the following paths:
> 
> /org/freedesktop/NetworkManager/Devices/ath0/Networks/foo
> /org/freedesktop/NetworkManager/Devices/ath0/Networks/bar
> /org/freedesktop/NetworkManager/Devices/ath0/Networks/
> 
> The first two appear to be fine, but the third causes the assertion
> failure, presumably because it's calling without an essid appended.

This is the applet, right?

Take a look at gnome/applet/applet-dbus-devices.c,
nma_dbus_device_properties_cb().  The code looks like this:

        /* Call the "getProperties" method on each wireless network the device 
may have. */
        if (num_networks > 0) {
                char ** item;
                for (item = networks; *item; item++)
                        nma_dbus_device_update_one_network (applet, op, *item, 
active_network_path);
        }

you might try printing out what NM returns in the network list (ie,
print the value of "*item" inside the for loop), or using 'nm-tool' to
see what NM reports.  Or

dbus-send --system --dest=org.freedesktop.NetworkManager \
     --print-reply /org/freedesktop/NetworkManager/Devices/ath0 \
     org.freedesktop.NetworkManager.Devices.getProperties

See if any of the network object paths look funny.

Dan

> Can someone suggest where these path strings are being created, and
> where the essid is supposed to come from?
> 
> Simon.
> _______________________________________________
> NetworkManager-list mailing list
> [email protected]
> http://mail.gnome.org/mailman/listinfo/networkmanager-list

_______________________________________________
NetworkManager-list mailing list
[email protected]
http://mail.gnome.org/mailman/listinfo/networkmanager-list

Reply via email to