special characters break WPA key

Hi there
I was unable to reproduce this bug, for testing i use "ñïmósàê" as wpa password, and works fine, using network manager in gutsy.
Are you trying to connect using network manager?, "the icon at the top panel".
Could you please specify which version of ubuntu are you using, the network-manager, wpasupplicant and related packages as well.

Thanks in advance

I'm using an up to date Gutsy, NetworkManager and since I the special characters don't type well in password-dialogs, I copy-paste them from OOo. I can check the password with the 'show characters' box in Ubuntu, but I can't check how the password copy-pastes in my router through the webbrowser. Maybe the problem is in that copy-paste part to my router. If you can't reproduce it, then the problem is probably not Ubuntu's. I'll try to find out where the problem lies (maybe try to enter the password in the router from the WinXP machine and see if there's something amiss in the router or its webinterface).

You can mark this bug as something not-urgent / unconfirmed and I'll get back to it when I find out why this happens in my situation. Thanks for the quick reply!

Let's leave it incomplete until you can confirm if it was a problem with the copy/paste or with your local copy of wpasupplicant/network-manager.
I'll wait for your answer before taking further actions. I'm linking this report to network-manager since is what you're using to connect and because i don't want to leave this report without a package :-D.

I had the same problem on both Feisty and Gutsy with a WPA passphrase that contained umlauts (öäüÖÄÜ). This passphrase worked fine with Windows wifi clients but I never was able to connect through the Ubuntu network manager, though the network ESSID was shown correctly and the signal was of high strength.

Changing the passphrase to one that did not contain any umlauts or other special characters made a connection possible for the first time.

Hi there
Is this still an issue under Hardy Heron?, could you please check with the beta version.

Thanks.

Hello, and sorry for being rather late in my reply. I have just tested in an up-to-date Hardy, and the situation has bettered. NM tells its connected, the signalstrength indicators show connection as well, but I can't browse. After a minute the passphrase dialog comes again, asking for a password, even though the laptop looks connected. So there is some improvement, but we're not there yet.

If there's any logs or other info I can give you, please ask. I'll try to be quicker to answer next time!

I have the same problem with a fresh an up to date Hardy installation. With the network manager, the wpa pass phrase is not recognized when it includes special characters (French "é" in this case).

Logs example:

Jun 20 10:51:40 lsi-laptop NetworkManager: <info> Activation (eth1) New wireless user key for network 'Stratic' received.
Jun 20 10:51:40 lsi-laptop NetworkManager: <info> Activation (eth1) Stage 1 of 5 (Device Prepare) scheduled...
Jun 20 10:51:40 lsi-laptop NetworkManager: <info> Activation (eth1) Stage 1 of 5 (Device Prepare) started...
Jun 20 10:51:40 lsi-laptop NetworkManager: <info> Activation (eth1) Stage 2 of 5 (Device Configure) scheduled...
Jun 20 10:51:40 lsi-laptop NetworkManager: <info> Activation (eth1) Stage 1 of 5 (Device Prepare) complete.
Jun 20 10:51:40 lsi-laptop NetworkManager: <info> Activation (eth1) Stage 2 of 5 (Device Configure) starting...
Jun 20 10:51:40 lsi-laptop NetworkManager: <info> Activation (eth1/wireless): access point 'Stratic' is encrypted, and a key exists. No new key needed.
Jun 20 10:51:41 lsi-laptop NetworkManager: <info> SUP: sending command 'INTERFACE_ADD eth1^I^Iwext^I/var/run/wpa_supplicant0^I'
Jun 20 10:51:41 lsi-laptop NetworkManager: <info> SUP: response was 'OK'
Jun 20 10:51:42 lsi-laptop NetworkManager: <info> SUP: sending command 'AP_SCAN 1'
Jun 20 10:51:42 lsi-laptop NetworkManager: <info> SUP: response was 'OK'
Jun 20 10:51:42 lsi-laptop NetworkManager: <info> SUP: sending command 'ADD_NETWORK'
Jun 20 10:51:42 lsi-laptop NetworkManager: <info> SUP: response was '0'
Jun 20 10:51:42 lsi-laptop NetworkManager: <info> SUP: sending command 'SET_NETWORK 0 ssid 53747261746963'
Jun 20 10:51:42 lsi-laptop NetworkManager: <info> SUP: response was 'OK'
Jun 20 10:51:42 lsi-laptop NetworkManager: <info> SUP: sending command 'SET_NETWORK 0 proto WPA'
Jun 20 10:51:42 lsi-laptop NetworkManager: <info> SUP: response was 'OK'
Jun 20 10:51:42 lsi-laptop NetworkManager: <info> SUP: sending command 'SET_NETWORK 0 key_mgmt WPA-PSK'
Jun 20 10:51:42 lsi-laptop NetworkManager: <info> SUP: response was 'OK'
Jun 20 10:51:42 lsi-laptop NetworkManager: <info> SUP: sending command 'SET_NETWORK 0 psk <key>'
Jun 20 10:51:42 lsi-laptop NetworkManager: <info> SUP: response was 'OK'
Jun 20 10:51:42 lsi-laptop NetworkManager: <info> SUP: sending command 'ENABLE_NETWORK 0'
Jun 20 10:51:42 lsi-laptop NetworkManager: <info> SUP: response was 'OK'
Jun 20 10:51:42 lsi-laptop NetworkManager: <info> Activation (eth1) Stage 2 of 5 (Device Configure) complete.
Jun 20 10:51:42 lsi-laptop NetworkManager: <info> Old device 'eth1' activating, won't change.
Jun 20 10:51:46 lsi-laptop NetworkManager: <info> Supplicant state changed: 0
Jun 20 10:51:46 lsi-laptop NetworkManager: <info> Supplicant state changed: 0
Jun 20 10:51:47 lsi-laptop NetworkManager: <info> Old device 'eth1' activating, won't change.
Jun 20 10:51:52 lsi-laptop NetworkManager: <info> Supplicant state changed: 0
Jun 20 10:51:52 lsi-laptop NetworkManager: <info> Supplicant state changed: 0
Jun 20 10:51:53 lsi-laptop NetworkManager: <info> Old device 'eth1' activating, won't change.
Jun 20 10:51:58 ls...

this is a dupe of bug 210484