Re: Fw: NM stops and doesn't connect

[Dan Williams <dcbw redhat com>]

On Mon, 2009-03-16 at 14:40 +0000, Cliff McDiarmid wrote: 
> ----- Original Message -----
> From: "Cliff McDiarmid" <cliffhanger gardener com>
> To: dcbw redhat com
> Subject: NM stops and doesn't connect
> Date: Sat, 14 Mar 2009 20:34:52 +0000
> 
> > In any case, lets get to the bottom of this by building some debug info
> > into the dbus autolaunch binary.
> 
> Hi Dan
> 
> I've built the dbus source, just waiting for some instruction on 
> altering the dbus autolaunch binary.

Yeah, sorry for the lag...

So looking at the code (while trying to come up with a patch for you to
apply) we actually get information in the return error message of a dbus
call that auto-launches the process.  So, can you do the following with
your existing dbus instance before we start patching stuff?

1) stop the NetworkManager service
2) killall -TERM wpa_supplicant
3) run the following command as root:

dbus-send --system --print-reply --dest=fi.epitest.hostap.WPASupplicant /fi/epitest/hostap/WPASupplicant fi.epitest.hostap.WPASupplicant.getInterface string:eth2

Then reply with the output of that command.  The error message will help
us narrow down the problem a bit further.  It's important that
wpa_supplicant be *stopped* before you run that command.

Dan