Description of problem: gogoc service loads but service doesn't start Version-Release number of selected component (if applicable): 1.2-22.fc18 How reproducible: Consistently on my machine since I upgraded Steps to Reproduce: 1. Upgrade from F17 to F18 2. Start service automatically (upon restart) or manually Actual results: The service only loads but fails to start Expected results: The service starts after an IPv4 connection is established & establishes an IPv6 over IPv4 tunnel Additional info: It works perfectly fine when typing gogoc in Konsole but just not as a service Related excerpts from /var/log/messages: Feb 6 22:28:32 Rey7 systemd[1]: Starting Freenet6.net tunnel client to IPv6... Feb 6 22:28:32 Rey7 systemd[1]: Started Freenet6.net tunnel client to IPv6. Feb 6 22:28:32 Rey7 systemd[546]: Failed at step NAMESPACE spawning /usr/bin/gogoc: Operation not permitted Feb 6 22:28:32 Rey7 systemd[1]: gogoc.service: main process exited, code=exited, status=226/NAMESPACE Feb 6 22:28:32 Rey7 systemd[1]: Unit gogoc.service entered failed state
It looks similar to bug #835131 Is your /tmp or /var/tmp a symlink? What have you mounted in /tmp and /var/tmp? Could you copy /usr/lib/systemd/system/gogoc.service to /etc/systemd/system/ and test without PrivateTmp?
Well I'm happy to troubleshoot how to fix but it also shouldn't have happened in the first place since I have a fairly uncustomized Fedora KDE install. Not sure if this happens with a fresh install of F18 or if its something that carried over from the upgrade.... Now I do remember ABRT with F17 complaining about a certain path where it was asking to use an alternate path (spool something or other) but I forget if /var/tmp was part of the original or alternate. Haven't seen that again since upgrading though. Back to your response, both /tmp & /var/tmp are not symlinks and their owner is set to root with read/write permissions. I noticed that /usr/tmp is a symlink though. I tried copying the .service file over & setting PrivateTmp to false and even including the -y parameter but still the same.
gogoc-1.2-23.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/gogoc-1.2-23.fc18
This bug was caused because the inclusion of /lib64 in ReadOnlyDirectories. I didn't notice it because I use a 64 bit machine. Sorry for the inconveniences.
Package gogoc-1.2-23.fc18: * 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 gogoc-1.2-23.fc18' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-2180/gogoc-1.2-23.fc18 then log in and leave karma (feedback).
gogoc-1.2-23.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report.