| Summary: | Laptop won't sleep when wireless network containing apostrophe is present | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Andrew <abenson> |
| Component: | pm-utils | Assignee: | Jaroslav Škarvada <jskarvad> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 16 | CC: | abenson, hughsient, jskarvad, pknirsch |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | i386 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2011-11-14 21:55:43 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
Andrew
2011-11-11 23:24:31 UTC
Could you provide the content of your ifcfg-Joel_Primack's_Guest_Network?, e.g. the following command should do it: # cat "/etc/sysconfig/network-scripts/ifcfg-Joel_Primack's_Guest_Network" Here's the current version, but this is after renaming the connection in NetworkManager to remove the '. If I try to put it back in I don't get the same problem any more - I installed an update to some of the NetworkManager tools on Saturday so perhaps this fixed the problem from NetworkManager's side? $ cat "/etc/sysconfig/network-scripts/ifcfg-Joel_Primacks_Guest_Network" ESSID="\'Joel Primack\\\'s Guest Network\'" MODE=Managed KEY_MGMT=WPA-PSK WPA_ALLOW_WPA=yes WPA_ALLOW_WPA2=yes TYPE=Wireless BOOTPROTO=dhcp DEFROUTE=yes PEERDNS=yes PEERROUTES=yes IPV4_FAILURE_FATAL=no IPV6INIT=no NAME="Joel Primacks Guest Network" UUID=398330e3-945b-4ae9-94f3-849d7b4e64e5 ONBOOT=yes USERS=abenson This was probably NetworkManager issue as special chars in ifcfg-* files have to be quoted. If it works, could we close this? It seems to work OK for me now, so I think this bug can be closed. |