On 08/11/2017 03:59 PM, Orion Poplawski wrote:
> There is also "systemd-run", not sure how that compares.
systemd-run is changing the unit type in which context a command is executed. By
default, commands are executed in a session context. With systemd-run, that can
be changed to scope, service
On 08/11/2017 12:53 AM, Mihai Moldovan wrote:
On 08/10/2017 04:07 AM, Orion Poplawski wrote:
So I guess the fix for this is to run "loginctl enable-linger" in
x2goruncommand? Do this seem correct?
See also https://bugzilla.redhat.com/show_bug.cgi?id=1478974
Sounds sane, I guess? This
That "fix" did not change anything to my issues.
The issues are coming even on a new session.
2017-08-11 9:47 GMT+02:00 Mihai Moldovan :
> tag #1198 pending
> fixed #1198 4.0.1.21
> thanks
>
> Hello,
>
> X2Go issue #1198 (src:x2goserver) reported by you has been
> fixed in X2Go
Processing commands for cont...@bugs.x2go.org:
> tag #1198 pending
Bug #1198 [x2goserver] Suspend session does not work since update to Fedora 26
Added tag(s) pending.
> fixed #1198 4.0.1.21
Bug #1198 [x2goserver] Suspend session does not work since update to Fedora 26
There is no source info for
tag #1198 pending
fixed #1198 4.0.1.21
thanks
Hello,
X2Go issue #1198 (src:x2goserver) reported by you has been
fixed in X2Go Git. You can see the changelog below, and you can
check the diff of the fix at:
http://code.x2go.org/gitweb?p=x2goserver.git;a=commitdiff;h=d0d592b
The issue will
On 08/11/2017 08:53 AM, Mihai Moldovan wrote:
> On 08/10/2017 04:07 AM, Orion Poplawski wrote:
>> So I guess the fix for this is to run "loginctl enable-linger" in
>> x2goruncommand? Do this seem correct?
I'll go for x2gostartagent, though, since that's really the first process in our
chain.
On 08/10/2017 04:07 AM, Orion Poplawski wrote:
> So I guess the fix for this is to run "loginctl enable-linger" in
> x2goruncommand? Do this seem correct?
>
> See also https://bugzilla.redhat.com/show_bug.cgi?id=1478974
Sounds sane, I guess? This feature (i.e., letting users enable linger) can