[X2Go-User] username sessions begin even after reboot without login on Ubuntu 20.04

[h i]

Hello,

Recently working on a new system using x2go on Ubuntu 20.04 linux.

Noticed something different that we never experienced previously on 18.04.

Reboots usually clear all sessions per user.

After reboot on 18.04, you would see the following output from the linux 
command:

%ps -elf | grep username

4 S username    1  0  80   0 - x -  15:20 ?00:00:00 
/lib/systemd/systemd --user
5 S username       0  80   0 - x -  15:20 ?00:00:00 
(sd-pam)


However, after reboot on the Ubuntu 20.04 system, I see the following output:

4 S username  1 0 80 0 -  - 20:44 ? 0:00:00 /lib/systemd/systemd --user
5 S username   0 80 0 -  - 20:44 ? 0:00:00 (sd-pam)
0 S username   0 80 0 -  - 20:44 ? 0:00:00 /usr/bin/pulseaudio
0 S username   0 99 - -  - 20:44 ? 0:00:00 
/usr/libexec/tracker-miner-fs
0 S username   0 80 0 -  - 20:44 ? 0:00:00 /usr/bin/dbus-daemon 
--session --address=systemd: --nofork --nopidfile --systemd-activation 
--syslog-only
0 S username   0 80 0 -  - 20:44 ? 0:00:00 /usr/libexec/gvfsd
0 S username   0 80 0 -  - 20:44 ? 0:00:00 /usr/libexec/gvfsd-fuse 
/run/user/1020/gvfs -f -o big_writes
0 S username   0 80 0 -  - 20:44 ? 0:00:00 
/usr/libexec/gvfs-udisks2-volume-monitor
0 S username   0 80 0 -  - 20:44 ? 0:00:00 
/usr/libexec/gvfs-gphoto2-volume-monitor
0 S username   0 80 0 -  - 20:44 ? 0:00:00 
/usr/libexec/gvfs-afc-volume-monitor
0 S username   0 80 0 -  - 20:44 ? 0:00:00 
/usr/libexec/gvfs-mtp-volume-monitor
0 S username   0 80 0 -  - 20:44 ? 0:00:00 
/usr/libexec/gvfs-goa-volume-monitor
0 S username   0 80 0 -  - 20:44 ? 0:00:00 /usr/libexec/goa-daemon
0 S username   0 80 0 -  - 20:44 ? 0:00:00 
/usr/libexec/goa-identity-service


This behavior occurs after login to x2goclient for just one time. The usernames 
appear in the "top" commmand output with goa-identity-se process despite not 
logging for a x2goclient session after a reboot.

Is there some setting one can change in x2go for Ubuntu 20.04, so these 
processes aren't running if a person hasn't logged in x2goclient session after 
reboot?

Thanks.

h.
___
x2go-user mailing list
x2go-user@lists.x2go.org
https://lists.x2go.org/listinfo/x2go-user

Re: [X2Go-User] Removing "Suspend X2go Session.." in Ubuntu Mate desktop System Panel , 20.04

[h i]

Okay, Thanks.

I was able to get it to suspend using both methods. That was a mistake on my 
part. Too many x2go client windows open.

Using the command line x2gosuspend-session worked and properly suspended the 
session. Clicking on the item from the mate desktop menu worked as well.

Thanks for providing insight on how this menu item is now coded in the 
Mate-panel applet with 20.04.

It looks like it can't be removed easily. Since it just provides an additional 
option for suspending the session, removing it most likely isn't necessary.

Thanks again.

h



From: Mike Gabriel
Sent: Sunday, May 16, 2021 3:34 PM
To: h i
Cc: x2go-user@lists.x2go.org
Subject: Re: [X2Go-User] Removing "Suspend X2go Session.." in Ubuntu Mate 
desktop System Panel , 20.04

Hi,

On  So 16 Mai 2021 21:08:45 CEST, h i wrote:

> Hello,
>
> How can you remove the "Suspend X2Go Sesseion..." item from the
> Ubuntu Mate System panel?
>
> [cid:8d0d43b2-6e97-4a50-87a4-d76edbc29ab6]
>
> In Ubuntu 18.04, this was linked with x2gomatebindings. Uninstalling
> the bindings removed it. However, with Ubuntu 20.04, I could not
> locate x2gomatebindings in the Ubuntu repository. I want to remove
> it because  we don't need it and it doesn't work well with x2go
> client. Clicking on the item makes the desktop session disappear,
> but the x2go client window says the session is still running and
> doesn't disappear.
>
> Thanks.
>
> h.

The "Suspend X2Go Session..." menu item is now coded into the
corresponding MATE panel applet (via librda).

Currently, there is no "switch" to disable it, but it could be a
feature request.

The other issue is that X2Go Client does not recognize the session
suspension properly when done from inside the session, it seems.

If you open a terminal in the X2Go session and issue the command
x2gosuspend-session on the command line, do you observe the same
behaviour? (i.e. session goes away, but X2Go Client does not get it?)

Mike
--

DAS-NETZWERKTEAM
c\o Technik- und Ökologiezentrum Eckernförde
Mike Gabriel, Marienthaler Str. 17, 24340 Eckernförde
mobile: +49 (1520) 1976 148
landline: +49 (4351) 850 8940

GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22  0782 9AF4 6B30 2577 1B31
mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de

___
x2go-user mailing list
x2go-user@lists.x2go.org
https://lists.x2go.org/listinfo/x2go-user

[X2Go-User] Removing "Suspend X2go Session.." in Ubuntu Mate desktop System Panel , 20.04

[h i]

Hello,

How can you remove the "Suspend X2Go Sesseion..." item from the Ubuntu Mate 
System panel?

[cid:8d0d43b2-6e97-4a50-87a4-d76edbc29ab6]

In Ubuntu 18.04, this was linked with x2gomatebindings. Uninstalling the 
bindings removed it. However, with Ubuntu 20.04, I could not locate 
x2gomatebindings in the Ubuntu repository. I want to remove it because  we 
don't need it and it doesn't work well with x2go client. Clicking on the item 
makes the desktop session disappear, but the x2go client window says the 
session is still running and doesn't disappear.

Thanks.

h.
___
x2go-user mailing list
x2go-user@lists.x2go.org
https://lists.x2go.org/listinfo/x2go-user

Re: [X2Go-User] Suspending sessions causes performance slowing down

[h i]

Hello,

We added the sleep=0 option in the /etc/x2go/x2goagent.options file.

X2GO_NXOPTIONS="sleep=0"

In the /etc/x2go/x2goserver.conf file, we enabled the superenicer,i.e., changed 
enable=no to enable=yes.

[superenicer]
# enable the SupeReNicer code in x2gocleansessions, this will renice suspended s
essions to nice level 19
# and renice them to level 0 if the session becomes marked as running again...
enable=yes

and removed the comment from idle-nice-level and kept the value of 19

# the idle nice level (for suspended sessions)
idle-nice-level=19


Then we rebooted our system. With these changed settings we were able to see 
comparable processing speeds and CPU usage for active vs suspended sessions. 
This was our desire because many times we have to run processes overnight or 
over the course of several days while the session is suspended.

h


From: Ulrich Sibiller 
Sent: Tuesday, June 2, 2020 3:14 AM
To: h i 
Cc: x2go-user@lists.x2go.org 
Subject: Re: [X2Go-User] Suspending sessions causes performance slowing down

On Tue, Jun 2, 2020 at 3:04 AM h i  wrote:
> I ran a few tests and see the issue is GUI related in our case. It seems to 
> speak to the 2nd reason for sleep you described regarding the sending of 
> pixmaps.
>
> I ran two MATLAB scripts. Both including the same steps. However, 1 script 
> suppressed pop-windows tracking the script status. The 2nd script did not 
> suppress the pop-up windows displaying

What gui toolkit is matlab using?

> real-time status. The 1st script involving command lines ran in the same 
> amount whether the session was active or suspended. No reduction of time or 
> CPU usage. The 2nd script took much longer and CPU was reduced significantly 
> while the session was suspended.
>
> A few questions:
>
> for X2GO_NXOPTIONS="sleep=0", what does 0 represent in time. If I set the 
> value to 1000, what would that mean?

This defines how long nxagent should sleep. The unit should be
microseconds but there's a ticket for doublechecking that because it
looks like a mixup happened during implementation
(https://github.com/ArcticaProject/nx-libs/issues/928).

> Is the idle-nice-level=19 for suspended sessions the default setting?

As I said I don't know the superreniver feature in detail.

> Would the supernicer setting override the x2goagent sleep option setting?

no, they are two different things.

> What would be an example command for the -irlimit option in x2goagent.options 
> file.

see https://github.com/ArcticaProject/nx-libs/issues/796

Uli
___
x2go-user mailing list
x2go-user@lists.x2go.org
https://lists.x2go.org/listinfo/x2go-user

Re: [X2Go-User] Suspending sessions causes performance slowing down

[h i]

Thanks for the info, Uli.

I ran a few tests and see the issue is GUI related in our case. It seems to 
speak to the 2nd reason for sleep you described regarding the sending of 
pixmaps.

I ran two MATLAB scripts. Both including the same steps. However, 1 script 
suppressed pop-windows tracking the script status. The 2nd script did not 
suppress the pop-up windows displaying real-time status. The 1st script 
involving command lines ran in the same amount whether the session was active 
or suspended. No reduction of time or CPU usage. The 2nd script took much 
longer and CPU was reduced significantly while the session was suspended.

A few questions:


  1.  for X2GO_NXOPTIONS="sleep=0", what does 0 represent in time. If I set the 
value to 1000, what would that mean?
  2.  Is the idle-nice-level=19 for suspended sessions the default setting?
  3.  Would the supernicer setting override the x2goagent sleep option setting?
  4.  What would be an example command for the -irlimit option in 
x2goagent.options file.

h

From: Ulrich Sibiller 
Sent: Monday, June 1, 2020 5:22 PM
To: h i 
Cc: x2go-user@lists.x2go.org 
Subject: Re: [X2Go-User] Suspending sessions causes performance slowing down

On Mon, Jun 1, 2020 at 5:51 PM h i  wrote:
> By how much does the load reduce? I tried again over the weekend, and a 
> typical 5 minute process now takes 3 hours during a suspended session. Is 
> this normal or is there some underlying issue? Did this type of behavior 
> occur under freenx? Just don't recall this type of reduced speed while 
> suspending a session on the client side and running something overnight.  
> I've recently installed a Windows update on the client side and updated our 
> ubuntu 18.04 LTS server with mate DE. Any input would be appreciated. Thanks.
>

I cannot give you a percentage. It depends on the workload. There are
two locations where the nxagent will sleep before going on:  The first
is where the nxagent waits for input by his clients or the real X
server and the second one is when clients are sending pixmaps to the
nxagent. Here the sleep depends on the size of the pixmap. Bigger
pixmap, longer sleep.

So sessions with a higher percentage of pixmap operations are slower
than others.

This behaviour was added in June 2016 between 3.5.0.28 and 3.5.0.29
(commit 6051dec4a1ae6decd9123a3310098baf43f45c49). So if it was active
with freenx depends on what version of nx-libs your were using with
freenx.

Uli
___
x2go-user mailing list
x2go-user@lists.x2go.org
https://lists.x2go.org/listinfo/x2go-user

Re: [X2Go-User] Update: Problems after upgrading to recent x2go-server and x2go client releases

[h i]

Hello,

When using the ppa:x2go/stable repository, something seemed strange when I ran 
the update manager in Ubuntu 14.04 and Ubuntu 16.04. I received a message about 
a partial upgrade I've never seen since using Ubuntu. I've attached the 
message. After running this partial upgrade, I started experiencing the 
flickering problems. Removed x2goserver entirely, and did a fresh install of 
the most update to date version. Still experiencing the flickering problems.

I  uninstalled everything from x2goserver on our system. Also uninstalled any 
lingering package versions that might conflict with trying to install from the 
Saimaa repository.

After cleaning, I installed x2goserver from the Saimaa repository.

I no longer experience the flickering when maximizing/minimizing or moving the 
window from side-to side. Everything is working fine like it was prior to the 
most recent update from the ppa:x2go/stable repository. I think I'm going to 
stick with the Saimaa repository for now until the bugs are fixed from the 
ppa:x2go/stable  repository.

Also going to stick with x2goclient 4.1.0.0 where there is no issue with 
clicking the session panel. I can click where I'm accustomed to clicking again.

Why are there 2 repositories for x2go and which one should we use for the 
long-term?

Any help would be appreciated.

h.


From: x2go-user <x2go-user-boun...@lists.x2go.org> on behalf of h i 
<qpile...@outlook.com>
Sent: Friday, March 9, 2018 4:23 PM
To: x2go-user@lists.x2go.org
Subject: Re: [X2Go-User] Problems after upgrading to recent x2go-server and 
x2go client releases


Mihai,


Thanks for your response. Please see my responses below:


* On 03/07/2018 07:34 PM, h i wrote:
> >I've been experiencing problems with opening applications and resizing my 
> >x2go
> >client window after installing the newest version x2go-server.
>
>
> >The issues occurs on Ubuntu 14.04 and 16.04.
>
>
> >What happens now is that every time I maximize my x2go-client window, the 
> >images
> >on screen rapidly flicker and won't stop until I minimize the screen.

>>The flickering is a known problem, but as far as we can tell only appears on
>>Windows (and even then not with all X servers, but prominently with VcXsrv, 
>>that
>>we bundle). It's tracked here: 
>>https://github.com/ArcticaProject/nx-libs/issues/600

> Also, each time I move the window, a quick flicker occurs across the screen.

>Probably related to the move being something alike to a resize and thus also
>triggering the new xinerama code.


> >This never occurred before this new release.

>There is no known workaround currently, though it might be possible to just
>ignore multiple resize events in nxagent if the requested size doesn't change.
>We'll have to see how that goes.





I think I might have to roll-back to the previous x2goserver version. At least 
with our setup, we never had a flicker issue until this most recent  update.




> >On the client side, I upgraded to the 4.1.1.1 from 4.1.0.0 and experienced 
> >some
> >issues. I have to click on the outside/top-right edge of the session panel 
> >for
> >the login session window to appear. Any thing closer to the middle, and it 
> >won't
> >respond.

>This is not an issue, but an often requested new feature. I've changed the
>click-sensitive area to an upside-down L shape around the session settings that
>can be modified within the tile. Actually like this, where "s" denotes a
>click-sensitive area:

 ___
|sss|
|sss|
|sss|
|sss|
|sss|
|sss|
 ---

>The problem so far has been that users can normally edit some exposed settings
>within a tile, but doing so proved to be very difficult since an incorrect 
>click
>triggered a session startup instead of changing a setting, which was happening
>quite often.

>The sensitive area isn't small and figuring that out shouldn't take long
>usually, so I guess you've just been unlucky to always click on the right hand
>side which is typically insensitive but in the upper part.





Interesting. Yeah, I never had an issue with the sensitive area. Understandable 
that others might have an issue.





> >Once logged into a session, the flickering resulting
> >from moving/maximizing the window is much worse.
> >
>> Fortunately, I was able to revert back to x2go-client 4.1.0.0.

>Huh, the flickering should be always the same, whether a session has been
>started with 4.1.1.1 or 4.1.0.0. Though, potentially there could be a
>difference: versions prior to 4.1.1.1 won't be able to utilize the Xinerama
>feature in X2Go Server 4.

Re: [X2Go-User] Problems after upgrading to recent x2go-server and x2go client releases

[h i]

Mihai,


Thanks for your response. Please see my responses below:


* On 03/07/2018 07:34 PM, h i wrote:
> >I've been experiencing problems with opening applications and resizing my 
> >x2go
> >client window after installing the newest version x2go-server.
>
>
> >The issues occurs on Ubuntu 14.04 and 16.04.
>
>
> >What happens now is that every time I maximize my x2go-client window, the 
> >images
> >on screen rapidly flicker and won't stop until I minimize the screen.

>>The flickering is a known problem, but as far as we can tell only appears on
>>Windows (and even then not with all X servers, but prominently with VcXsrv, 
>>that
>>we bundle). It's tracked here: 
>>https://github.com/ArcticaProject/nx-libs/issues/600

> Also, each time I move the window, a quick flicker occurs across the screen.

>Probably related to the move being something alike to a resize and thus also
>triggering the new xinerama code.


> >This never occurred before this new release.

>There is no known workaround currently, though it might be possible to just
>ignore multiple resize events in nxagent if the requested size doesn't change.
>We'll have to see how that goes.





I think I might have to roll-back to the previous x2goserver version. At least 
with our setup, we never had a flicker issue until this most recent  update.






> >On the client side, I upgraded to the 4.1.1.1 from 4.1.0.0 and experienced 
> >some
> >issues. I have to click on the outside/top-right edge of the session panel 
> >for
> >the login session window to appear. Any thing closer to the middle, and it 
> >won't
> >respond.

>This is not an issue, but an often requested new feature. I've changed the
>click-sensitive area to an upside-down L shape around the session settings that
>can be modified within the tile. Actually like this, where "s" denotes a
>click-sensitive area:

 ___
|sss|
|sss|
|sss|
|sss|
|sss|
|sss|
 ---

>The problem so far has been that users can normally edit some exposed settings
>within a tile, but doing so proved to be very difficult since an incorrect 
>click
>triggered a session startup instead of changing a setting, which was happening
>quite often.

>The sensitive area isn't small and figuring that out shouldn't take long
>usually, so I guess you've just been unlucky to always click on the right hand
>side which is typically insensitive but in the upper part.





Interesting. Yeah, I never had an issue with the sensitive area. Understandable 
that others might have an issue.






> >Once logged into a session, the flickering resulting
> >from moving/maximizing the window is much worse.
> >
>> Fortunately, I was able to revert back to x2go-client 4.1.0.0.

>Huh, the flickering should be always the same, whether a session has been
>started with 4.1.1.1 or 4.1.0.0. Though, potentially there could be a
>difference: versions prior to 4.1.1.1 won't be able to utilize the Xinerama
>feature in X2Go Server 4.1.0.0, so when connecting with older client versions
>Xinerama will always be disabled in nxagent.


>> However,is there a way to revert back to this previous version/configuration
>> of x2goserver. Right now, it is has been a lot of flickering while to trying 
>> to
> >do routine tasks with the current release.

>That's what the Saimaa release is for. You'll have to switch repositories and
>make sure to pin the release.

>After doing so, you should be following issue reports that affect you and
>eventually switch back to the stable server release, since Saimaa is not 
>getting
>any bug fixes or new features, apart from security-related issues.




What is Saimaa release, and why are there two separate releases for x2go now?


Is the saimaa release from here:

https://launchpad.net/~x2go/+archive/ubuntu/saimaa


Thank you for your help.


h.





___
x2go-user mailing list
x2go-user@lists.x2go.org
https://lists.x2go.org/listinfo/x2go-user

[X2Go-User] Problems after upgrading to recent x2go-server and x2go client releases

[h i]

Hello,


I've been experiencing problems with opening applications and resizing my x2go 
client window after installing the newest version x2go-server.


The issues occurs on Ubuntu 14.04 and 16.04.


What happens now is that every time I maximize my x2go-client window, the 
images on screen rapidly flicker and won't stop until I minimize the screen.


Also, each time I move the window, a quick flicker occurs across the screen.


This never occurred before this new release.


I have a few systems with the current x2go verison installed, here is the 
output:


x2goversion
x2goserver: 4.1.0.0
x2goserver-common: 4.1.0.0
x2goserver-extensions: 4.1.0.0
x2goserver-fmbindings: 4.1.0.0
x2goserver-printing: 4.1.0.0
x2goserver-x2goagent: 3.5.99.14
x2goserver-xsession: 4.1.0.0



We have another system running x2go server, but have yet to update it due to 
the problems we've experienced.  Here is the output of the previous version we 
are running without the issues:


x2goversion
x2goagent: 3.5.0.33
x2goserver: 4.0.1.22
x2goserver-extensions: 4.0.1.22
x2goserver-xsession: 4.0.1.22


On the client side, I upgraded to the 4.1.1.1 from 4.1.0.0 and experienced some 
issues. I have to click on the outside/top-right edge of the session panel for 
the login session window to appear. Any thing closer to the middle, and it 
won't respond. I also get a pop-up message about the sound that I had not 
experienced with previous versions. Once logged into a session, the flickering 
resulting from moving/maximizing the window is much worse.

Fortunately, I was able to revert back to x2go-client 4.1.0.0.


However,is there a way to revert back to this previous version/configuration of 
x2goserver. Right now, it is has been a lot of flickering while to trying to do 
routine tasks with the current release.


Any insight would be appreciated.


Thanks.


H.


___
x2go-user mailing list
x2go-user@lists.x2go.org
https://lists.x2go.org/listinfo/x2go-user

[X2Go-User] Can't resume sessions on CentOS 7

[h i]

Hello,


We've had issues resuming suspended sessions. We connect to a linux server from 
different client machines (PC and Mac) using x2go. For some reason, after 
suspending sessions, we cannot resume sessions.


We receive messages such as:


X2Go-52
The remote proxy closed the connection while negotiating the session. This may 
be due to the wrong authentication credentials passed to the server.


or


Copyright (C) 2001, 2010 NoMachine.

See 
http://www.nomachine.com/
 for more information.



Info: Proxy running in client mode with pid '8xxx'.

Session: Starting session at 'Tue Jan 24 11:17:00 2017'.

Info: Connecting to remote host 'localhost:x'.

Info: Connection to remote proxy 'localhost:' established.

Info: Connection with remote proxy completed.

Warning: Unrecognized session type 'unix-kde-depth_32'. Assuming agent session.

Warning: Failed to read data from the X auth command.

Warning: Generated a fake cookie for X authentication.

Info: Using LAN link parameters xxx/24/1/0.

Info: Using pack method '16m-jpeg-9' with session 'unix-kde-depth_32'.

Info: Not using NX delta compression.

Info: Not using ZLIB data compression.

Info: Not using ZLIB stream compression.

Info: Not using a persistent cache.

Info: Forwarding X11 connections to display 'localhost:0'.

Session: Session started at 'Tue Jan 24 11:17:00 2017'.

Warning: Cookie mismatch in the X authentication data.

Session: Terminating session at 'Tue Jan 24 11:17:05 2017'.

Info: Your session was closed before reaching a usable state.

Info: This can be due to the local X server refusing access to the client.

Info: Please check authorization provided by the remote X application.

Session: Session terminated at 'Tue Jan 24 11:17:05 2017'.

Connection timeout, aborting

NXPROXY - Version 3.5.0




Or


The only way to resolve this problem is using the following two commands on the 
server:


rm -rf /tmp/.x2go-username/
 rm -rf ~/.x2go/C-username-*


After 2 attempts, we can log into the server using x2go, but a new session is 
started. The previous open session is terminated.


Is there a reason why this is happening? Is there an option to select during 
installation/configuration to prevent these resume problems?


Any help would greatly be appreciated.

___
x2go-user mailing list
x2go-user@lists.x2go.org
http://lists.x2go.org/listinfo/x2go-user