Spaces in ESSID Cause Wireless to Not Connect

I forgot to mention, that, as implied, the moment I remove spaces from the networks ESSID the problem immediately goes away. This leaves Gutsy unable to connect to most public networks I don't personally administrate, though.

Thank you for filing this bug. Are you still experiencing this problem on gutsy final or on Hardy?
If so, please attach /var/log/syslog when network-manager fails to connect.

I just took a look and can confirm that this bug still exists and is
100% replicatable in Kubuntu Hardy Alpha 6 / Beta. If I put a space in
the ssid, knetworkmanager doesn't even show a device, let alone ssid.
If I take the space(s) out of the ssid, it connects automatically with
no problems.
The only strange thing I just noticed is that if I have no spaces, and
it connects, and then I change the ssid to include a space, the system
is able to reconnect fine completely automatically until the computer
is rebooted. After reboot wireless is not able to conntect to the ssid
with a space.
So to recap:
1. SSID-space=ok
2. SSID-space, connect, change to SSID+space=ok
3. SSID+space+reboot=fail
Anyway, here's the syslog:

Mar 20 01:35:13 tablet syslogd 1.5.0#1ubuntu1: restart.
Mar 20 01:35:13 tablet anacron[11319]: Job `cron.daily' terminated (exit status: 1) (mailing output)
Mar 20 01:35:13 tablet anacron[11319]: Can't find sendmail at /usr/sbin/sendmail, not mailing output
Mar 20 01:35:13 tablet anacron[11319]: Normal exit (1 job run)
Mar 20 02:00:20 tablet -- MARK --
Mar 20 02:00:47 tablet init: tty4 main process (4208) killed by TERM signal
Mar 20 02:00:47 tablet init: tty5 main process (4209) killed by TERM signal
Mar 20 02:00:47 tablet init: tty2 main process (4213) killed by TERM signal
Mar 20 02:00:47 tablet init: tty3 main process (4214) killed by TERM signal
Mar 20 02:00:47 tablet init: tty1 main process (4215) killed by TERM signal
Mar 20 02:00:47 tablet init: tty6 main process (4216) killed by TERM signal
Mar 20 02:00:51 tablet kernel: [ 5168.743458] klauncher[5576]: segfault at 00000095 eip b74e0ee7 esp bf80ecc0 error 4
Mar 20 02:00:51 tablet console-kit-daemon[4853]: WARNING: Unable to activate console: No such device or address
Mar 20 02:00:51 tablet avahi-daemon[4703]: Got SIGTERM, quitting.
Mar 20 02:00:51 tablet avahi-daemon[4703]: Leaving mDNS multicast group on interface eth1.IPv4 with address 192.168.2.4.
Mar 20 02:00:53 tablet kernel: [ 8622.408508] ip6_tables: (C) 2000-2006 Netfilter Core Team
Mar 20 02:00:55 tablet exiting on signal 15
Mar 20 02:01:50 tablet syslogd 1.5.0#1ubuntu1: restart.
Mar 20 02:01:50 tablet kernel: Inspecting /boot/System.map-2.6.24-12-generic
Mar 20 02:01:50 tablet kernel: Loaded 27847 symbols from /boot/System.map-2.6.24-12-generic.
Mar 20 02:01:50 tablet kernel: Symbols match kernel version 2.6.24.
Mar 20 02:01:51 tablet kernel: Loaded 28249 symbols from 88 modules.
Mar 20 02:01:51 tablet kernel: [ 0.000000] Linux version 2.6.24-12-generic (buildd@palmer) (gcc version 4.2.3 (Ubuntu 4.2.3-2ubuntu4)) #1 SMP Wed Mar 12 23:01:54 UTC 2008 (Ubuntu 2.6.24-12.22-generic)
Mar 20 02:01:51 tablet kernel: [ 0.000000] BIOS-provided physical RAM map:
Mar 20 02:01:51 tablet kernel: [ 0.000000] BIOS-e820: 0000000000000000 - 000000000009f800 (usable)
Mar 20 02:01:51 tablet kernel: [ 0.000000] BIOS-e820: 000000000009f800 - 00000000000a0000 (reserved)
Mar 20 02:01:51 tablet kernel: [ 0.000000] BIOS-e820: 00000000000dc000 - 0000000000100000 (reserved)
Mar 20 02:01:51 tablet kernel: [ 0.000000] BIOS-e820: 0000000000100000 - 000000001ff70000 (usable)
Mar 20 02:01:51 tablet kernel: [ 0.000000] BIO...

In the future, please don't post logs directly in the comment.

Sure thing. Strange thing is that I went to the effort of adding it as an attachment here (click on read more... and you see the .txt file at the top). I'm not sure why it showed up actually in my comment... :(

I still suffer this problem on Ubuntu 8.10. I tried using the wl driver (my wireless card is a Broadcom one) and also using ndiswrapper with the proper firmware. Also happens with other laptop with a Inter card.

Thank you for taking the time to report this bug and helping to make Kubuntu better. The KDE3 version of KNetworkManager has been discontinued by its original authors. This unfortunately means that there will be no more bugfix releases, and updates in general will be limited to those fixing security flaws.

While we cannot fix your bug, the good news is that the applet has been totally rewritten for KDE4 in the upcoming Kubuntu 9.10 release. There is a good chance that this bug is no longer an issue with the new applet. If you find any similar or new issues with the applet included in Kubuntu 9.10, we would politely ask you to file them as new bugs against the "plasma-widget-networkmanagement" package.

Thanks in advance for your cooperation and understanding.

Heh.

Thanks John. I moved to KDE4 as soon as the first alpha of 4.0 was released. Problem is long since gone for me. :)