Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1478974
Summary: | x2go killed by systemd | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Neal Becker <ndbecker2> |
Component: | x2goserver | Assignee: | Orion Poplawski <orion> |
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 26 | CC: | jansen, ngaywood, orion, pawel.bogucki |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
URL: | https://bugs.x2go.org/cgi-bin/bugreport.cgi?bug=1198 | ||
Whiteboard: | |||
Fixed In Version: | x2goserver-4.0.1.22-2.fc27 x2goserver-4.0.1.22-2.fc26 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2018-03-06 17:18:39 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Neal Becker
2017-08-07 15:33:23 UTC
And how should it accomplish this? At the moment I'm guessing that x2goruncommand should run "loginctl enable-linger". Could you try adding that and see what happens? I'm not able to reproduce this myself for some reason. I think systemd-run could do it, see example 5: https://www.freedesktop.org/software/systemd/man/systemd-run.html#Examples According to: https://bugs.x2go.org/cgi-bin/bugreport.cgi?bug=1198 this should be fixed in x2goserver (4.0.1.21) with: loginctl enable-linger in /usr/bin/x2gostartagent Could a new Fedora 26 package be built with this update? x2goserver-4.0.1.21-1.fc26 nx-libs-3.5.0.33-1.fc26 has been submitted as an update to Fedora 26. https://bodhi.fedoraproject.org/updates/FEDORA-2017-8d369659cb x2goserver-4.0.1.21-1.fc27 nx-libs-3.5.0.33-1.fc27 has been submitted as an update to Fedora 27. https://bodhi.fedoraproject.org/updates/FEDORA-2017-60c4aa0e01 x2goserver-4.0.1.21-1.el6 nx-libs-3.5.0.33-1.el6 has been submitted as an update to Fedora EPEL 6. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2017-1ef5f8615b x2goserver-4.0.1.21-1.fc25 nx-libs-3.5.0.33-1.fc25 has been submitted as an update to Fedora 25. https://bodhi.fedoraproject.org/updates/FEDORA-2017-5c350e9cf1 Any news on this? I ran into this same issue on F27, and after some searching, I found this bug report, but the version x2goserver-4.0.1.21-1 mentioned here doesn't seem to be in updates or updates-testing. The update to fix this still seems to be in bodhi and has not been pushed to updates-testing. I don't know enough to know why. I installed the upstream repo and updated that way: http://packages.x2go.org/fedora/x2go.repo x2goserver-4.0.1.21-1.fc27 nx-libs-3.5.0.33-1.fc27 has been submitted as an update to Fedora 27. https://bodhi.fedoraproject.org/updates/FEDORA-2017-60c4aa0e01 nx-libs-3.5.0.33-4.fc27 x2goserver-4.0.1.22-2.fc27 has been submitted as an update to Fedora 27. https://bodhi.fedoraproject.org/updates/FEDORA-2017-60c4aa0e01 nx-libs-3.5.0.33-4.fc26 x2goserver-4.0.1.22-2.fc26 has been submitted as an update to Fedora 26. https://bodhi.fedoraproject.org/updates/FEDORA-2017-8d369659cb nx-libs-3.5.0.33-4.fc26, x2goserver-4.0.1.22-2.fc26 has been pushed to the Fedora 26 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2017-8d369659cb nx-libs-3.5.0.33-4.fc27, x2goserver-4.0.1.22-2.fc27 has been pushed to the Fedora 27 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2017-60c4aa0e01 On Fedora 27 it seems that enable-linger does not work as an ordinary user which is required for x2goserver keep sessions alive. Inside an x2go session: $ loginctl enable-linger Failed to look up user 62: No such process and (as root) "loginctl show-user ngaywood" shows: Linger=no As root I can: loginctl enable-linger ngaywood and Linger will be set. This used to work in Fedora 26 x2goserver-4.0.1.22-0.0x2go1.1.git20180204.1197.main.fc27.x86_64 nx-libs-3.5.0.33-4.fc27, x2goserver-4.0.1.22-2.fc27 has been pushed to the Fedora 27 stable repository. If problems still persist, please make note of it in this bug report. nx-libs-3.5.0.33-4.fc26, x2goserver-4.0.1.22-2.fc26 has been pushed to the Fedora 26 stable repository. If problems still persist, please make note of it in this bug report. |