x2go-user

x2go-user@lists.x2go.org

2 participants
2322 discussions

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

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

x2go-user