Re: nm-tool and nm-applet problems in recent svn



On Thu, 2008-05-08 at 13:56 -0400, Dan Williams wrote:
> On Tue, 2008-05-06 at 19:38 +0200, Björn Martensen wrote:
> > Hi,
> > 
> > I had this problem with nm-tool for some time now and it doesn't work in
> > the latest svn of libnm, networkmanager and nm-applet yet:
> 
> Hmm; nm-tool seems to work for me in latest SVN.

it doesn't with the latest here :/

> > 
> > > $ nm-tool 
> > > 
> > > NetworkManager Tool
> > > 
> > > State: connected
> > > 
> > > 
> > > (process:14913): GLib-GObject-WARNING **: invalid uninstantiatable type `(null)' in cast to `NMDevice'
> > > 
> > > ** (process:14913): CRITICAL **: nm_device_get_state: assertion `NM_IS_DEVICE (device)' failed
> > > 
> > > ** (process:14913): CRITICAL **: nm_device_get_iface: assertion `NM_IS_DEVICE (device)' failed
> > > - Device: (null) ----------------------------------------------------------------
> > > 
> > > ** (process:14913): CRITICAL **: nm_device_get_driver: assertion `NM_IS_DEVICE (device)' failed
> > >   Driver:            (unknown)
> > >   Active:            no
> > > 
> > > ** (process:14913): CRITICAL **: nm_device_get_capabilities: assertion `NM_IS_DEVICE (device)' failed
> > > 
> > >   Capabilities:
> > >     Supported:       no
> > > 
> > > 
> > > Segmentation fault
> > 
> > I'm using a thinkpad t60 with iwl3945 and e100e driven devices. both work fine, but nm-tool doesn't seem to like my system.
> 
> Can you try a clean rebuild of NM?  Might be mismatched libnm-glib and
> nm-tool.

i always do svn up and then svn export that tree to a temporary build
directory to create clean packages, so i always have a clean rebuild.

> > since nm-applet svn 711, nm-applet doesn't start anymore. when it starts, bug buddy tells me, the applet has crashed.
> 
> That sounds like the same issue as nm-tool is having.

actually it was solved after a recent nm commit and now the applet works
again. however, nm-tool does not.

> > > $ nm-applet 
> > > 
> > > ** (nm-applet:14850): WARNING **: Could not retrieve dbus connections: Launch helper exited with unknown return code 1.
> > > 6d91daf9-4738-49a8-54b19ba7-45e237df is dumped
> > 
> > the weird part is that it still connects and then crashes right away. has there anything important been
> > changed and conflicts with old settings now in that commit or what's happening? I'm running arch linux and it worked
> > fine with older versions, and i can still connect to all the networks i could before... maybe this helps:
> > 
> > 
> > > ** (nm-applet:15045): WARNING **: Could not retrieve dbus connections: Launch helper exited with unknown return code 1.
> > > 
> > > Program received signal SIGSEGV, Segmentation fault.
> > > [Switching to Thread 0xb728a6c0 (LWP 15045)]
> > > 0xb76abb05 in free () from /lib/libc.so.6
> > > (gdb) bt full
> > > #0  0xb76abb05 in free () from /lib/libc.so.6
> > > No symbol table info available.
> > > #1  0xb78da096 in g_free () from /usr/lib/libglib-2.0.so.0
> > > No symbol table info available.
> > > #2  0xb78aafac in g_ptr_array_free () from /usr/lib/libglib-2.0.so.0
> > > No symbol table info available.
> > > #3  0xb8087422 in fetch_connections_done () from /usr/lib/libnm_glib.so.0
> 
> I think Tambet fixed this yesterday actually.  Can you try with latest
> NM svn?

as stated above, the applet works fine again, thanks :)

björn

Attachment: signature.asc
Description: This is a digitally signed message part



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]