On Sat, 2009-03-21 at 13:34 +0000, Cliff McDiarmid wrote: > > ----- Original Message ----- > > From: "Cliff McDiarmid" <[email protected]> > > > > ----- Original Message ----- > > > From: "Dan Williams" <[email protected]> > > > To: "Cliff McDiarmid" <[email protected]> > > > Cc: [email protected] > > > Subject: Re: Fw: NM stops and doesn't connect > > > Date: Mon, 16 Mar 2009 17:42:33 -0400 > > > > > > > > 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. > > > > > > The output is: Error org.freedesktop.DBus.Error.ServiceUnknown: The > > name fi..epitest.hostap.WPASupplicant was not provided by any > > ..service files > > > > This is not very informative me thinks, file definitely exists > > > > ls -all /usr/share/dbus-1/system-services: > > > > drw-rw-rw- 2 root root 4096 2009-03-16 22:43 . > > drwxr-xr-x 5 root root 4096 2009-01-03 23:04 .. > > -rw-r--r-- 1 root root 155 2009-03-03 15:51 > > fi.epitest.hostap.WPASupplicant.service > > -rw-r--r-- 1 root root 164 2008-10-28 03:47 > > org.freedesktop.NetworkManagerSystemSettings.service > > -rw-r--r-- 1 root root 101 2008-10-28 03:47 > > org.freedesktop.nm_dispatcher.service > > -rw-r--r-- 1 root root 258 2009-03-01 22:28 > > org.freedesktop.PolicyKit.service > > I assume you can't help me any further Dan, I quite understand
Ran into the autolaunch problem the other day with somebody else and debugged that issue. It turned out to be a permissions problem with the dbus launch helper. dbus-daemon-launch-helper needed to have the following permissions: -rwsr-x--- 1 root dbus where of course "dbus" should be the group that is set in /etc/dbus-1/system.conf in the <user>xxxxx</user> setting. can you confirm what permissions your dbus-daemon-launch-helper binary has? Mine is in /lib/dbus-1, but it's also been found in /usr/lib/dbus-1 on other distros. Dan _______________________________________________ NetworkManager-list mailing list [email protected] http://mail.gnome.org/mailman/listinfo/networkmanager-list
