- x2go-user - X2Go ListServ

Nightly Builds Ubuntu Broken
by Robert Dinse 01 Mar '18

01 Mar '18

Updates broke on every Ubuntu server I have x2go nightly builds installed upon. It ends with: dpkg: error processing package x2goserver-fmbindings (--configure): dependency problems - leaving unconfigured Errors were encountered while processing: x2goserver x2goserver-extensions x2goserver-printing x2goserver-xsession x2goserver-fmbindings And a non-functional server though many more errors leading up to that. If you need the full dialogue let me know. -_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_- 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.

1 0

Fedora 27 and loginctl linger
by Norman Gaywood 01 Mar '18

01 Mar '18

It seems that 'loginctl linger' does not work anymore as an ordinary user on Fedora 27. This worked on Fedora 26. From: https://bugzilla.redhat.com/show_bug.cgi?id=1478974#c15 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 -- 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

2 1

Nightly Builds Exploded
by Robert Dinse 01 Mar '18

01 Mar '18

I know this is a hazard of using nightly builds but the stable does not have the right version of xrandr. Is there anything I can do to fix or do I just need to wait for another push? dpkg --configure x2goserver Setting up x2goserver (4.1.0.1-0x2go1~git20180301.1604+9.heuler.1) ... Job for x2goserver.service failed because the control process exited with error code. See "systemctl status x2goserver.service" and "journalctl -xe" for details. invoke-rc.d: initscript x2goserver, action "start" failed. â x2goserver.service - X2Go Server Daemon Loaded: loaded (/lib/systemd/system/x2goserver.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Wed 2018-02-28 18:16:37 PST; 3ms ago Process: 16339 ExecStart=/usr/sbin/x2gocleansessions (code=exited, status=2) Main PID: 906 (code=exited, status=0/SUCCESS) Feb 28 18:16:37 debian systemd[1]: Starting X2Go Server Daemon... Feb 28 18:16:37 debian x2gocleansessions[16339]: Can't locate X2Go/Server/DB/MySQL.pm in @INC (you may need to install the X2Go::Server::DB::MySQL moduleâ¦2. Feb 28 18:16:37 debian x2gocleansessions[16339]: BEGIN failed--compilation aborted at /usr/share/perl5/X2Go/Server/DB.pm line 42. Feb 28 18:16:37 debian x2gocleansessions[16339]: Compilation failed in require at /usr/sbin/x2gocleansessions line 34. Feb 28 18:16:37 debian x2gocleansessions[16339]: BEGIN failed--compilation aborted at /usr/sbin/x2gocleansessions line 34. Feb 28 18:16:37 debian systemd[1]: x2goserver.service: Control process exited, code=exited status=2 Feb 28 18:16:37 debian systemd[1]: Failed to start X2Go Server Daemon. Feb 28 18:16:37 debian systemd[1]: x2goserver.service: Unit entered failed state. Feb 28 18:16:37 debian systemd[1]: x2goserver.service: Failed with result 'exit-code'. Hint: Some lines were ellipsized, use -l to show in full. dpkg: error processing package x2goserver (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: x2goserver -_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_- 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.

1 0

x2go on Zorin
by Robert Dinse 27 Feb '18

27 Feb '18

The daily build formerly was working on Zorin, save for the xrandr issue. Now it is failing with: Loop: PANIC! Failure negotiating the session in stage '7'. Error: Failure negotiating the session in stage '7'. Loop: PANIC! Wrong version or invalid session authentication cookie. Error: Wrong version or invalid session authentication cookie. Session: Terminating session at 'Mon Feb 26 23:28:49 2018'. Session: Session terminated at 'Mon Feb 26 23:28:49 2018'. Connection timeout, abortingConnection timeout, -_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_- 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.

1 0

X2go on Zorin
by Robert Dinse 24 Feb '18

24 Feb '18

The stable build of x2go presently works on Zorin except xrandr version issues but the Nightly Builds does not. Nightly builds nxagent core dumps when the session tries to start. Got to go now but will provide more details, try to get a backtrace if I can, later when I get back. -_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_- 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.

1 0

Re: [X2Go-User] unable to start Qt/KDE apps under x2go
by Bernd Schubert 23 Feb '18

23 Feb '18

Hmm, yes, xwayland is installed, but I didn't update it yet to the version on bionic. For me it seems to be a pure qt issue on ubuntu 17.10. On 02/23/2018 12:47 AM, Robert Dinse wrote: > > I just apt install Xorg; apt remove Xwayland, didn't mess with any > of the Qt install. > > -_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_- > > 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. > > On Fri, 23 Feb 2018, Bernd Schubert wrote: > >> Date: Fri, 23 Feb 2018 00:32:04 +0100 >> From: Bernd Schubert <bs_lists(a)aakef.fastmail.fm> >> To: Robert Dinse <nanook(a)eskimo.com> >> Subject: Re: [X2Go-User] unable to start Qt/KDE apps under x2go >> >> >> >> On 02/22/2018 11:51 PM, Robert Dinse wrote: >>> >>> I'm running 17.10 but not Unity, been working fine for me. I do >>> not >>> use Wayland however, I am using Xorg. Bionic also moved back to Xorg, >>> so that >>> may be your issue. >> >> Which part does this? I have seen qtwayland, but didn't have it installed >> >> Thanks, >> Bernd >>

2 2

Attention: All X2Go Server Admins! Upcoming major X2Go (Server) Release
by Stefan Baur 23 Feb '18

23 Feb '18

Hi! We would like to inform you that a new X2Go stable version is about to be released, most likely around March 1st, 2018. In fact, the release is already ready - we are actively holding back the binary package builds at the moment so you have a chance to react. If you have set all your servers to automatically update to new releases, we suggest that you disable this mechanism now until you have verified that the new version works for you. If, on the other hand, you test and deploy updates manually, no change is required. Please test the new X2Go stable version as soon as it becomes available, so that we have a chance to fix any remaining issues that slipped through our testing early on. Should you encounter major problems with the new version, we suggest switching to the ESR branch, codenamed "saimaa". This branch will continue to receive security updates, but is (and will remain) based on what you currently know as "stable". Some packages, like cups-x2go, pinentry-x2go, x2godesktopsharing, x2go*bindings, are not part of saimaa and thus must be pulled from the regular repository. This requires proper setting of repository priorities, so packages existing in the saimaa repository take priority over packages from the regular repository. If you need assistance with this, please make sure you have disabled automatic updates before doing anything else, then ask for help either in our IRC channel #x2go on freenode, or on the x2go-user Mailing List. However, if you are a daredevil and already want to access binary packages that pretty much match what we are going to release soon, temporarily change your X2Go repository entry to the timestamped heuler repository bearing the timestamp of 2018-02-16, pull the update, then switch your repository back to stable. Note that this is a procedure not recommended for the average user. Try and use at your own risk. Kind Regards, Stefan Baur -- BAUR-ITCS UG (haftungsbeschränkt) Geschäftsführer: Stefan Baur Eichenäckerweg 10, 89081 Ulm | Registergericht Ulm, HRB 724364 Fon/Fax 0731 40 34 66-36/-35 | USt-IdNr.: DE268653243 -- BAUR-ITCS UG (haftungsbeschränkt) Geschäftsführer: Stefan Baur Eichenäckerweg 10, 89081 Ulm | Registergericht Ulm, HRB 724364 Fon/Fax 0731 40 34 66-36/-35 | USt-IdNr.: DE268653243

3 2

unable to start Qt/KDE apps under x2go
by Tomasz Chmielewski 22 Feb '18

22 Feb '18

Any Qt/KDE apps I start renders just a border and nothing else - see the screenshot: https://screenshots.firefox.com/GhM80HJvhnCV9TDu/null Not sure how to debug this? $ kate failed to get the current screen resources QXcbConnection: XCB error: 172 (Unknown), sequence: 169, resource id: 174, major code: 149 (Unknown), minor code: 20 Server - Ubuntu 17.10 64 bit: $ dpkg -l|grep x2go ii x2goagent 2:3.5.0.33-0~710~ubuntu17.10.1 all X2Go agent ii x2goserver 4.0.1.22-0~1197~ubuntu17.10.1 amd64 X2Go server daemon scripts ii x2goserver-extensions 4.0.1.22-0~1197~ubuntu17.10.1 all X2Go server daemon scripts (extensions) ii x2goserver-xsession 4.0.1.22-0~1197~ubuntu17.10.1 all X2Go server daemon scripts (Xsession runner) Client - Ubuntu 17.10 64 bit: $ dpkg -l|grep x2go ii x2goclient 4.1.0.0-1 amd64 X2Go Client application (Qt4) Tomasz Chmielewski https://lxadm.com

2 5

Some troubles with unclosed sessions
by Alain Aupeix 19 Feb '18

19 Feb '18

Hi, I'm using x2go from a maintaining program tools. I'm launching sessions from a program using this syntax: ------------------------------------------------------------- x2goclient --thinclient --kbd-type=pc105/fr --autologin --link=lan --clipboard=both --close-disconnect --session="x2go: alain@aupeix-GX723" & ------------------------------------------------------------- When launching, I have these messages in the terminal: ------------------------------------------------------------- x2go-INFO-1> "Starting X2Go Client..." x2go-INFO-4> "Translator: :/i18n/x2goclient_fr_fr found." x2go-INFO-4> "Traducteur : :/i18n/qt_fr_fr trouvé." Got bus address: "unix:abstract=/tmp/dbus-NNXGrUY5vF,guid=15d5d6a1f32b73b2952171e70000003a" Connected to accessibility bus at: "unix:abstract=/tmp/dbus-NNXGrUY5vF,guid=15d5d6a1f32b73b2952171e70000003a" Registered DEC: true x2go-INFO-3> "X2Go Client démarré." Registered event listener change listener: true QPixmap::scaled: Pixmap is a null pixmap QPixmap::scaled: Pixmap is a null pixmap x2go-INFO-8> "Démarrage de la connexion au serveur : 192.168.1.10:22461" Generating public/private rsa key pair. Your identification has been saved in /home/alain/.x2go/ssh/gen/key.MT9507. Your public key has been saved in /home/alain/.x2go/ssh/gen/key.MT9507.pub. The key fingerprint is: c8:f1:c4:f1:0e:c1:20:6b:9d:50:1f:1c:39:84:80:3a X2Go Client RSA user key The key's randomart image is: +--[ RSA 4096]----+ | .+oo**o | | . =.+== | | . o + =.. | |E . . = o | | . o S . | | | | | | | | | +-----------------+ ------------------------------------------------------------- When closing the session with the window system button [X], I have these messages: ------------------------------------------------------------- x2go-INFO-12> "Fermons X2Go Client parce que le paramètre --close-disconnect a été fourni." x2go-INFO-6> "Fermeture de X2Go Client ..." x2go-INFO-7> "Fini X2Go Client par la fermeture des "hooks"." WARNING: unable to send SIGTERM to process group '9507': No such process ------------------------------------------------------------- My program offers the choice of the session mode: SHADOW or XFCE/UNITY/.... The program choice is validated by modifying the parameter command of session in .x2goclient It has worked, by I have sometimes (and often) problems to open the session in the required mode. It often, even the parameter command has been changed, opens in the last used mode, and when the session is opened, in this case, I have a notification which says that the session is restored. I have tried removing the corresponding files in .x2go, but it doesn't solves anything. Do I use the good way to close the session ? Is there another way to close it ? Is there another way to open a session, and avoid this problem or can my launching command be improved ? Thanks A+ -- ------------------------------------------------------------------------ Alain Aupeix http://jujuland.pagesperso-orange.fr/ http://pissobi-lacassagne.pagesperso-orange.fr/ ------------------------------------------------------------------------ U.buntu 12.04 & Xu.buntu 16.04 | G.ramps 3.4.9-1 | H.arbour 3.2.0dev (2018-01-05 14:38) | Hw.Gui (2639) ------------------------------------------------------------------------

1 1

Re: [X2Go-User] Windows x2go client displays at incorrect resolution
by Davis, Jean-Paul 18 Feb '18

18 Feb '18

I have not followed up in the past nine months because my remote sessions are somewhat useable in the current state, but it still annoys me to no end, so I just tried looking at it some more. I do not have a solution. Here is a recap of what I have and have not figured out. When the Windows client display preferences are set to full screen (everything else default), the remote desktop session that appears on the client's physical display thinks it is connected to the "default" video output, for which xrandr (run in a terminal window, inside the remote desktop session) shows a maximum resolution of 1920x1200, with a resolution of 1280x720 selected, which is exactly half the width and half the height of the physical display on the client (2560x1440). The xdpyinfo command reports a dpi of 75. If I set the client preferences to 192 dpi (corresponding to physical display on client), the resulting remote desktop session is still 1280x720, but all elements are scaled up by a factor of 2. It is my understanding that this is the default scaling generated by X when it detects (or is given) a dpi larger than some value that it considers to be hi-dpi. I have seen suggestions about creating a new display section in xorg.conf on the server for a virtual monitor, but most people report that does not work. I am not knowledgeable enough to understand exactly how x2go interacts both with the X-server on the x2go server (RHEL 7.4) and with the X-server (VcXsrv) on the x2go client (Windows 10). I'm thinking that somehow, if possible, I need to change the "default" video output used by one or the other of those X-servers to allow 2560x1440 resolution. Does anyone know how to do this? Even if I get that to work, I may still have an issue getting the MATE desktop to use my desired hi-dpi scaling (instead of just forcing everything to double). Inside the remote MATE desktop, I am not able to change any display preferences; it always produces an error related to the versions of xrandr (display preferences requires at least 1.3, server version is 1.2, though program I'm actually running is 1.5). And would it be worth my time to try again building x2go from the Arctica project? Jean-Paul

1 1

Re: [X2Go-User] Fullscreen on multiple monitors
by Rob Janssen 14 Feb '18

14 Feb '18

Thanks for your reply! Well, maybe my terminology is wrong, but as I wrote I want to use Windows on the first physical screen and Linux via X2Go on the second physical screen, using the full screen so not running in a fullsized window. But that is all I can achieve now. Before, I could really use the full screen. It is a 1600x1200 screen and that was also the display size in X. Now the display size is less. Hope that is clear. Thanks for the hint w.r.t. the settings. I don't think it is a userfriendly solution, maybe I should file a bug report? It should just allow setting of options before it bombs out, I think. However, now that I have experimented with the settings and know it does not solve my issue, it is not an import problem at this time. BTW: I installed it on 64-bit Windows, so the program gets installed in Program Files (x86), but when I first try to do these settings the default X server path is in Program Files without the (x86) so that is obviously an invalid path. the default should be set to the actual location. Rob Janssen

1 0

Looking for X2GoClient 4.1.0 or higher for Windows
by Roger Moye 14 Feb '18

14 Feb '18

I am looking for X2Go client version 4.1.0.1 or higher for Windows in order to fix bug #1100. Currently 4.1.0.0 is the highest version available for download. Does anyone know if 4.1.0.1 will be made available for Windows? Thanks! -Roger Roger Moye HPC Engineer 713.425.6236 Office 713.376.2540 Mobile QUANTLAB Financial, LLC 3 Greenway Plaza Suite 200 Houston, Texas 77046 www.quantlab.com<https://www.quantlab.com/> ----------------------------------------------------------------------------------- The information in this communication and any attachment is confidential and intended solely for the attention and use of the named addressee(s). All information and opinions expressed herein are subject to change without notice. This communication is not to be construed as an offer to sell or the solicitation of an offer to buy any security. Any such offer or solicitation can only be made by means of the delivery of a confidential private offering memorandum (which should be carefully reviewed for a complete description of investment strategies and risks). Any reliance one may place on the accuracy or validity of this information is at their own risk. Past performance is not necessarily indicative of the future results of an investment. All figures are estimated and unaudited unless otherwise noted. If you are not the intended recipient, or a person responsible for delivering this to the intended recipient, you are not authorized to and must not disclose, copy, distribute, or retain this message or any part of it. In this case, please notify the sender immediately at 713-333-5440

1 0

pyhoca-gui doesn't minimize to systray in ubuntu gnome desktop
by brian mullan 13 Feb '18

13 Feb '18

I am using pre-release Ubuntu 18.04 which uses the Gnome desktop. x2goclient runs well using cli or gui pyhoca-cli works well also however, pyhoca-gui once executed shows the seal pup icon then disappears and I assumes runs in the background but its icon doesn't appear in the top systray like it used to in Unity. Brian

1 1

Fullscreen on multiple monitors
by Rob Janssen 13 Feb '18

13 Feb '18

I am using a setup where on a Windows PC I have the usual Windows interface on the left screen, and on the right screen I want fullscreen X2Go client. This has worked OK in the past on a Windows Vista PC with an X2Go version from 2014. For obvious reasons the PC has since been replaced and I have installed more recent X2Go software and from then on it fails to work like it did before. I have selected to use full screen on monitor 2 in the past, and it used the full display area, although it always started in a somewhat erratic way. It first opened a window on the second screen, then told the Linux system the display size had changed, then immediately changed it to full screen and sent another display size update. This sometimes confused the Linux window manager, resulting in funny window placement, but otherwise it worked OK. On the new system, first with Windows 7 and now with Windows 8, and with X2Go version 4.0.5.0 at first and now 4.1.0.0, I cannot get it to work anymore. No matter if I select the full screen mode or not, it always opens the Linux screen in a window, and on the left screen. I have to drag it to the right, and then click the "full screen window" widget, it then changes to nearly-full-screen (there are no window borders but there is a title bar with the usual widgets). I have experimented with the -multiwindows and -multimonitors flags as suggested in a bug tracking item, but without the desired result. I also experienced another bug while trying this: when the settings for the X server are invalid, the program bombs out with an alert that the settings are invalid and I need to check my configuration, but then it is no longer possible to change the configuration because the program won't stay running. Fortunately I had an image backup of the system made just before I started that experiment. Please advise what to do next... Rob

2 1

multimedia not running in the client
by Zenny 09 Feb '18

09 Feb '18

Hi, I am having problem to get multimedia played in an x2goclient or pyhoca-gui instance. The server is ubuntu 16.04 xenial and the client is running in debian 8 jessie. Says glx1.3+ needed. Both the server and the client have latest mesa-utils with glx v. 1.4, yet when I run 'glxinfo | grep -i version' via x2go clients, it reported server glx version 1.2 ! The outputs are reported below verbatim SERVER x2goserver-ubuntu-16.04): $ glxinfo | grep -i version server glx version string: 1.4 client glx version string: 1.4 GLX version: 1.4 Version: 18.1.0 Max core profile version: 3.3 Max compat profile version: 3.0 Max GLES1 profile version: 1.1 Max GLES[23] profile version: 3.0 OpenGL core profile version string: 3.3 (Core Profile) Mesa 18.1.0-devel OpenGL core profile shading language version string: 3.30 OpenGL version string: 3.0 Mesa 18.1.0-devel OpenGL shading language version string: 1.30 OpenGL ES profile version string: OpenGL ES 3.0 Mesa 18.1.0-devel OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.00 CLIENT x2goclient-debian-8-jessie: $ glxinfo | grep -i version server glx version string: 1.4 client glx version string: 1.4 GLX version: 1.4 OpenGL core profile version string: 3.3 (Core Profile) Mesa 13.0.6 OpenGL core profile shading language version string: 3.30 OpenGL version string: 3.0 Mesa 13.0.6 OpenGL shading language version string: 1.30 OpenGL ES profile version string: OpenGL ES 3.0 Mesa 13.0.6 OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.00 INSIDE X2GO SESSION x2goclient-ruuning-inside-debian-8-jessie: $ glxinfo | grep -i version server glx version string: 1.2 client glx version string: 1.4 GLX version: 1.2 Version: 18.1.0 Max core profile version: 3.3 Max compat profile version: 3.0 Max GLES1 profile version: 1.1 Max GLES[23] profile version: 3.0 OpenGL version string: 3.0 Mesa 18.1.0-devel OpenGL shading language version string: 1.30 -- Cheers, /z -.. .. ... -.-. .-.. .- .. -- . .-. | -.. .. ... -.-. .-.. .- .. -- . .-. CONFIDENTIALITY NOTICE AND DISCLAIMER: Access to this e-mail and its contents by anyone other than the intended recipient is unauthorized as it contains privileged and confidential information, and is subject to legal privilege. Please do not re/distribute it. If you are not the intended recipient (or responsible for delivery of the message to such person), you may not use, copy, distribute or deliver the email and part of its contents to anyone this message (or any part of its contents or take any action in connection to it. In such case, you should destroy this message, and notify the sender immediately. If you have received this email in error, please notify the sender or your sysadmin immediately by e-mail or telephone, and delete the e-mail from any computer. If you or your employer does not consent to internet e-mail messages of this kind, please notify the sender immediately. All reasonable precautions have been taken to ensure no viruses are present in this e-mail and attachments included. As the sender cannot accept responsibility for any loss or damage arising from the use of this e-mail or attachments it is recommended that you are responsible to follow your virus checking procedures prior to use. The views, opinions, conclusions and other informations expressed in this electronic mail are not given or endorsed by any company including the network providers unless otherwise indicated by an authorized representative independent of this message. -.. .. ... -.-. .-.. .- .. -- . .-. | -.. .. ... -.-. .-.. .- .. -- . .-.

3 4

Shared folders are not mounted in Ubuntu 16.04
by Zenny 09 Feb '18

09 Feb '18

Hi, I am having problem to get the local folder shared to an x2goclient or pyhoca-gui mounted despite adding the path and checking automount option. The server is ubuntu 16.04 xenial and the client is running in debian 8 jessie. However when I added manually using sshfs from the server, it gets mounted without problem. Could not figure out exactly what the problem is. -- Cheers, /z -.. .. ... -.-. .-.. .- .. -- . .-. | -.. .. ... -.-. .-.. .- .. -- . .-. CONFIDENTIALITY NOTICE AND DISCLAIMER: Access to this e-mail and its contents by anyone other than the intended recipient is unauthorized as it contains privileged and confidential information, and is subject to legal privilege. Please do not re/distribute it. If you are not the intended recipient (or responsible for delivery of the message to such person), you may not use, copy, distribute or deliver the email and part of its contents to anyone this message (or any part of its contents or take any action in connection to it. In such case, you should destroy this message, and notify the sender immediately. If you have received this email in error, please notify the sender or your sysadmin immediately by e-mail or telephone, and delete the e-mail from any computer. If you or your employer does not consent to internet e-mail messages of this kind, please notify the sender immediately. All reasonable precautions have been taken to ensure no viruses are present in this e-mail and attachments included. As the sender cannot accept responsibility for any loss or damage arising from the use of this e-mail or attachments it is recommended that you are responsible to follow your virus checking procedures prior to use. The views, opinions, conclusions and other informations expressed in this electronic mail are not given or endorsed by any company including the network providers unless otherwise indicated by an authorized representative independent of this message. -.. .. ... -.-. .-.. .- .. -- . .-. | -.. .. ... -.-. .-.. .- .. -- . .-.

1 0

X font path is wrong
by A- Team 09 Feb '18

09 Feb '18

Hi all, we want to use x2go for a custom application that requires additional fonts. We installed the x2go-server on a CentOS 7 machine from EPEL repository and the x2go-client on Windows 7 (32-bit). When starting a session with xterm as application, that works as expected. But when starting a session with our custom application, it complains about not finding the fonts. We realized that in the x2go session, the font path as reported by "xset -q" is: Font Path: /usr/share/X11/fonts/misc/ But when opening a PuTTY session with X11 forwarding the font path as reported by "xset -q" is: Font Path: fonts/misc/,fonts/TTF/,fonts/OTF,fonts/Type1/,fonts/100dpi/,fonts/75dpi/,fonts/cyrillic/,fonts/Speedo/,fonts/terminus-font/,built-ins For the latter case, we used VcXsrv as X server on the Windows PC, and our custom application works. It seems that X11 forwarding in PuTTY uses the font directories of the X server on the Windows PC, but x2go uses the font path on the x2go-server (CentOS machine). How can we change this behaviour? Setting font path with e.g "xset fp+ fonts/100dpi/" returns: xset: bad font path element (#97), possible causes are: Directory does not exist or has wrong permissions Directory missing fonts.dir Incorrect font server address or syntax regards, Ralph

1 0

X font path is wrong
by A- Team 09 Feb '18

09 Feb '18

1 0

X font path is wrong
by A- Team 09 Feb '18

09 Feb '18

1 0

windows-10: how to setup borderless fullscreen window mode in multi monitor setup?
by Jörg Scheuermann 08 Feb '18

08 Feb '18

hey there, I have a new Windows-10 PC with 2 different-size monitors (16:9 + 4:3) attached. In my old Windows-7 PC I used to have X2Go running in borderless fullscreen window mode completely covering my widescreen monitor - so I could easily use the 4:3 monitor (e.g. Windows terminal program on the small monitor, while the X session covers the big one) without disturbing the 16:9 monitor. I tried that with my new Windows-10 PC to no avail - best I could get is Fullscreen mode, but this does not work for me: the mouse is locked to the big X screen and I cannot simply move to the small one. to do this I have to leave the fullscreen mode -- very distracting (flickering) and annoying. configuring the output to not be fullscreen but any of the other options does not get me to what I was used to have either: it's placing the X screen somewhere in the "middle", covering both of my monitors ... //update: seems when playing with output settings, x2go stores some strange settings somewhere - only way to get rid of placing the X screen "between" my monitors was to completely deleting that session and entering all the data again into a new one :/ anyway: I now have somethings I can live with, but still not perfect: even if I set the Display to "use whole monitor", it is not overlapping the taskbar - but only above! - meaning my X Desktop is higher than my monitor and I always have to scroll to see the top/bottom :-( --> is there any way to: * either have the X Window covering *everything*, including the taskbar, * or only let the X server render the screen not in the full height, but excluding the taskbars height? any of these options would get me the full X desktop on my widescreen monitor, without the need for scrolling; I don't really care whether I see the taskbar or not... any help please! p.s. the other two Display options are broken: * "custom resolution" does not take the selected monitor into account (see above: it's placing that custom window in the 'middle', covering both of my monitors) * "maximum size" does not generate a borderless window p.p.s. if I set the taskbar to auto-hide, the X screen still is pretending that it was there, i.e. it's not covering the taskbars space and I have an empty row where the taskbar used to be... /joerg

1 0

Upcoming Deprecation of (Almost) EOL Distributions
by Mihai Moldovan 07 Feb '18

07 Feb '18

Hi In order to lower resource stress when building packages, I plan to deprecate support for distributions that have (almost) reached End Of Life on December 31th 2017. This includes the following distro versions: - Debian: o 7.0 "wheezy" - Fedora o 23 o 24 o 25 - OpenSuSE o 13.1 o 13.2 o 42.1 Ubuntu builds are ceased automatically after upstream deprecation. After deprecation, no new builds will be published and existing builds will be moved to the archive repositories to discourage users from installing unmaintained software. Mihai

2 2

Could x2go make use of thisNirbheek’s Rantings: GStreamer has grown a WebRTC implementation
by brian mullan 03 Feb '18

03 Feb '18

http://blog.nirbheek.in/2018/02/gstreamer-webrtc.html?m=1

1 0

Gnome 3 and X2go
by Robert Dinse 31 Jan '18

31 Jan '18

When gnome3 first came out I was unsuccessful at getting it to work with x2go. However, I just tried installing gnome-flashback and gave it another shot, now it mostly works except I can find no way of logging out except to kill the gnome-flashback process. Am I missing something that should be installed or is it broken this way? -_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_- 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.

2 2

TCE usb mount
by Widu Wittekindt 29 Jan '18

29 Jan '18

Hi again, now that the netboot image builds just fine even on a stretch build host, I have another problem - well I've got a problem for every solution :-) My client doesn't mount usb media, with any of the images I made, regardless of the distribution (stretch or jessie) or the repo (code.x2go.org or LinuxHaus) or the build host (stretch or jessie). But the usb mount works with an image I got from a friend here in Freiburg - but this is a jessie image and one of my clients will not boot with a 3.16 kernel :-( Of course I think I did everything just as I should: 1. put the config as a script in the BUILDDIR 2. put the usb mount patch as a script in the BUILDDIR 3. put the build-script in the BUILDDIR 4. source the config 5. call the patch script 6. call the build script. What am I doing wrong? And theres a second question: Is it possible to output the sound on the x2go-server? cheers Widu

2 5

Can't get full screen on Raspberry PI
by Blake McBride 25 Jan '18

25 Jan '18

Hi, I have a Raspberry PI running their latest OS (9.1 Stretch) And I am running x2goclient 4.1.1.0 I can't seem to get full screen. If I set x2goclient and set it to Display Fullscreen, it starts up and works fine except that it is a window on my screen (having a head line with minimize, atc. buttons). Then when I exit, it changed the config to Custom 1920x1078. In fact I just noticed that if I select "Fullscreen" and then click "OK", when I go back in, it's changed to Custom 1920x1078. Same thing with Display Use whole display. Nothing I do will make "Fullscreen" stick. Not having any problems on my LinuxMint box. Thanks for any help! Blake McBride

1 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

x2go-user