x2go-dev

x2go-dev@lists.x2go.org

1 participants
5399 discussions

Bug#1322: RFE: Allow setting nxagent nx/nx options on the server via x2goagent.options
by Orion Poplawski 20 Aug '18

20 Aug '18

Package: x2goserver Persion: 4.1.0.2 Tags: patch The attached patch allows the setting of nxagent nx/nx options on the server via x2goagent.options. Very useful for being able to set sleep=0. -- Orion Poplawski Manager of NWRA Technical Systems 720-772-5637 NWRA, Boulder/CoRA Office FAX: 303-415-9702 3380 Mitchell Lane orion(a)nwra.com Boulder, CO 80301 https://www.nwra.com/

3 2

Bug#1280: Windows x2goclient 4.1.x crashes with Try Auto Login
by Ross Mohn 15 Aug '18

15 Aug '18

Package: x2goclient (Windows) Version: 4.1.x Reproduced with x2goclient-4.1.0.0-2017.03.11-setup.exe and x2goclient-4.1.1.1-2018.03.01-setup.exe Noticed this about a year ago, but didn't debug at that time and just fell back to 4.0.x version. Setup: pagent.exe running with correct id_rsa.ppk SSH key. Check the "Try auto login" box in the session preferences. Launch x2goclient.debug.exe (v4.1.1.1): x2go-INFO-1> "Starting X2Go Client..." x2go-WARNING-1> "English language requested, not loading translator." x2go-WARNING-1> "English language requested, not loading translator." x2go-INFO-3> "Started X2Go Client." Process Explorer shows the following processes started, roughly in this order: x2goclient.debug.exe x2gohelper.exe sshd.exe pulseaudio.exe conhost.exe Click to launch the Session: x2go-INFO-8> "Starting connection to server: example.com:922" QObject::killTimers: timers cannot be stopped from another thread Process Explorer shows the following processes killed, roughly all at once: x2goclient.debug.exe x2gohelper.exe sshd.exe pulseaudio.exe conhost.exe Work arounds: 1) roll back to v4.0.x 2) uncheck the "Try auto login" box" and live with typing in your password. Thanks -Ross -- Ross Palmer Mohn rpmohn(a)waxandwane.org

2 1

Bug#1280: Resolved
by Ross Mohn 15 Aug '18

15 Aug '18

Installed x2goclient-4.1.2.0-2018.06.22 and performed additional testing. It seems that if I specify a key in the "Use RSA/DSA key for ssh connection" the client doesn't attempt to use the ssh agent at all, only that specific key file. I had thought that it would still try the agent first, but it only tries the specified key file and then moves right to asking for the password, skipping the agent altogether. Next I created a new id_ed25519.ppk file and loaded it with pagent. I leave "Use RSA/DSA key for ssh connection" blank. The client now immediately uses pagent for authentication and launches my session without requiring any further interaction. OK to close, thanks! -Ross

2 1

Bug#1319: PulseAudio does not start
by SW＠EU 14 Aug '18

14 Aug '18

Package: mingw32-pulseaudio Version: 7.1 Hi, Windows 10 forced update to 1803 (Pro edition, englisch + German language pack) and x2goclient updated using x2goclient-4.1.2.0-2018.06.22-setup.exe. Since that I have to disable Pulse-Audio because otherwise I get the attached error during any start of the client. I have in meantime uninstalled the the separate installed 64 Bit VcXsrv because the 32 Bit x2goclient installation has changed files in the 64 Bit VcXsrv installation (is this correct?) and uninstalled x2goclient, rebooted, x2goclient again installed but 64 Bit VcXsrv not again, rebooted, but still the same. TIA, Silvio

1 0

Bug#1317: extended checks for loadchecker (or broker ... dunno)
by Walid MOGHRABI 13 Aug '18

13 Aug '18

package: x2gobroker version: 0.0.4.0-0~1038~ubuntu16.04.1 priority: enhancement We encountered another corner case very annoying. The whole broker stack does its work quite well when everything works as expected (which is mostly the case). A failing server for example is perfectly handled, loadchecker simply disable this server from the list and thus, broker sends users to remaining live servers. Problems are beginning when your servers misbehaves. Loadchecker mainly checks : * liveness ("ping") * ssh acess * load/memory values This is okay but not enough to be sure that a server can handle incoming connections, for example, for our needs, we should make sure that : * a user can authenticate on a server (Active Directory authentication through PAM/Winbind) * some mounts are correct (/home folders, other user mounts or shares) * some networks are available * some mandatory services are running * ... In our recent problems, for unknown reasons, some servers were having troubles joining the Active Directory domain and thus, user auth was failing. On the broker/loadchecker side, the server is perfectly working and this is even one of the best performing server since it is empty so it allways tries to redirect incoming connections to this server and since users can't auth, it fails and blocks every new connections. With extended checks, this server would have been considered offline from the loadchecker point of view and thus, it would have just been out of the load balancing. Since those checks are pretty "specific", it would be great to have some kind of "extended check" feature where a directory "extra-check.d" folder would exist on the x2gobroker setup in which we could drop some scripts that would be executed by the x2gobroker user on the remote servers with just an "ok" or "ko" value. As soon as you get a "ko" value, the server would be considered unavailable and then removed from load balancing until the next "ok" check. Script could be of any language with supported intepreter installed on the server (could be bash, perl, python or anything, you'll just need the interpreted to be installed but this is the administrator responsibility). --- DISCLAIMER: This e-mail is private and confidential and may contain proprietary or legally privileged information. It is for the intended recipient only. If you have received this email in error, please notify the author by replying to it and then destroy it. If you are not the intended recipient you must not use, disclose, distribute, copy, print or rely on this e-mail or any attachment. Thank you

1 0

Bug#1316: many connections within the loadchecker sleeping time frame
by Walid MOGHRABI 13 Aug '18

13 Aug '18

package: x2gobroker version: 0.0.4.0-0~1038~ubuntu16.04.1 priority: enhancement I'm not really sure of that because it is pretty hard to reproduce that one but I have the impression that, if you have many users connecting nearly at the same time (and especially within the loadchecker sleep time which is 300s by default), the load factor value is not recalculated and thus, you might have many users sent to the same server instead of beeing equally distributed of the farm. Sometime, I have 3, 4, 5 ... users sent to the same server while I have a few servers empty of connected users. This is a race condition but every morning, it can happen since our users starts between 8:30AM and 9:30AM and we have about 100 users so you can easily have 5~6 people connecting in less than a minute. I think the load calculation should be more dynamic and not strictly done every x minutes. For example, you can still do the load calculation every 5mn in order to "reset" load values once but then, I think something like this could be done : * calculate the load every x minutes ("bootstrap" calculation) * user A logging in, broker asks loadchecker for a server to connect the user, loadchecker respond "server-01" * user A is sent to "server-01" and then, "server-01" is locked for a few seconds (5, 10, ... maybe user defined) (blocked for new incoming connections) * broker asks loadchecker to re-calculate the load value for "server-01" only * "server-01" is unlocked for new incoming connections That way, load value is recalculated "on demand" in real time and connections are sure to be retargeted to more available servers while this calculation is done. --- DISCLAIMER: This e-mail is private and confidential and may contain proprietary or legally privileged information. It is for the intended recipient only. If you have received this email in error, please notify the author by replying to it and then destroy it. If you are not the intended recipient you must not use, disclose, distribute, copy, print or rely on this e-mail or any attachment. Thank you

1 0

Bug#1315: loadchecker bad auto sleep time leads to faulty service
by Walid MOGHRABI 13 Aug '18

13 Aug '18

package: x2gobroker-loadchecker version: 0.0.4.0-0~1038~ubuntu16.04.1 priority: bug I had a problem with broker loadbalancing not working anymore even though the loadchecker service seemed to work well. Looking at the logs, I found an unusual "sleep time" for the loadchecker service then, after that, it seemed to never re-caclulate load on remote servers. --- 2018-08-08 08:43:40,379 - loadchecker - INFO - Executing agent command on remote host tce-server-14 (10.50.0.214): sh -c '/usr/lib/x2go/x2gobroker-agent foo checkload' 2018-08-08 08:43:40,812 - loadchecker - INFO - Broker agent answered: OK; loadavgXX:49; memAvail:21904; myMemAvail:22030; numCPU:16; typeCPU:2400; 2018-08-08 08:43:40,812 - loadchecker - INFO - LoadChecker.loadchecker(): contacted remote broker agent for backend=inifile, profile_id=WIN-TRAVAUX, hostname=tce-server-14, new load factor is: 1716558 2018-08-08 08:43:40,813 - loadchecker - DEBUG - LoadChecker.loadchecker(): sleeping for 6.976744186046512secs before querying next server 2018-08-08 08:43:48,051 - loadchecker - INFO - Executing agent command on remote host tce-server-13 (10.50.0.213): sh -c '/usr/lib/x2go/x2gobroker-agent foo checkload' 2018-08-08 08:43:48,497 - loadchecker - INFO - Broker agent answered: OK; loadavgXX:126; memAvail:21117; myMemAvail:21242; numCPU:16; typeCPU:2400; 2018-08-08 08:43:48,497 - loadchecker - INFO - LoadChecker.loadchecker(): contacted remote broker agent for backend=inifile, profile_id=WIN-TRAVAUX, hostname=tce-server-13, new load factor is: 643565 2018-08-08 08:43:48,498 - loadchecker - DEBUG - LoadChecker.loadchecker(): sleeping for 6.976744186046512secs before querying next server 2018-08-08 08:43:55,734 - loadchecker - INFO - Executing agent command on remote host tce-server-12 (10.50.0.212): sh -c '/usr/lib/x2go/x2gobroker-agent foo checkload' 2018-08-08 08:43:56,162 - loadchecker - INFO - Broker agent answered: OK; loadavgXX:52; memAvail:22260; myMemAvail:22386; numCPU:16; typeCPU:2400; 2018-08-08 08:43:56,162 - loadchecker - INFO - LoadChecker.loadchecker(): contacted remote broker agent for backend=inifile, profile_id=WIN-TRAVAUX, hostname=tce-server-12, new load factor is: 1643815 2018-08-08 08:43:56,163 - loadchecker - DEBUG - LoadChecker.loadchecker(): sleeping for 6.976744186046512secs before querying next server 2018-08-08 08:44:03,404 - loadchecker - INFO - Executing agent command on remote host tce-server-11 (10.50.0.211): sh -c '/usr/lib/x2go/x2gobroker-agent foo checkload' 2018-08-08 08:44:03,850 - loadchecker - INFO - Broker agent answered: OK; loadavgXX:123; memAvail:21398; myMemAvail:21524; numCPU:16; typeCPU:2400; 2018-08-08 08:44:03,851 - loadchecker - INFO - LoadChecker.loadchecker(): contacted remote broker agent for backend=inifile, profile_id=WIN-TRAVAUX, hostname=tce-server-11, new load factor is: 668035 2018-08-08 08:44:03,851 - loadchecker - DEBUG - LoadChecker.loadchecker(): sleeping for 6.976744186046512secs before querying next server 2018-08-08 08:44:11,093 - loadchecker - INFO - Executing agent command on remote host tce-server-10 (10.50.0.210): sh -c '/usr/lib/x2go/x2gobroker-agent foo checkload' 2018-08-08 08:44:11,532 - loadchecker - INFO - Broker agent answered: OK; loadavgXX:84; memAvail:22133; myMemAvail:22259; numCPU:16; typeCPU:2400; 2018-08-08 08:44:11,532 - loadchecker - INFO - LoadChecker.loadchecker(): contacted remote broker agent for backend=inifile, profile_id=WIN-TRAVAUX, hostname=tce-server-10, new load factor is: 1011794 2018-08-08 08:44:11,533 - loadchecker - DEBUG - LoadChecker.loadchecker(): sleeping for 6.976744186046512secs before querying next server 2018-08-08 08:44:18,774 - loadchecker - INFO - Executing agent command on remote host tce-server-09 (10.50.0.209): sh -c '/usr/lib/x2go/x2gobroker-agent foo checkload' 2018-08-08 08:44:19,206 - loadchecker - INFO - Broker agent answered: OK; loadavgXX:93; memAvail:21758; myMemAvail:21883; numCPU:16; typeCPU:2400; 2018-08-08 08:44:19,206 - loadchecker - INFO - LoadChecker.loadchecker(): contacted remote broker agent for backend=inifile, profile_id=WIN-TRAVAUX, hostname=tce-server-09, new load factor is: 898394 2018-08-08 08:44:19,206 - loadchecker - DEBUG - LoadChecker.loadchecker(): sleeping for 6.976744186046512secs before querying next server 2018-08-08 08:44:26,189 - loadchecker - DEBUG - LoadChecker.loadchecker(): performed 44 queries (failures: 0), sleeping for -6.976744186046517secs before starting next query cycle 2018-08-08 08:46:47,377 - loadchecker - DEBUG - LoadCheckServiceHandler.handle_read(): received load check query: backend=inifile, profile_id=TRAVAUX, hostname= 2018-08-08 08:46:47,377 - loadchecker - INFO - LoadCheckServiceHandler.handle_read(): load check result for backend=inifile, profile_id=TRAVAUX, hostname=tce-server-11: 763244 2018-08-08 08:46:47,377 - loadchecker - INFO - LoadCheckServiceHandler.handle_read(): load check result for backend=inifile, profile_id=TRAVAUX, hostname=tce-server-23: 1742811 2018-08-08 08:46:47,377 - loadchecker - INFO - LoadCheckServiceHandler.handle_read(): load check result for backend=inifile, profile_id=TRAVAUX, hostname=tce-server-26: 507295 2018-08-08 08:46:47,378 - loadchecker - INFO - LoadCheckServiceHandler.handle_read(): load check result for backend=inifile, profile_id=TRAVAUX, hostname=tce-server-18: 899328 2018-08-08 08:46:47,378 - loadchecker - INFO - LoadCheckServiceHandler.handle_read(): load check result for backend=inifile, profile_id=TRAVAUX, hostname=tce-server-19: 932160 2018-08-08 08:46:47,378 - loadchecker - INFO - LoadCheckServiceHandler.handle_read(): load check result for backend=inifile, profile_id=TRAVAUX, hostname=tce-server-09: 879966 2018-08-08 08:46:47,378 - loadchecker - INFO - LoadCheckServiceHandler.handle_read(): load check result for backend=inifile, profile_id=TRAVAUX, hostname=tce-server-28: 834700 2018-08-08 08:46:47,378 - loadchecker - INFO - LoadCheckServiceHandler.handle_read(): load check result for backend=inifile, profile_id=TRAVAUX, hostname=tce-server-17: 721955 2018-08-08 08:46:47,378 - loadchecker - INFO - LoadCheckServiceHandler.handle_read(): load check result for backend=inifile, profile_id=TRAVAUX, hostname=tce-server-25: 715089 2018-08-08 08:46:47,379 - loadchecker - INFO - LoadCheckServiceHandler.handle_read(): load check result for backend=inifile, profile_id=TRAVAUX, hostname=tce-server-29: 1195074 2018-08-08 08:46:47,379 - loadchecker - INFO - LoadCheckServiceHandler.handle_read(): load check result for backend=inifile, profile_id=TRAVAUX, hostname=tce-server-20: 1431168 2018-08-08 08:46:47,379 - loadchecker - INFO - LoadCheckServiceHandler.handle_read(): load check result for backend=inifile, profile_id=TRAVAUX, hostname=tce-server-27: 1196586 2018-08-08 08:46:47,379 - loadchecker - INFO - LoadCheckServiceHandler.handle_read(): load check result for backend=inifile, profile_id=TRAVAUX, hostname=tce-server-31: 1972650 2018-08-08 08:46:47,379 - loadchecker - INFO - LoadCheckServiceHandler.handle_read(): load check result for backend=inifile, profile_id=TRAVAUX, hostname=tce-server-13: 735827 2018-08-08 08:46:47,379 - loadchecker - INFO - LoadCheckServiceHandler.handle_read(): load check result for backend=inifile, profile_id=TRAVAUX, hostname=tce-server-24: 780717 2018-08-08 08:46:47,379 - loadchecker - INFO - LoadCheckServiceHandler.handle_read(): load check result for backend=inifile, profile_id=TRAVAUX, hostname=tce-server-10: 932487 2018-08-08 08:46:47,380 - loadchecker - INFO - LoadCheckServiceHandler.handle_read(): load check result for backend=inifile, profile_id=TRAVAUX, hostname=tce-server-12: 1237871 2018-08-08 08:46:47,380 - loadchecker - INFO - LoadCheckServiceHandler.handle_read(): load check result for backend=inifile, profile_id=TRAVAUX, hostname=tce-server-30: 1371001 2018-08-08 08:46:47,380 - loadchecker - INFO - LoadCheckServiceHandler.handle_read(): load check result for backend=inifile, profile_id=TRAVAUX, hostname=tce-server-21: 587846 2018-08-08 08:46:47,380 - loadchecker - INFO - LoadCheckServiceHandler.handle_read(): load check result for backend=inifile, profile_id=TRAVAUX, hostname=tce-server-14: 1616787 2018-08-08 08:46:47,380 - loadchecker - INFO - LoadCheckServiceHandler.handle_read(): load check result for backend=inifile, profile_id=TRAVAUX, hostname=tce-server-15: 741288 2018-08-08 08:46:47,380 - loadchecker - INFO - LoadCheckServiceHandler.handle_read(): load check result for backend=inifile, profile_id=TRAVAUX, hostname=tce-server-22: 924074 2018-08-08 08:46:54,245 - loadchecker - DEBUG - LoadCheckServiceHandler.handle_read(): received load check query: backend=inifile, profile_id=TRAVAUX, hostname= 2018-08-08 08:46:54,245 - loadchecker - INFO - LoadCheckServiceHandler.handle_read(): load check result for backend=inifile, profile_id=TRAVAUX, hostname=tce-server-11: 763244 2018-08-08 08:46:54,245 - loadchecker - INFO - LoadCheckServiceHandler.handle_read(): load check result for backend=inifile, profile_id=TRAVAUX, hostname=tce-server-23: 1742811 2018-08-08 08:46:54,246 - loadchecker - INFO - LoadCheckServiceHandler.handle_read(): load check result for backend=inifile, profile_id=TRAVAUX, hostname=tce-server-26: 507295 2018-08-08 08:46:54,246 - loadchecker - INFO - LoadCheckServiceHandler.handle_read(): load check result for backend=inifile, profile_id=TRAVAUX, hostname=tce-server-18: 899328 2018-08-08 08:46:54,246 - loadchecker - INFO - LoadCheckServiceHandler.handle_read(): load check result for backend=inifile, profile_id=TRAVAUX, hostname=tce-server-19: 932160 2018-08-08 08:46:54,246 - loadchecker - INFO - LoadCheckServiceHandler.handle_read(): load check result for backend=inifile, profile_id=TRAVAUX, hostname=tce-server-09: 879966 2018-08-08 08:46:54,246 - loadchecker - INFO - LoadCheckServiceHandler.handle_read(): load check result for backend=inifile, profile_id=TRAVAUX, hostname=tce-server-28: 834700 2018-08-08 08:46:54,246 - loadchecker - INFO - LoadCheckServiceHandler.handle_read(): load check result for backend=inifile, profile_id=TRAVAUX, hostname=tce-server-17: 721955 2018-08-08 08:46:54,246 - loadchecker - INFO - LoadCheckServiceHandler.handle_read(): load check result for backend=inifile, profile_id=TRAVAUX, hostname=tce-server-25: 715089 2018-08-08 08:46:54,246 - loadchecker - INFO - LoadCheckServiceHandler.handle_read(): load check result for backend=inifile, profile_id=TRAVAUX, hostname=tce-server-29: 1195074 2018-08-08 08:46:54,246 - loadchecker - INFO - LoadCheckServiceHandler.handle_read(): load check result for backend=inifile, profile_id=TRAVAUX, hostname=tce-server-20: 1431168 2018-08-08 08:46:54,247 - loadchecker - INFO - LoadCheckServiceHandler.handle_read(): load check result for backend=inifile, profile_id=TRAVAUX, hostname=tce-server-27: 1196586 2018-08-08 08:46:54,247 - loadchecker - INFO - LoadCheckServiceHandler.handle_read(): load check result for backend=inifile, profile_id=TRAVAUX, hostname=tce-server-31: 1972650 2018-08-08 08:46:54,247 - loadchecker - INFO - LoadCheckServiceHandler.handle_read(): load check result for backend=inifile, profile_id=TRAVAUX, hostname=tce-server-13: 735827 2018-08-08 08:46:54,247 - loadchecker - INFO - LoadCheckServiceHandler.handle_read(): load check result for backend=inifile, profile_id=TRAVAUX, hostname=tce-server-24: 780717 2018-08-08 08:46:54,247 - loadchecker - INFO - LoadCheckServiceHandler.handle_read(): load check result for backend=inifile, profile_id=TRAVAUX, hostname=tce-server-10: 932487 2018-08-08 08:46:54,247 - loadchecker - INFO - LoadCheckServiceHandler.handle_read(): load check result for backend=inifile, profile_id=TRAVAUX, hostname=tce-server-12: 1237871 2018-08-08 08:46:54,247 - loadchecker - INFO - LoadCheckServiceHandler.handle_read(): load check result for backend=inifile, profile_id=TRAVAUX, hostname=tce-server-30: 1371001 2018-08-08 08:46:54,247 - loadchecker - INFO - LoadCheckServiceHandler.handle_read(): load check result for backend=inifile, profile_id=TRAVAUX, hostname=tce-server-21: 587846 2018-08-08 08:46:54,247 - loadchecker - INFO - LoadCheckServiceHandler.handle_read(): load check result for backend=inifile, profile_id=TRAVAUX, hostname=tce-server-14: 1616787 2018-08-08 08:46:54,247 - loadchecker - INFO - LoadCheckServiceHandler.handle_read(): load check result for backend=inifile, profile_id=TRAVAUX, hostname=tce-server-15: 741288 2018-08-08 08:46:54,248 - loadchecker - INFO - LoadCheckServiceHandler.handle_read(): load check result for backend=inifile, profile_id=TRAVAUX, hostname=tce-server-22: 924074 2018-08-08 08:47:21,453 - loadchecker - DEBUG - LoadCheckServiceHandler.handle_read(): received load check query: backend=inifile, profile_id=TRAVAUX, hostname= --- As you can see, there is a strange line with a '-6.976744186046517secs' value for sleep time which seems to be interpreted as an infinite sleep time by the process and then, load is never recalculated : --- 2018-08-08 08:44:26,189 - loadchecker - DEBUG - LoadChecker.loadchecker(): performed 44 queries (failures: 0), sleeping for -6.976744186046517secs before starting next query cycle --- I don't see any reason why this happens and I was unable to reproduce it manually, it is a rare case but it already happened more than once. --- DISCLAIMER: This e-mail is private and confidential and may contain proprietary or legally privileged information. It is for the intended recipient only. If you have received this email in error, please notify the author by replying to it and then destroy it. If you are not the intended recipient you must not use, disclose, distribute, copy, print or rely on this e-mail or any attachment. Thank you

1 0

Bug#1314: x2gobroker : [limit groups] is not respected in a broker setup
by Walid MOGHRABI 13 Aug '18

13 Aug '18

package: x2goserver version: 4.1.0.1-0~1613~ubuntu16.04.1 priority: bug I added a limit of 10 for the x2gousers group like this : [limit groups] x2gousers=10 It seems to work when you connect directly with x2goclient (I get blocked when I reach the limit so the group is the good one and the limit work) but I had cases where the loadchecker was crashed and every users where targeted to the same server and on this server, I ended with more opened session than the limit. --- DISCLAIMER: This e-mail is private and confidential and may contain proprietary or legally privileged information. It is for the intended recipient only. If you have received this email in error, please notify the author by replying to it and then destroy it. If you are not the intended recipient you must not use, disclose, distribute, copy, print or rely on this e-mail or any attachment. Thank you

1 0

Bug#1312: Ubuntu 16.04 LTS Qt bug
by e8dude 11 Aug '18

11 Aug '18

I fixed my "Print" error. I'm still getting high CPU usage with Openbox using x2go and QT apps not opening after the last update. Here is the full XSession-x2go-errors error log if this helps: > XSession-x2go: X session started for root at Fri Aug 10 00:53:40 UTC 2018 > > xhost: must be on local machine to add or remove hosts. > > localuser:root being added to access control list > > xhost: must be on local machine to add or remove hosts. > > dbus-update-activation-environment: setting TERM=dumb > > dbus-update-activation-environment: setting SHELL=/bin/bash > > dbus-update-activation-environment: setting SSH_CLIENT=xxxxxxxxx > > dbus-update-activation-environment: setting QT_LINUX_ACCESSIBILITY_ALWAYS_ON=1 > > dbus-update-activation-environment: setting X2GO_SESSION=root-50-1533862411_stDOPENBOX_dp32 > > dbus-update-activation-environment: setting X2GO_AGENT_PID=2339 > > dbus-update-activation-environment: setting USER=root > > dbus-update-activation-environment: setting QT_ACCESSIBILITY=1 > > dbus-update-activation-environment: setting SSH_AUTH_SOCK=/root/.x2go/C-root-50-1533862411_stDOPENBOX_dp32/ssh-agent.PID > > dbus-update-activation-environment: setting PULSE_CLIENTCONFIG=/root/.x2go/C-root-50-1533862411_stDOPENBOX_dp32/.pulse-client.conf > > dbus-update-activation-environment: setting PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin > > dbus-update-activation-environment: setting MAIL=/var/mail/root > > dbus-update-activation-environment: setting PWD=/root > > dbus-update-activation-environment: setting LANG=en_US.UTF-8 > > dbus-update-activation-environment: setting QT_GRAPHICSSYSTEM=native > > dbus-update-activation-environment: setting XSESSION_EXEC=openbox-session > > dbus-update-activation-environment: setting HOME=/root > > dbus-update-activation-environment: setting SHLVL=4 > > dbus-update-activation-environment: setting LOGNAME=root > > dbus-update-activation-environment: setting DBUS_SESSION_BUS_ADDRESS=unix:abstract=/tmp/dbus-O72i0ObC0V,guid=3ac317e9aef52623e8dude291c79955b6ce213 > > dbus-update-activation-environment: setting XDG_DATA_DIRS=/usr/local/share:/usr/share:/var/lib/snapd/desktop > > dbus-update-activation-environment: setting SSH_CONNECTION=xxxxxxxxxxxxxxxx > > dbus-update-activation-environment: setting XDG_RUNTIME_DIR=/run/user/0 > > dbus-update-activation-environment: setting DISPLAY=:50 > > dbus-update-activation-environment: setting STARTUP=/usr/bin/env LD_LIBRARY_PATH= openbox-session > > dbus-update-activation-environment: setting XAUTHORITY=/root/.Xauthority > > dbus-update-activation-environment: setting _=/usr/bin/dbus-update-activation-environment > > dbus-update-activation-environment: warning: error sending to systemd: org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.freedesktop.systemd1 exited with status 1 > > Openbox-Message: Invalid button "A-Left" in mouse binding > > Openbox-Message: Invalid button "A-Middle" in mouse binding > > Openbox-Message: Invalid button "A-Up" in mouse binding > > Openbox-Message: Invalid button "A-Down" in mouse binding > > Openbox-Message: Invalid button "C-A-Up" in mouse binding > > Openbox-Message: Invalid button "C-A-Down" in mouse binding > > Openbox-Message: Invalid button "A-Up" in mouse binding > > Openbox-Message: Invalid button "A-Down" in mouse binding > > No composite extension > > ** (process:2627): WARNING **: Failed to register client: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SessionManager was not provided by any .service files > > Activating service name='org.a11y.atspi.Registry' > > warning : (/build/buildd/cairo-dock-3.4.1/src/implementations/cairo-dock-X-utilities.c:cairo_dock_support_X_extension:729) > > XComposite extension not available. > > warning : (/build/buildd/cairo-dock-3.4.1/src/implementations/cairo-dock-egl.c:gldi_register_egl_backend:232) > > Cairo-Dock was not built with EGL support > > Successfully activated service 'org.a11y.atspi.Registry' > > warning : (/build/buildd/cairo-dock-3.4.1/src/implementations/cairo-dock-glx.c:_initialize_opengl_backend:129) > > couldn't find an appropriate visual, trying to get one without Stencil buffer > > (it may cause some little deterioration in the rendering) ... > > warning : (/build/buildd/cairo-dock-3.4.1/src/implementations/cairo-dock-glx.c:_initialize_opengl_backend:188) > > couldn't find a suitable GLX Visual, OpenGL can't be used. > > (sorry to say that, but your graphic card and/or its driver is crappy) > > ============================================================================ > > Cairo-Dock version : 3.4.1 > > Compiled date : Feb 19 2015 18:17:26 > > Built with GTK : 3.14 > > Running with OpenGL: 0 > > ============================================================================ > > XIO: fatal IO error 0 (Success) on X server ":50" > > after 280 requests (278 known processed) with 0 events remaining.

1 0

Bug#1312: Ubuntu 16.04 LTS Qt bug
by e8dude 09 Aug '18

09 Aug '18

Same here. Upgraded my Ubuntu 16.04 LTS. After the upgrade only some of my QT apps work. Stipend wallet works but Apollon and Deviant do not open at all. Since the update I'm also having high CPU usage in Openbox. Logs are filliing up with Print error while x2go is running. If I close x2go CPU usage is normal and error reporting stops. Here is the .xsession-x2go-errors log of a failed QT app that doesn't open nestled in the gazillion Openbox messages that occur running x2go: > Openbox-Message: Requested key "Print" does not exist on the display > > Openbox-Message: Requested key "Print" does not exist on the display > > Openbox-Message: Requested key "Print" does not exist on the display > > Openbox-Message: Requested key "Print" does not exist on the display > > Openbox-Message: Requested key "Print" does not exist on the display > > XIO: fatal IO error 0 (Success) on X server ":50" > > after 280 requests (278 known processed) with 0 events remaining. > > Openbox-Message: Requested key "Print" does not exist on the display > > Openbox-Message: Requested key "Print" does not exist on the display > > Openbox-Message: Requested key "Print" does not exist on the display > > Openbox-Message: Requested key "Print" does not exist on the display

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

x2go-dev