x2go-user March 2017

x2go-user@lists.x2go.org

22 participants
26 discussions

Problems reconnecting
by Michael Eager 24 Mar '17

24 Mar '17

I'm using x2goclient v 4.0.5.2 on a Fedora 24 system connecting to a Centos 7 system. When I stop the client and attempt to reconnect, a window pops up saying that there are two sessions, one suspended and one running. If I click on the running session, the client appears to negotiate a connection but does not open a window. Instead it hangs and I have to kill the client. When I run the client again, I see the same two sessions. If I click on the suspended session, it also hangs, but the next time I run the client, both sessions are listed as running. If I select either session and click on terminate, the pop-up window updates to remove the session, but I can't connect. When I restart the client again, both sessions are still there, listed as running. Any suggestions? -- Michael Eager eager(a)eagercon.com 1960 Park Blvd., Palo Alto, CA 94306 650-325-8077

1 1

Continuing issue with resuming session on Windows Client
by Bragg, Richard 23 Mar '17

23 Mar '17

Client : 4.1.0.0 (Qt - 4.8.6) Want to run in full screen but that screen may change on location but issue is that I can start new session fine but resume always goes into a window. If I use Process Explorer I see the vcxsrv process On initial session parameters are as expected -nodecoration -notrayicon -clipboard -screen 0 @.... On resume I see (integrated X) - -multiwindow -notrayicon -clipboard (custom X - vcxsrv) - -screen 0 %wx%h -notrayicon -clipboard Any ideas? Richard Bragg MBCS| Application Analyst | Enterprise Monitoring and Automation | Technology and transformation Virgin Media | Unit C, Wellington Gate, Silverthorne Way, PORTSMOUTH, Hampshire, PO7 7XY M +447967046983 | D +443703 900110 | I 7806402 | E richard.bragg(a)virginmedia.co.uk<mailto:richard.bragg@virginmedia.co.uk> jive profile https://jive.systems.private/people/B0001850 | netcool community https://jive.systems.private/groups/netcool -------------------------------------------------------------------- Save Paper - Do you really need to print this e-mail? Visit www.virginmedia.com for more information, and more fun. This email and any attachments are or may be confidential and legally privileged and are sent solely for the attention of the addressee(s). Virgin Media will never ask for account or financial information via email. If you are in receipt of a suspicious email, please report to www.virginmedia.com/netreport If you have received this email in error, please delete it from your system: its use, disclosure or copying is unauthorised. Statements and opinions expressed in this email may not represent those of Virgin Media. Any representations or commitments in this email are subject to contract. Registered office: Media House, Bartley Wood Business Park, Hook, Hampshire, RG27 9UP Registered in England and Wales with number 2591237

1 0

multiwindow option and resizing an application window
by Dionne, Dennis P 09 Mar '17

09 Mar '17

Hello, I am using X2Go on RHEL 6.7 and I am very pleased with how well it works but I am having an issue when using X2Go with a custom application when I resize the application window. There are hundreds of other applications on our system that have no issue with resizing, it' just this one. This will happen every time I resize the app IF AND ONLY IF I start vcxsrv with "-multiwindow", if I start it any other way (-rootless, -fullscreen, -multimonitor) the app will resize fine. The problem is I then cannot resize the session window (resizing is only available in multiwindow mode apparently?). I am 100% aware that the application in question is at fault, however, it is very old, was produced by another company that will not give me the code and refuses to update it... I am also aware that this may be a VCXSrv issue and I can ask them as well but I was wondering if you all had run across something like this before. If you could give me some background on the differences between multiwindow vs "non-multiwindow" or could explain why multiwindow would fail I'd appreciate it. That may be a question for VCXSrv though. Setup: RHEL 6.7 X2Go Windows Client 4.0.5.1 (Windows 7 64bit) Server 4.0.1.19 Gnome 2.28 Thanks Dennis

3 7

Can't resume sessions on CentOS 7
by h i 07 Mar '17

07 Mar '17

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/<https://umail.umaryland.edu/owa/redir.aspx?C=WiEk1KdXvbDNgUFiMIUhnXCARdz6hK…> 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:xxxxx'. Info: Connection to remote proxy 'localhost:xxxx' 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.

1 0

X2Go on Mac with MATE and NIS/Fedora 25 closes after opening
by Robert Kudyba 07 Mar '17

07 Mar '17

We made sure to downgrade mesa but this happens with certain NIS users. Non-NIS users do not have this problem. Here are some logs. Mar 7 08:48:56 ourhost /usr/bin/x2gostartagent: x2gostartagent called with options: 800x600 adsl 16m-jpeg-9 unix-kde-depth_32 us query 0 D MATE both Mar 7 08:48:56 ourhost /usr/bin/x2gosessionlimit[30463]: x2gosessionlimit has been called Mar 7 08:48:56 ourhost /usr/bin/x2golistsessions[30466]: x2golistsessions has been called with options: --all-servers Mar 7 08:48:58 ourhost /usr/bin/x2gofeature: x2gofeature called with options: X2GO_RUN_EXTENSIONS Mar 7 08:48:58 ourhost /usr/share/x2go/x2gofeature.d/x2goserver-extensions.features: x2goserver-extensions.features called with options: X2GO_RUN_EXTENSIONS Mar 7 08:48:58 ourhost /usr/bin/x2goserver-run-extensions: x2goserver-run-extensions called with options: hostname-61-1488894536_stDMATE_dp32 pre-start Mar 7 08:48:58 ourhost /usr/bin/x2gostartagent: successfully started X2Go agent session with ID hostname-61-1488894536_stDMATE_dp32 Mar 7 08:48:58 ourhost /usr/bin/x2gofeature: x2gofeature called with options: X2GO_RUN_EXTENSIONS Mar 7 08:48:58 ourhost /usr/share/x2go/x2gofeature.d/x2goserver-extensions.features: x2goserver-extensions.features called with options: X2GO_RUN_EXTENSIONS Mar 7 08:48:58 ourhost /usr/bin/x2goserver-run-extensions: x2goserver-run-extensions called with options: hostname-61-1488894536_stDMATE_dp32 post-start Mar 7 08:48:58 ourhost dnf: Metadata cache created. Mar 7 08:48:58 ourhost /usr/bin/x2gostartagent: blocking creation of agent's keyboard file /tmp/.x2go-hostname/C-hostname-61-1488894536_stDMATE_dp32/keyboard as requested by session startup command Mar 7 08:48:58 ourhost systemd: Started dnf makecache. Mar 7 08:49:03 ourhost /usr/bin/x2gocmdexitmessage: x2gocmdexitmessage called with options: hostname-61-1488894536_stDMATE_dp32 Mar 7 08:49:20 ourhost /usr/bin/x2gosuspend-session: x2gosuspend-session called with options: hostname-61-1488894536_stDMATE_dp32 Mar 7 08:49:21 ourhost /usr/bin/x2gofeature: x2gofeature called with options: X2GO_DESKTOPSHARING Mar 7 08:49:21 ourhost /usr/share/x2go/x2gofeature.d/x2goserver-extensions.features: x2goserver-extensions.features called with options: X2GO_DESKTOPSHARING Mar 7 08:49:21 ourhost /usr/share/x2go/x2gofeature.d/x2goserver-xsession.features: x2goserver-xsession.features called with options: X2GO_DESKTOPSHARING Mar 7 08:49:21 ourhost /usr/share/x2go/x2gofeature.d/x2goserver.features: x2goserver.features called with options: X2GO_DESKTOPSHARING Mar 7 08:49:21 ourhost /usr/bin/x2gofeature: x2gofeature called with options: X2GO_RUN_EXTENSIONS Mar 7 08:49:21 ourhost /usr/share/x2go/x2gofeature.d/x2goserver-extensions.features: x2goserver-extensions.features called with options: X2GO_RUN_EXTENSIONS Mar 7 08:49:21 ourhost /usr/bin/x2goserver-run-extensions: x2goserver-run-extensions called with options: hostname-61-1488894536_stDMATE_dp32 pre-suspend Mar 7 08:49:21 ourhost /usr/bin/x2goumount-session[31047]: x2goumount-session has been called with options: hostname-61-1488894536_stDMATE_dp32 Mar 7 08:49:41 ourhost /usr/bin/x2gosuspend-session: x2gosuspend-session called with options: hostname-61-1488894536_stDMATE_dp32 Mar 7 08:49:41 ourhost /usr/bin/x2gofeature: x2gofeature called with options: X2GO_DESKTOPSHARING Mar 7 08:49:41 ourhost /usr/share/x2go/x2gofeature.d/x2goserver-extensions.features: x2goserver-extensions.features called with options: X2GO_DESKTOPSHARING Mar 7 08:49:41 ourhost /usr/share/x2go/x2gofeature.d/x2goserver-xsession.features: x2goserver-xsession.features called with options: X2GO_DESKTOPSHARING Mar 7 08:49:41 ourhost /usr/share/x2go/x2gofeature.d/x2goserver.features: x2goserver.features called with options: X2GO_DESKTOPSHARING Mar 7 08:49:41 ourhost /usr/bin/x2gofeature: x2gofeature called with options: X2GO_RUN_EXTENSIONS Mar 7 08:49:41 ourhost /usr/share/x2go/x2gofeature.d/x2goserver-extensions.features: x2goserver-extensions.features called with options: X2GO_RUN_EXTENSIONS Mar 7 08:49:41 ourhost /usr/bin/x2goserver-run-extensions: x2goserver-run-extensions called with options: hostname-61-1488894536_stDMATE_dp32 pre-suspend Mar 7 08:49:41 ourhost /usr/bin/x2goumount-session[31286]: x2goumount-session has been called with options: hostname-61-1488894536_stDMATE_dp32 Mar 7 08:50:00 ourhost /usr/bin/x2gosuspend-session: x2gosuspend-session called with options: hostname-61-1488894536_stDMATE_dp32 Mar 7 08:50:01 ourhost /usr/bin/x2gofeature: x2gofeature called with options: X2GO_DESKTOPSHARING Mar 7 08:50:01 ourhost /usr/share/x2go/x2gofeature.d/x2goserver-extensions.features: x2goserver-extensions.features called with options: X2GO_DESKTOPSHARING Mar 7 08:50:01 ourhost /usr/share/x2go/x2gofeature.d/x2goserver-xsession.features: x2goserver-xsession.features called with options: X2GO_DESKTOPSHARING Mar 7 08:50:01 ourhost /usr/share/x2go/x2gofeature.d/x2goserver.features: x2goserver.features called with options: X2GO_DESKTOPSHARING Mar 7 08:50:01 ourhost /usr/bin/x2gofeature: x2gofeature called with options: X2GO_RUN_EXTENSIONS Mar 7 08:50:01 ourhost /usr/share/x2go/x2gofeature.d/x2goserver-extensions.features: x2goserver-extensions.features called with options: X2GO_RUN_EXTENSIONS Mar 7 08:50:01 ourhost /usr/bin/x2goserver-run-extensions: x2goserver-run-extensions called with options: hostname-61-1488894536_stDMATE_dp32 pre-suspend Mar 7 08:50:01 ourhost /usr/bin/x2goumount-session[31537]: x2goumount-session has been called with options: hostname-61-1488894536_stDMATE_dp32 Mar 7 08:50:20 ourhost /usr/bin/x2gosuspend-session: x2gosuspend-session called with options: hostname-61-1488894536_stDMATE_dp32 Mar 7 08:50:21 ourhost /usr/bin/x2gofeature: x2gofeature called with options: X2GO_DESKTOPSHARING Mar 7 08:50:21 ourhost /usr/share/x2go/x2gofeature.d/x2goserver-extensions.features: x2goserver-extensions.features called with options: X2GO_DESKTOPSHARING Mar 7 08:50:21 ourhost /usr/share/x2go/x2gofeature.d/x2goserver-extensions.features: x2goserver-extensions.features called with options: X2GO_DESKTOPSHARING Mar 7 08:50:21 ourhost /usr/share/x2go/x2gofeature.d/x2goserver-xsession.features: x2goserver-xsession.features called with options: X2GO_DESKTOPSHARING Mar 7 08:50:21 ourhost /usr/share/x2go/x2gofeature.d/x2goserver.features: x2goserver.features called with options: X2GO_DESKTOPSHARING Mar 7 08:50:21 ourhost /usr/bin/x2gofeature: x2gofeature called with options: X2GO_RUN_EXTENSIONS Mar 7 08:50:21 ourhost /usr/share/x2go/x2gofeature.d/x2goserver-extensions.features: x2goserver-extensions.features called with options: X2GO_RUN_EXTENSIONS Mar 7 08:50:21 ourhost /usr/bin/x2goserver-run-extensions: x2goserver-run-extensions called with options: hostname-61-1488894536_stDMATE_dp32 pre-suspend Mar 7 08:50:21 ourhost /usr/bin/x2goumount-session[31776]: x2goumount-session has been called with options: hostname-61-1488894536_stDMATE_dp32 Mar 7 08:50:40 ourhost /usr/bin/x2gosuspend-session: x2gosuspend-session called with options: hostname-61-1488894536_stDMATE_dp32 Mar 7 08:50:40 ourhost /usr/bin/x2gofeature: x2gofeature called with options: X2GO_DESKTOPSHARING Mar 7 08:50:41 ourhost /usr/share/x2go/x2gofeature.d/x2goserver-extensions.features: x2goserver-extensions.features called with options: X2GO_DESKTOPSHARING Mar 7 08:50:41 ourhost /usr/share/x2go/x2gofeature.d/x2goserver-xsession.features: x2goserver-xsession.features called with options: X2GO_DESKTOPSHARING Mar 7 08:50:41 ourhost /usr/share/x2go/x2gofeature.d/x2goserver.features: x2goserver.features called with options: X2GO_DESKTOPSHARING Mar 7 08:50:41 ourhost /usr/bin/x2gofeature: x2gofeature called with options: X2GO_RUN_EXTENSIONS Mar 7 08:50:41 ourhost /usr/share/x2go/x2gofeature.d/x2goserver-extensions.features: x2goserver-extensions.features called with options: X2GO_RUN_EXTENSIONS Mar 7 08:50:41 ourhost /usr/bin/x2goserver-run-extensions: x2goserver-run-extensions called with options: hostname-61-1488894536_stDMATE_dp32 pre-suspend Mar 7 08:50:41 ourhost /usr/bin/x2goumount-session[32016]: x2goumount-session has been called with options: hostname-61-1488894536_stDMATE_dp32 Mar 7 08:51:00 ourhost /usr/bin/x2gosuspend-session: x2gosuspend-session called with options: hostname-61-1488894536_stDMATE_dp32 Mar 7 08:51:00 ourhost /usr/bin/x2gofeature: x2gofeature called with options: X2GO_DESKTOPSHARING Mar 7 08:51:00 ourhost /usr/share/x2go/x2gofeature.d/x2goserver-extensions.features: x2goserver-extensions.features called with options: X2GO_DESKTOPSHARING Mar 7 08:51:00 ourhost /usr/share/x2go/x2gofeature.d/x2goserver-xsession.features: x2goserver-xsession.features called with options: X2GO_DESKTOPSHARING Mar 7 08:51:00 ourhost /usr/share/x2go/x2gofeature.d/x2goserver.features: x2goserver.features called with options: X2GO_DESKTOPSHARING Mar 7 08:51:00 ourhost /usr/bin/x2gofeature: x2gofeature called with options: X2GO_RUN_EXTENSIONS Mar 7 08:51:01 ourhost /usr/share/x2go/x2gofeature.d/x2goserver-extensions.features: x2goserver-extensions.features called with options: X2GO_RUN_EXTENSIONS Mar 7 08:51:01 ourhost /usr/bin/x2goserver-run-extensions: x2goserver-run-extensions called with options: hostname-61-1488894536_stDMATE_dp32 pre-suspend Mar 7 08:51:01 ourhost /usr/bin/x2goumount-session[32256]: x2goumount-session has been called with options: hostname-61-1488894536_stDMATE_dp32 Copyright (C) 2001, 2010 NoMachine. See http://www.nomachine.com/ for more information. Info: Proxy running in client mode with pid '30953'. Session: Starting session at 'Tue Mar 7 08:48:58 2017'. Info: Connecting to remote host 'localhost:62357'. Info: Connection to remote proxy 'localhost:62357' 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 ADSL link parameters 512/24/1/0. Info: Using cache parameters 4/4096KB/8192KB/8192KB. Info: Using pack method '16m-jpeg-9' with session 'unix-kde-depth_32'. Info: Using ZLIB data compression 1/1/32. Info: Using ZLIB stream compression 4/4. Info: No suitable cache file found. Info: Forwarding X11 connections to display '/private/tmp/com.apple.launchd.KQ3HYr1H3E/org.macosforge.xquartz:0'. Session: Session started at 'Tue Mar 7 08:49:00 2017'. Warning: Protocol mismatch or no X authentication data. Session: Terminating session at 'Tue Mar 7 08:49:03 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 Mar 7 08:49:03 2017'. Connection timeout, aborting

2 1

Re: [X2Go-User] High performance OpenGL issues : fixed
by Robert GRASSO 07 Mar '17

07 Mar '17

Yes, sure. First, keep in mind that I am a sysadmin, I don't know a thing about graphic programming. It all began, fortunately, as we have one RHEL 6 virtual machine, and a RHEL 6 physical machine with an NVidia card. So, strangely, this software worked perfectly in the virtual machine, not only with the display in X2go, but on the console too ! The ESX does NOT have an NVidia card, it is a basic display for servers ! I would not have expected this ? So I began digging, using strace on my machines, reading your pages, searching with Google. An interesting test was the following : I initiated an X2go connection on the virtual machine, then from a terminal in this connection, I connected to the virtual machine through ssh -X : and from within this connection, I started the software on the vm, but with its display redirected on the X2go display of the physical machine : and it worked perfectly : this meant that the graphic driver on the machine where the software is run is not involved at all ! it would have to be some specific library involved in OpenGL. Then I figured out that on the VM alone, the software uses the stock "mesa" libGL.so. I found on some page on the web that a good test to see which libGL.so was used was to run ldd /usr/bin/glxinfo Then I looked at the postinstall script of the NVidia driver provided by ELrepo : I saw ldconfig ! This is how the NVidia libGL.so is provided to OpenGl applications ! And I must have seen somewhere else the tip about LD_LIBRARY_PATH : which worked perfectly with ldd /usr/bin/glxinfo But my software was still failing : why ? Actually, this software is complex, it starts opening a graphic console, from which the real utilities are started : this console is buggy, it does not provide the user's environment to the utilities it starts : this is what got me confused in a first time, I did not know it was buggy, I had to figure it out : so I dug deeper, found the utilities' rc file, figured out how to change LD_LIBRARY_PATH inside the rc file, and I was done ! So to us, the fix is "just" to add at the beginning of LD_LIBRARY_PATH : /usr/lib64, so that it is libGL.so from mesa-libGL-devel which is used for the OpenGL calls, and not the NVidia one, which is registered in the OS by ldconfig. And then, fix the other bugs which get in the way ;-) I hope I have been clear enough ? Robert Grasso | System engineer T +33 (0)4 56 38 08 33 | F +33 (0)4 56 38 08 30 rgrasso(a)altair.com | www.altair.com Altair | Innovation Intelligence ® > -----Original Message----- > From: ulrich.sibiller(a)gmail.com [mailto:ulrich.sibiller@gmail.com] On Behalf Of Ulrich Sibiller > Sent: Monday, March 06, 2017 7:00 PM > To: Robert GRASSO > Subject: Re: [X2Go-User] High performance OpenGL issues : fixed > > On Mon, Mar 6, 2017 at 5:53 PM, Robert GRASSO <rgrasso(a)altair.com> wrote: > > Apologies, fix found. > > > > > > > > Please dismiss this question > > > Can you please give us information about the fix? It may help others... > > Uli

1 0

Utility for cleaning x2go sessions
by Norman Gaywood 07 Mar '17

07 Mar '17

I can have 50-60 users logged on via x2go. Sometimes I need to logout many users. I use the following utility to list and match x2go sessions. Using the -r switch will run x2goterminate-session against the matched sessions. Others may find this useful, so I post my script here. Running the script without arguments will simply list all x2go sessions. The -h switch will show usage. I've attached the file but I suspect that will it be lost in the mailing list archives. Since it's short I also cut and paste here: ------------------------------ cut ------------------------------ #!/usr/bin/perl # List (and terminate) x2go sessions use strict; use warnings; use v5.10; use Getopt::Std; my %opts; getopts('hjqr', \%opts); my $help = defined $opts{h} ? $opts{h} : 0; my $printjob = defined $opts{j} ? $opts{j} : 0; my $quite = defined $opts{q} ? $opts{q} : 0; my $run = defined $opts{r} ? $opts{r} : 0; my $x2goterminate = '/usr/bin/x2goterminate-session'; my $x2golistsessions = '/usr/sbin/x2golistsessions_root'; if ($help) { print STDERR <<EOT; Usage: $0 [-hjqr] [[pattern] .. pattern] Runs $x2golistsessions and outputs in a more readable format Only print x2go sessions that match the pattern[s] If no pattern is given, lists all x2go sessions -h This message -j print job command to terminate matched sessions, not session information -q quite, don't print anything -r Terminate the matched sessions with $x2goterminate EOT exit 1; } # $x2golistsessions lists sessions like this: #456|user-122-1460160892_stDXFCE_dp32|122|host.com |R|2016-04-09T10:14:52|cba4aa51a29c4b7e2d529e6f628245eb|123.456.789.012|30259|30261|2016-04-09T10:14:56|user|1125|30262| # 0 1 2 3 4 5 6 7 8 9 10 11 12 13 # # These are the fields that we print (@pretty) and/or we match against my @pretty = (4,5,7,1); # # The sessionID field required for $x2goterminate my $sessionID = 1; # Results sorted by time my $sessionTime = 5; # Generate the string we print and match against sub pretty { my $s = shift; return "" unless defined $s; # (ref to) array of session fields return sprintf "%s %s %-16s %s", @{$s}[@pretty]; } # Get the session list and split the fields in each session my $sessions = qx( $x2golistsessions ); my @sessions = (); for my $s (split /\n/, $sessions) { push @sessions, [ split '\|', $s ]; } # If no command line patterns, match all sessions unless (@ARGV) { @ARGV = ( '.' ); } # patten match on the session information my %tokill; # sessions to kill/display for my $p (@ARGV) { my @tokill = grep { grep /$p/, pretty($_) } @sessions; # convert to hash to eliminate duplicates over multiple @ARGV for my $s (@tokill) { $tokill{$s->[$sessionID]} = $s; } } # pretty = session information that patterns are matched against # job = command that would execute to terminate session for my $s (sort {$a->[$sessionTime] cmp $b->[$sessionTime]} values %tokill) { my $pretty = pretty($s); my $job = sprintf "%s %s", $x2goterminate, $s->[$sessionID]; unless ($quite) { say $printjob ? $job : $pretty; } system $job if $run; } -- Norman Gaywood, Computer Systems Officer School of Science and Technology University of New England Armidale NSW 2351, Australia ngaywood(a)une.edu.au http://turing.une.edu.au/~ngaywood Phone: +61 (0)2 6773 2412 Mobile: +61 (0)4 7862 0062 Please avoid sending me Word or Power Point attachments. See http://www.gnu.org/philosophy/no-word-attachments.html

1 0

High performance OpenGL issues
by Robert GRASSO 06 Mar '17

06 Mar '17

Hello, I am trying to have high-performance OpenGL graphics in X2go, from a modeling software : it is based on Jogl; for instance, you can rotate objects in the GUI. I am having issues. I am using : - X2go client 4.0.5.1 on Windows 7 - X2go server v 4.0.1 on RHEL 6 with KDE When I start the software on a physical machine with RHEL 6 and an updated NVIdia driver, on the physical screen, it works perfectly. When I start the software on the physical machine but with the display in the X2go client, the software crashes almost immediately Strangely, when I start the software on a virtual machine running RHEL 6 inside Vsphere, with the display either in the console or X2go, it works perfectly. So I assume that it may be related to other libraries brought in by the driver. I already figured out that I can work around the libGL.so from NVidia, if I add to the environment : export LD_LIBRARY_PATH=/usr/lib64 In this way, the software uses the system's libGL.so, I can see it with ldd /usr/bin/glxinfo Unfortunately, this is not sufficient. Does anybody have a solution ? or a hint ? Best regards R. Grasso

2 2

High performance OpenGL issues : fixed
by Robert GRASSO 06 Mar '17

06 Mar '17

Apologies, fix found. Please dismiss this question ********************************************************************************************* Hello, I am trying to have high-performance OpenGL graphics in X2go, from a modeling software : it is based on Jogl; for instance, you can rotate objects in the GUI. I am having issues. I am using : - X2go client 4.0.5.1 on Windows 7 - X2go server v 4.0.1 on RHEL 6 with KDE When I start the software on a physical machine with RHEL 6 and an updated NVIdia driver, on the physical screen, it works perfectly. When I start the software on the physical machine but with the display in the X2go client, the software crashes almost immediately Strangely, when I start the software on a virtual machine running RHEL 6 inside Vsphere, with the display either in the console or X2go, it works perfectly. So I assume that it may be related to other libraries brought in by the driver. I already figured out that I can work around the libGL.so from NVidia, if I add to the environment : export LD_LIBRARY_PATH=/usr/lib64 In this way, the software uses the system's libGL.so, I can see it with ldd /usr/bin/glxinfo Unfortunately, this is not sufficient. Does anybody have a solution ? or a hint ? Best regards R. Grasso

1 0

libnx
by Robert Dinse 03 Mar '17

03 Mar '17

For what it's worth, nx libs version 3.5.99.3 appear to be a significant improvement over 3.5.99.2, at least the machines with the 3.5.99.3 haven't exploded on me while I'm using them yet. -_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_- Eskimo North Linux Friendly Internet Access, Shell Accounts, and Hosting. Knowledgeable human assistance, not telephone trees or script readers. See our web site: http://www.eskimo.com/ (206) 812-0051 or (800) 246-6874.

4 10

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

x2go-user March 2017