Re: NetworkManager - dbus returned an error.

2006-11-14 Thread Tom Sutherland
Couple of questions and comments:

This issue appears to happen using the gnome equivalent of
knetworkmanager (nm-applet?)

I've tried multiple WEP encrypted networks and non-encrypted
networks.  I *am* prompted to enter network credentials and the
front end in Gnome and KDE both appear to accept them.

I searched, but cannot seem to find a list for knetworkmanager -
any idea how to contact them?

Also got the following output, that somehow didn't get included in
original post:

NetworkManager: information   Activation (eth1) started...
NetworkManager: information   Activation (eth1) Stage 1 of 5
(Device Prepare) scheduled...
NetworkManager: information   Activation (eth1) Stage 1 of 5
(Device Prepare) started...
NetworkManager: information   Activation (eth1) Stage 2 of 5
(Device Configure) scheduled...
NetworkManager: information   Activation (eth1) Stage 1 of 5
(Device Prepare) complete.
NetworkManager: information   Activation (eth1) Stage 2 of 5
(Device Configure) starting...
NetworkManager: information   Activation (eth1/wireless):
access point 'bgw' is unencrypted, no key needed.
NetworkManager: WARNINGreal_act_stage2_config ():
Activation (eth1/wireless): couldn't connect to the supplicant.


Cheers,
Tom

On Thu, 2006-11-09 at 14:53 -0500, Dan Williams wrote:
 On Thu, 2006-11-09 at 09:04 -0500, Tom Sutherland wrote:
  Hello List!
  
  I've just recently upgrade to Kubuntu Edgy Eft, now it seems that
  NetworkManager is having issues with DBUS.
  
  When knetworkmanager attempts to connect to any wireless network, the
  bar graph gets about 30% complete, then disappears.  The connection is
  never made - it just kinda resets to a disconnected state.
 
 It appears that knetworkmanager is not storing the security information
 correctly, or cannot find it to return it to NM when NM requests it.
 Please check with the knetworkmanager people on that.
 
 Dan
 



smime.p7s
Description: S/MIME cryptographic signature
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list


Re: NetworkManager - dbus returned an error.

2006-11-14 Thread Timo Hoenig
Hi Tom,

On Tue, 2006-11-14 at 11:56 -0500, Tom Sutherland wrote:

 Couple of questions and comments:
 
 This issue appears to happen using the gnome equivalent of
 knetworkmanager (nm-applet?)
 
 I've tried multiple WEP encrypted networks and non-encrypted
 networks.  I *am* prompted to enter network credentials and the
 front end in Gnome and KDE both appear to accept them.
 
 I searched, but cannot seem to find a list for knetworkmanager -
 any idea how to contact them?

There is not a specific KNetworkManager list but I asked the KDE guys to
set up a list for NetworkManager specific questions regarding KDE. 

You can either find it at the end of this mail [1] or by clicking on the
first link popping up when querying the web using Google on the term
'kde networkmanager'.

If you experience the described behavior with KNetworkManager only
(read: if it works with nm-applet), please head over to that list and
post your troubles.

 Also got the following output, that somehow didn't get included in
 original post:

partial log snipped 

Thanks,

   Timo

[1] 'kde-networkmanager' mailing list
https://mail.kde.org/mailman/listinfo/kde-networkmanager

___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list


Re: NetworkManager - dbus returned an error.

2006-11-09 Thread Dan Williams
On Thu, 2006-11-09 at 09:04 -0500, Tom Sutherland wrote:
 Hello List!
 
 I've just recently upgrade to Kubuntu Edgy Eft, now it seems that
 NetworkManager is having issues with DBUS.
 
 When knetworkmanager attempts to connect to any wireless network, the
 bar graph gets about 30% complete, then disappears.  The connection is
 never made - it just kinda resets to a disconnected state.

It appears that knetworkmanager is not storing the security information
correctly, or cannot find it to return it to NM when NM requests it.
Please check with the knetworkmanager people on that.

Dan

 I can connect manually with no problem.
 
 Any help would be appreciated.
 
 
 Nov  8 21:29:10 localhost NetworkManager: information^Istarting...
 Nov  8 21:29:10 localhost NetworkManager: information^IAdding VPN
 service 'org.freedesktop.NetworkManager.vpnc' with name 'vpnc' and
 program '/usr/bin/nm-vpnc-service'
 Nov  8 21:29:10 localhost NetworkManager: information^IAdding VPN
 service 'org.freedesktop.NetworkManager.ppp_starter' with name 'ppp'
 and program '/usr/bin/nm-ppp-starter'
 Nov  8 21:29:10 localhost NetworkManager: information^Ieth0: Device
 is fully-supported using driver 'e1000'.
 Nov  8 21:29:10 localhost NetworkManager:
 information^Inm_device_init(): waiting for device's worker thread to
 start
 Nov  8 21:29:10 localhost NetworkManager:
 information^Inm_device_init(): device's worker thread started,
 continuing.
 Nov  8 21:29:10 localhost NetworkManager: information^INow managing
 wired Ethernet (802.3) device 'eth0'.
 Nov  8 21:29:10 localhost NetworkManager: information^IDeactivating
 device eth0.
 Nov  8 21:29:10 localhost NetworkManager: information^Ieth1: Device
 is fully-supported using driver 'ipw2200'.
 Nov  8 21:29:10 localhost NetworkManager:
 information^Inm_device_init(): waiting for device's worker thread to
 start
 Nov  8 21:29:10 localhost NetworkManager:
 information^Inm_device_init(): device's worker thread started,
 continuing.
 Nov  8 21:29:10 localhost NetworkManager: information^INow managing
 wireless (802.11) device 'eth1'.
 Nov  8 21:29:10 localhost NetworkManager: information^IDeactivating
 device eth1.
 Nov  8 21:29:12 localhost NetworkManager: information^IUpdating
 allowed wireless network lists.
 Nov  8 21:29:13 localhost NetworkManager: WARNING^I
 nm_dbus_get_network_data_cb (): nm_dbus_get_network_data_cb(): dbus
 returned an error.   (org.freedesktop.NetworkManagerInfo.NoSecurity)
 org.freedesktop.NetworkManagerInfo.NoSecurity
 Nov  8 21:29:13 localhost NetworkManager: information^ISWITCH: no
 current connection, found better connection 'eth1'.
 Nov  8 21:29:13 localhost dhcdbd: message_handler: message handler not
 found under /com/redhat/dhcp/eth1 for sub-path eth1.dbus.get.reason
 Nov  8 21:29:13 localhost NetworkManager: information^IWill activate
 connection 'eth1/2WIRE995'.
 
 Tom 
 [EMAIL PROTECTED]
 
 
 
 ___
 NetworkManager-list mailing list
 NetworkManager-list@gnome.org
 http://mail.gnome.org/mailman/listinfo/networkmanager-list

___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list