Description of problem: Trying to set the "pretty" hostname with a single-quote causes an error. ==== [root@an-c03n01 ~]# hostnamectl set-hostname --pretty "Alteeves Niche! - Cluster 01, Node 01" [root@an-c03n01 ~]# hostnamectl Static hostname: an-c03n01.alteeve.ca Pretty hostname: Alteeves Niche! - Cluster 01, Node 01 Icon name: n/a Machine ID: b7f473a7d24142beba31edcc5353f2fa Boot ID: 7a9d637f932e403085654cdd1bcd5f35 Operating System: Fedora 18 (Spherical Cow) CPE OS Name: cpe:/o:fedoraproject:fedora:18 Kernel: Linux 3.6.11-3.fc18.x86_64 Architecture: x86_64 [root@an-c03n01 ~]# hostnamectl set-hostname --pretty "Alteeve's Niche! - Cluster 01, Node 01" Failed to issue method call: Invalid argument [root@an-c03n01 ~]# hostnamectl set-hostname --pretty "Alteeve\'s Niche! - Cluster 01, Node 01" Failed to issue method call: Invalid argument ==== According to the man page, this should be fine. ==== the high-level "pretty" hostname which might include all all kinds of special characters (e.g. "Lennart's Laptop") ==== Version-Release number of selected component (if applicable): systemd-195-15.fc18.x86_64 How reproducible: 100% Steps to Reproduce: 1. Try to set a "pretty" hostname with a single-quote. 2. 3. Actual results: Fails to set the pretty hostname. Expected results: Set the pretty hostname. Additional info:
Fixed in git.
(In reply to comment #1) > Fixed in git. When will the update be available in Fedora 18? The issue still exists when using systemd-197-1.fc18.2.x86_64. Shall we walkaround it by manually editing the file /etc/machine-info?
systemd-201-2.fc18.1 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/systemd-201-2.fc18.1
Package systemd-201-2.fc18.2: * should fix your issue, * was pushed to the Fedora 18 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing systemd-201-2.fc18.2' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-5452/systemd-201-2.fc18.2 then log in and leave karma (feedback).
Package systemd-201-2.fc18.4: * should fix your issue, * was pushed to the Fedora 18 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing systemd-201-2.fc18.4' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-5452/systemd-201-2.fc18.4 then log in and leave karma (feedback).
Package systemd-201-2.fc18.5: * should fix your issue, * was pushed to the Fedora 18 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing systemd-201-2.fc18.5' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-5452/systemd-201-2.fc18.5 then log in and leave karma (feedback).
systemd-201-2.fc18.6 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/FEDORA-2013-5452/systemd-201-2.fc18.6
Package systemd-201-2.fc18.6: * should fix your issue, * was pushed to the Fedora 18 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing systemd-201-2.fc18.6' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-5452/systemd-201-2.fc18.6 then log in and leave karma (feedback).
systemd-201-2.fc18.6 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report.