Hi Timo, hi Michael,

Le lundi 8 janvier 2007 13:44, Timo Hoenig a écrit :
> I have fixed this issue.  Could you please grab the patch [1] and build
> packages for Yannick that he can give it a try?

I've rebuilt the the debian package from the debian source with your patch. 
Now, knetworkmanager can see the wireless networks.

But when I try to associate with the network, knetworkmanager does not ask me 
for the WPA key (I tryed with a blank new user). What is strange, is that de 
NetworkManager logs states that the key was sent:

NetworkManager: <information>   Device eth1 activation scheduled...
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 'linksys' is encrypted, but NO valid key exists.  New key needed.
NetworkManager: <information>   Activation (eth1) New wireless user key
        requested for network 'linksys'.
NetworkManager: <information>   Activation (eth1) Stage 2 of 5 (Device 
        Configure) complete.
NetworkManager: <information>   Activation (eth1) New wireless user key for 
        network 'linksys' received.
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 'linksys' is encrypted, but NO valid key exists.  New key needed.
NetworkManager: <information>   Activation (eth1) New wireless user key 
        requested for network 'linksys'.
[etc]

Note that in the beginning of the log, I have a difference between 
knetworkmanager and nm-applet :

With nm-applet:
        NetworkManager: <information>   Updating allowed wireless network lists.
        NetworkManager: <information>   SWITCH: no current connection, found 
better 
                connection 'eth1'.
        NetworkManager: <information>   Will activate 
                connection 'eth1/linksys'.
        NetworkManager: <information>   Device eth1 activation scheduled...

With knetworkmanager:
        NetworkManager: <information>   Updating allowed wireless network lists.
        NetworkManager: <WARNING>        nm_dbus_get_networks_cb (): error 
received:
                org.freedesktop.NetworkManagerInfo.NoNetworks
                - org.freedesktop.NetworkManagerInfo.NoNetworks.
        NetworkManager: <debug info>    [1168267103.022356] 
                nm_device_802_11_wireless_get_activation_ap (): Forcing AP 
'linksys'
        NetworkManager: <information>   User 
                Switch: /org/freedesktop/NetworkManager/Devices/eth1 / linksys
        NetworkManager: <information>   Deactivating device eth1.
        NetworkManager: <information>   Device eth1 activation scheduled...

I don't know if it's important.

Nevertheless, I can connect with the "connect to another network" feature 
except that I have to use the WPA-PSK key and not the ASCII passphrase; 
Michael, on the debian-powerpc mailing list another person told me he has the 
same issue not being able to use the ASCII passphrase.

Sincerely,

Yannick

-- 
Les hommes qui disent que les femmes sont frigides
sont de mauvaises langues. 
        -+- Sacha Guitry -+-

Reply via email to