Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#25362 - [netcfg] handles profile with spaces in the name badly
Attached to Project:
Arch Linux
Opened by Auguste Pop (Auguste) - Tuesday, 02 August 2011, 12:46 GMT
Last edited by Rémy Oudompheng (remyoudompheng) - Monday, 08 August 2011, 22:22 GMT
Opened by Auguste Pop (Auguste) - Tuesday, 02 August 2011, 12:46 GMT
Last edited by Rémy Oudompheng (remyoudompheng) - Monday, 08 August 2011, 22:22 GMT
|
DetailsDescription:
if came across a wireless network with a space in ssid. wifi-select successfully connected to the network and created a profile in /etc/network.d/ with a space in the file name accordingly. then, when i tried to netcfg -d 'profile with space', there were some warnings emitted in the console. anyway, the wlan0 interface was successfully brought down. btw, when trying to tab complete the command, the profile name is also broken down into pieces. Additional info: * package version(s) 2.5.5-1 * config and/or log files etc. Steps to reproduce: 1. find a wifi network with space in ssid. 2. use wifi-select to connect to this network. 3. netcfg -d 'the profile name' and don't forget to try to tab-complete the name in step 3. |
This task depends upon
Closed by Rémy Oudompheng (remyoudompheng)
Monday, 08 August 2011, 22:22 GMT
Reason for closing: Fixed
Additional comments about closing: in 2.6.7
Monday, 08 August 2011, 22:22 GMT
Reason for closing: Fixed
Additional comments about closing: in 2.6.7
Comment by Rémy Oudompheng (remyoudompheng) -
Saturday, 06 August 2011, 22:22 GMT
Fixed for next release. Could not reproduce any completion problems.