Re: NM stops and doesn't connect
On Sat, 2009-03-21 at 13:34 +, Cliff McDiarmid wrote: > > - Original Message - > > From: "Cliff McDiarmid" > > > > - Original Message - > > > From: "Dan Williams" > > > To: "Cliff McDiarmid" > > > Cc: networkmanager-list@gnome.org > > > 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 x 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 NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: NM stops and doesn't connect
On Sat, 2009-03-21 at 13:34 +, Cliff McDiarmid wrote: > > - Original Message - > > From: "Cliff McDiarmid" > > > > - Original Message - > > > From: "Dan Williams" > > > To: "Cliff McDiarmid" > > > Cc: networkmanager-list@gnome.org > > > 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 Not necessarily, but the code for reading the activation files is somewhat obfuscated. I can try to come up with a patch. My first thought was "misconfigured prefix", but your configure dump from earlier showed the correct prefix of /usr. Basically, it looks like dbus-daemon itself isn't correctly seeing the wpa_supplicant service's system bus activation file. Dan ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: NM stops and doesn't connect
> - Original Message - > From: "Cliff McDiarmid" > > - Original Message - > > From: "Dan Williams" > > To: "Cliff McDiarmid" > > Cc: networkmanager-list@gnome.org > > 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 thanks MAC -- Be Yourself @ mail.com! Choose From 200+ Email Addresses Get a Free Account at www.mail.com ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: NM stops and doesn't connect
> - Original Message - > From: "Dan Williams" > To: "Cliff McDiarmid" > Cc: networkmanager-list@gnome.org > 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 MAC -- Be Yourself @ mail.com! Choose From 200+ Email Addresses Get a Free Account at www.mail.com ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Fw: NM stops and doesn't connect
On Mon, 2009-03-16 at 14:40 +, Cliff McDiarmid wrote: > - Original Message - > From: "Cliff McDiarmid" > To: d...@redhat.com > Subject: NM stops and doesn't connect > Date: Sat, 14 Mar 2009 20:34:52 + > > > 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 ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Fw: NM stops and doesn't connect
- Original Message - From: "Cliff McDiarmid" To: d...@redhat.com Subject: NM stops and doesn't connect Date: Sat, 14 Mar 2009 20:34:52 + > 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. thanks MAC -- Be Yourself @ mail.com! Choose From 200+ Email Addresses Get a Free Account at www.mail.com --- Begin Message --- > 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. thanks MAC -- Be Yourself @ mail.com! Choose From 200+ Email Addresses Get a Free Account at www.mail.com --- End Message --- ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
NM stops and doesn't connect
> - Original Message -
> From: "Dan Williams"
> To: "Cliff McDiarmid"
> Cc: networkmanager-list@gnome.org
> Subject: Re: NM stops and doesn't connect
> Date: Thu, 12 Mar 2009 10:08:21 -0400
> In any case, lets get to the bottom of this by building some debug info
> into the dbus autolaunch binary.
> Dan
Right, that's kind Dan thanks for the help. Anyway I've built the
source package like so:
D-Bus 1.2.12
==
prefix: /usr
exec_prefix: ${prefix}
libdir: /usr/lib
libexecdir: /usr/libexec
bindir: /usr/bin
sysconfdir: /etc
localstatedir:/var
datadir: /usr/share
source code location: .
compiler: gcc
cflags: -ffunction-sections -fdata-sections -g -O2
-Wall -Wchar-subscripts -Wmissing-declarations -Wmissing-prototypes
-Wnested-externs -Wpointer-arith -Wcast-align -Wdeclaration-after-statement
-fno-common -Wno-unused -Wno-sign-compare -Wno-pointer-sign -Wno-format
-fno-strict-aliasing
cppflags:
cxxflags: -g -O2
64-bit int: long long
32-bit int: int
16-bit int: short
Doxygen: no
xmlto:/usr/bin/xmlto
Maintainer mode: no
gcc coverage profiling: no
Building unit tests: no
Building verbose mode:no
Building assertions: no
Building checks: yes
Building SELinux support: no
Building inotify support: yes
Building dnotify support: no
Building kqueue support: no
Building X11 code:yes
Building Doxygen docs:no
Building XML docs:yes
Building cache support: yes
Gettext libs (empty OK):
Using XML parser:
Init scripts style: none
Abstract socket names:yes
System bus socket:/var/run/dbus/system_bus_socket
System bus address: unix:path=/var/run/dbus/system_bus_socket
System bus PID file: /var/run/dbus/pid
Session bus socket dir: /tmp
Console auth dir: /var/run/console/
Console owner file: no
Console owner file path:
System bus user: cliffys
Session bus services dir: /usr/share/dbus-1/services
'make check' socket dir: /tmp
MAC
--
Be Yourself @ mail.com!
Choose From 200+ Email Addresses
Get a Free Account at www.mail.com
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: NM stops and doesn't connect
On Wed, 2009-03-11 at 20:17 +, Cliff McDiarmid wrote: > > - Original Message - > > From: "Dan Williams" > > To: "Cliff McDiarmid" > > Cc: networkmanager-list@gnome.org > > Subject: Re: NM stops and doesn't connect > > Date: Mon, 09 Mar 2009 16:21:16 -0400 > > I'm sending this message to the mailing site this time, I don't know whether > anyone can help me further. > > > Are you using the supplicant manually? With NM, there's no need to have > > a supplicant config file even, since NM will send config information to > > the supplicant on its own, based on the connections you've defined > > either in your distro config files or in GConf. > > Yes Dan, its the only way I can get it loaded, dbus is supposed to > activate it but won't, I've tried everything I know, which is not > much because I'm not a programmer. Yeah, what we should do is track down why the dbus activation stuff isn't working on your system. Any chance you'd like to download the dbus source package for your distro and rebuild it? YOu don't need to install it, since we can muck around in the source package build areas and just touch the tools we need, then copy them to the correct place on the system with our debugging information added. > I should make it clear that I'm trying to connect via the command > prompt as a user, although I get the same result as root. I assume this > is possible or should I be in a desktop manager with the applet etc? Yes, as long as the connection is provided either by the system settings service or the applet, you should be able to tell NM to connect using a simple python app or dbus-send. > > NetworkManager is trying to start the system settings service with D-Bus > > service activation, which is normal. Do you have > > the > > /usr/share/dbus-1/system-services/org.freedesktop.NetworkManagerSystemSettings.service > > file, and if so, what does it > > contain? > > [D-BUS Service] > Name=org.freedesktop.NetworkManagerSystemSettings > Exec=/usr/sbin/nm-system-settings --config > /etc/NetworkManager/nm-system-settings.conf > User=root > > > When nm-system-settings is started, what's the output of the following > > command? > > > > dbus-send --system --print-reply > > --dest=org.freedesktop.NetworkManagerSystemSettings > > /org/freedesktop/NetworkManagerSettings > > org.freedesktop.NetworkManagerSettings.ListConnections > > method return sender=:1.2 -> dest=:1.4 reply_serial=2 > object path "/fi/epitest/hostap/WPASupplicant/Interfaces/0" Hmm, that output doesn't look like something that the command would have returned. That looks like the output from a previous dbus-send command that I probably mailed to you when trying to debug the supplicant autolaunch issue. In any case, lets get to the bottom of this by building some debug info into the dbus autolaunch binary. Dan ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
NM stops and doesn't connect
> - Original Message - > From: "Dan Williams" > To: "Cliff McDiarmid" > Cc: networkmanager-list@gnome.org > Subject: Re: NM stops and doesn't connect > Date: Mon, 09 Mar 2009 16:21:16 -0400 I'm sending this message to the mailing site this time, I don't know whether anyone can help me further. > Are you using the supplicant manually? With NM, there's no need to have > a supplicant config file even, since NM will send config information to > the supplicant on its own, based on the connections you've defined > either in your distro config files or in GConf. Yes Dan, its the only way I can get it loaded, dbus is supposed to activate it but won't, I've tried everything I know, which is not much because I'm not a programmer. I should make it clear that I'm trying to connect via the command prompt as a user, although I get the same result as root. I assume this is possible or should I be in a desktop manager with the applet etc? > NetworkManager is trying to start the system settings service with D-Bus > service activation, which is normal. Do you have > the > /usr/share/dbus-1/system-services/org.freedesktop.NetworkManagerSystemSettings.service > file, and if so, what does it > contain? [D-BUS Service] Name=org.freedesktop.NetworkManagerSystemSettings Exec=/usr/sbin/nm-system-settings --config /etc/NetworkManager/nm-system-settings.conf User=root > When nm-system-settings is started, what's the output of the following > command? > > dbus-send --system --print-reply > --dest=org.freedesktop.NetworkManagerSystemSettings > /org/freedesktop/NetworkManagerSettings > org.freedesktop.NetworkManagerSettings.ListConnections method return sender=:1.2 -> dest=:1.4 reply_serial=2 object path "/fi/epitest/hostap/WPASupplicant/Interfaces/0" MAC -- Be Yourself @ mail.com! Choose From 200+ Email Addresses Get a Free Account at www.mail.com ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: NM stops and doesn't connect
On Mon, 2009-03-09 at 19:43 +, Cliff McDiarmid wrote: > Hi > > The last mail ended up blank trying this one: > > Can anyone advise on this error from NM after the supplicant is up with: Are you using the supplicant manually? With NM, there's no need to have a supplicant config file even, since NM will send config information to the supplicant on its own, based on the connections you've defined either in your distro config files or in GConf. > Trying to associate with * (SSID='Thomson7F8759' freq=2412 MHz) > Associated with * > WPA: Key negotiation completed with [PTK=CCMP GTK=TKIP] > CTRL-EVENT-CONNECTED - Connection to completed (auth) [id=0 > id_str=] > CTRL-EVENT-SCAN-RESULTS > CTRL-EVENT-SCAN-RESULTS > > > Mar 7 14:29:50 cliffhanger NetworkManager: starting... > Mar 7 14:29:50 cliffhanger NetworkManager: > nm_generic_enable_loopback(): error -17 returned from rtnl_addr_add(): Sucess > > Mar 7 14:29:50 cliffhanger NetworkManager: wlan0: driver is > 'iwl3945'. > Mar 7 14:29:50 cliffhanger NetworkManager: wlan0: driver supports > SSID scans (scan_capa 0x01). > Mar 7 14:29:50 cliffhanger NetworkManager: Found new 802.11 WiFi > device 'wlan0'. > Mar 7 14:29:50 cliffhanger NetworkManager: (wlan0): exported as > /org/freedesktop/Hal/devices/net_00_13_02_0d_3f_93 > Mar 7 14:29:50 cliffhanger NetworkManager: Trying to start the > system settings daemon... > Mar 7 14:29:54 cliffhanger NetworkManager: (wlan0): device state > change: 1 -> 2 > Mar 7 14:29:54 cliffhanger NetworkManager: (wlan0): preparing > device. > Mar 7 14:29:54 cliffhanger NetworkManager: (wlan0): deactivating > device (reason: 2). > Mar 7 14:29:54 cliffhanger NetworkManager: Setting system hostname > to 'localhost.localdomain' (no default device) > Mar 7 14:29:54 cliffhanger NetworkManager: (wlan0): device state > change: 2 -> 3 > Mar 7 14:29:54 cliffhanger NetworkManager: (wlan0): supplicant > interface state: starting -> ready > Mar 7 14:31:50 cliffhanger NetworkManager: Trying to start the > system settings daemon... > Mar 7 14:33:50 cliffhanger NetworkManager: Trying to start the > system settings daemon... > Mar 7 14:35:50 cliffhanger NetworkManager: Trying to start the > system settings > ETC ETC ETC NetworkManager is trying to start the system settings service with D-Bus service activation, which is normal. Do you have the /usr/share/dbus-1/system-services/org.freedesktop.NetworkManagerSystemSettings.service file, and if so, what does it contain? > If I use this check > > nm-system-settings --debug --config > /etc/NetworkManager/nm-system-settings.conf > > I get:. > > ** Message: Loaded plugin keyfile: (c) 2007 - 2008 Red Hat, Inc. To report > bugs please use the NetworkManager mailing list Expected, the service is running as normal and should be providing data to NetworkManager via D-Bus. It does not daemonize becuase it doesn't need to when its started with D-Bus service activation, which is the normal procedure. When nm-system-settings is started, what's the output of the following command? dbus-send --system --print-reply --dest=org.freedesktop.NetworkManagerSystemSettings /org/freedesktop/NetworkManagerSettings org.freedesktop.NetworkManagerSettings.ListConnections If that returns something like: method return sender=:1.6 -> dest=:1.5810 reply_serial=2 array [ object path "/org/freedesktop/NetworkManagerSettings/0" ] then the system settings service is working correctly. Dan > the system then stops and I have to ctrl-c to bring the prompt back > > What's going on? Google mentions this error but no solution. > > thanks > > MAC > ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
NM stops and doesn't connect
Hi The last mail ended up blank trying this one: Can anyone advise on this error from NM after the supplicant is up with: Trying to associate with * (SSID='Thomson7F8759' freq=2412 MHz) Associated with * WPA: Key negotiation completed with [PTK=CCMP GTK=TKIP] CTRL-EVENT-CONNECTED - Connection to completed (auth) [id=0 id_str=] CTRL-EVENT-SCAN-RESULTS CTRL-EVENT-SCAN-RESULTS Mar 7 14:29:50 cliffhanger NetworkManager: starting... Mar 7 14:29:50 cliffhanger NetworkManager: nm_generic_enable_loopback(): error -17 returned from rtnl_addr_add(): Sucess Mar 7 14:29:50 cliffhanger NetworkManager: wlan0: driver is 'iwl3945'. Mar 7 14:29:50 cliffhanger NetworkManager: wlan0: driver supports SSID scans (scan_capa 0x01). Mar 7 14:29:50 cliffhanger NetworkManager: Found new 802.11 WiFi device 'wlan0'. Mar 7 14:29:50 cliffhanger NetworkManager: (wlan0): exported as /org/freedesktop/Hal/devices/net_00_13_02_0d_3f_93 Mar 7 14:29:50 cliffhanger NetworkManager: Trying to start the system settings daemon... Mar 7 14:29:54 cliffhanger NetworkManager: (wlan0): device state change: 1 -> 2 Mar 7 14:29:54 cliffhanger NetworkManager: (wlan0): preparing device. Mar 7 14:29:54 cliffhanger NetworkManager: (wlan0): deactivating device (reason: 2). Mar 7 14:29:54 cliffhanger NetworkManager: Setting system hostname to 'localhost.localdomain' (no default device) Mar 7 14:29:54 cliffhanger NetworkManager: (wlan0): device state change: 2 -> 3 Mar 7 14:29:54 cliffhanger NetworkManager: (wlan0): supplicant interface state: starting -> ready Mar 7 14:31:50 cliffhanger NetworkManager: Trying to start the system settings daemon... Mar 7 14:33:50 cliffhanger NetworkManager: Trying to start the system settings daemon... Mar 7 14:35:50 cliffhanger NetworkManager: Trying to start the system settings ETC ETC ETC If I use this check nm-system-settings --debug --config /etc/NetworkManager/nm-system-settings.conf I get:. ** Message: Loaded plugin keyfile: (c) 2007 - 2008 Red Hat, Inc. To report bugs please use the NetworkManager mailing list the system then stops and I have to ctrl-c to bring the prompt back What's going on? Google mentions this error but no solution. thanks MAC -- Be Yourself @ mail.com! Choose From 200+ Email Addresses Get a Free Account at www.mail.com ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
NM stops and doesn't connect
-- Be Yourself @ mail.com! Choose From 200+ Email Addresses Get a Free Account at www.mail.com ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
