Can't connect if connection name contains spaces
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
network-manager (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: network-manager
I hope this is not a replicate of an other bug.
If you have a wired network with a space in the name (e.g.: "rooter 1") you are unable to connect to this network. I know that spaces are bad ;)
Don't know if it happens in wireless networks too, because I don't have one.
Network names without spaces work correct. So there is a workaround but an errormessage, that tells you to use no spaces in the name, would be nice.
The package is network-manager 0.8-ubuntu3 in Ubuntu 10.04.
ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: network-manager 0.8-0ubuntu3
ProcVersionSign
Uname: Linux 2.6.32-21-generic x86_64
NonfreeKernelMo
Architecture: amd64
CRDA: Error: [Errno 2] No such file or directory
Date: Sat May 1 09:19:58 2010
IfupdownConfig:
auto lo
iface lo inet loopback
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
IpRoute:
192.168.178.0/24 dev eth0 proto kernel scope link src 192.168.178.23 metric 1
192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1
169.254.0.0/16 dev eth0 scope link metric 1000
default via 192.168.178.1 dev eth0 proto static
Keyfiles: Error: [Errno 2] No such file or directory
ProcEnviron:
PATH=(custom, user)
LANG=de_DE.utf8
SHELL=/bin/bash
RfKill:
SourcePackage: network-manager
WifiSyslog: