If it's not obvious from the lshw output, I have a Dell Latitude D620 laptop, with an Intel wifi card, using the iwl3945 driver. I don't know which package is responsible for the bug, I just linked everything I thought might be related.
Note that I can't perfectly reproduce this, obviously, as I'm not staying at that hotel anymore. It was perfectly deterministic there, of course. I imagine it can be easily tested by changing an access-point's ESSID to the one described above (try some others, too), but it needs to be done by a developer to make sure the encoding is the same as that above. (They might want to try a few others for good measure.) ** Description changed: Binary package hint: network-manager + (Hardy, up-to-date at the moment, last week of Mars 2008.) Hello! I've been traveling last week and I stayed at a hotel that had WiFi. I noticed a weird problem. The access points had ESSIDs containing French diacritics—"Hôtel de la Gare 1", etc. (it was a French hotel)—and I couldn't connect to them using nm-applet. In fact, nm-applet didn't display those ESSIDs at all. The problem might be with wireless-tools or with the driver, though: I've had time to do a bit of looking around. I used "iwlist scan" to check what was going on, and it turns out that it could see the access points, but the 'ô' character in the ESSID was displayed with an "unknown code-point" symbol. However, my terminal is correctly configured to UTF-8 (I can type the character, and 'cat'ing Unicode files with 'ô' works correctly), so I suspected some encoding problems. I did some logging (I'll attach the files next), which included redirecting the output of the scan to a file. If I open the file with Geany it detects the encoding as ISO-8859-1. I imagine "iwlist" (or maybe the driver or some other component) doesn't do some charset conversion it should do at some point. (Note that Windows laptops in the same room could detect, display and connect to the APs.) I could connect to the network by using "iwconfig ap [address] && iwconfig essid any", so the APs were probably working correctly. This should be easy to test by setting the ESSID of your access-point to "Hôtel" (encoded in various charsets, at least ISO-8859-1). Note that the first file I attach was obtained by simply redirecting output of commands while I was typing. So it should contain exactly the bytes outputed by the applications. (There are two attempts at connection in the log, the first time I mistakenly connected to another AP I didn't have access to. There's some screwing around with dhclient, too.) -- can't connect to networks with non-unicode essids https://bugs.launchpad.net/bugs/210484 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
