Re: [X2Go-Dev] GitLab Install LXC - Update (issue)
Hi Uli and the rest, I know that Stefan has some personal issues several months ago. Hopefully he is able to push GitLab towards production and have everybody aligned. I'm ready when you are. See the wiki page for the work packages I identified so far: https://wiki.x2go.org/doku.php/wiki:development:gitlab There is one issue... I noticed that the server is down? https://gitlab.x2go.org/ I was also unable to ping 188.40.111.169. Which is not a good sign?... somebody? Regards, Melroy van den Berg melro...@pm.me ‐‐‐ Original Message ‐‐‐ Op donderdag, april 1, 2021 1:59 PM, Ulrich Sibiller schreef: > Hi, > > any progress on this? > > Uli > > On Tue, Jul 14, 2020 at 6:58 PM Melroy van den Berg > melro...@protonmail.com wrote: > > > Hi Mike and others, > > The latest state is that the installation is indeed working except the > > httpS (SSL) by Let's Encrypt. For some reason the installation fails to > > authenticate/verify itself correctly to the Let's encrypt server. Normally > > this works fine, and you will get a free Let's Encrypt certificate that is > > used by GitLab instance. > > For now the instance is using a self-signed certificate (which is not > > ideal). > > You can execute: 'gitlab-ctl reconfigure' on the VM to trigger a > > certificate deployment of Let's Encrypt. > > Maybe somebody knows why is goes wrong in this VM? > > More info: https://docs.gitlab.com/omnibus/settings/ssl.html > > Off-topic: Too bad I also hurt by wrist, so that is why I take it a bit > > easy now. > > Sorry about that, a wrist injury is taking some time to heal again. :\ > > Kind regards, > > Melroy van den Berg > > ‐‐‐ Original Message ‐‐‐ > > Op dinsdag, juli 7, 2020 11:06 PM, Mike Gabriel > > mike.gabr...@das-netzwerkteam.de schreef: > > > > > HI Melroy, > > > On Di 09 Jun 2020 23:01:24 CEST, Melroy van den Berg wrote: > > > > > > > Hi, > > > > I just discovered that GitLab tries to also set the following during > > > > > "sysctl -e --system" command: > > > > cat /etc/sysctl.d/90-omnibus-gitlab-kernel.sem.conf > > > > kernel.sem = 250 32000 32 262 > > > > And also: > > > > cat /etc/sysctl.d/protect-links.conf > > > > ### > > > > Protected links > > > > > > > > == > > > > Protects against creating or following links under certain conditions > > > > == > > > > Debian kernels have both set to 1 (restricted) > > > > === > > > > See https://www.kernel.org/doc/Documentation/sysctl/fs.txt > > > > === > > > > fs.protected_hardlinks = 1 > > > > fs.protected_symlinks = 1 > > > > You maybe want to change this as well in the host & container? > > > > I disabled the command "reload all sysctrl conf" for now in in the > > > > > GitLab recipes (Ruby code): > > > > /opt/gitlab/embedded/cookbooks/package/recipes/sysctl.rb > > > > As well as, I commented-out where "reload all sysctrl conf" is used in: > > > > /opt/gitlab/embedded/cookbooks/package/resources/gitlab_sysctl.rb > > > > I will create a GitLab issue or comment on an existing GitLab issue > > > > > regarding support LXC containers without this much hassle. > > > > Next issue I'm facing is regarding Let's Encrypt. But the terminal > is > > > > now in use by somebody else... > > > > Regards, > > > > Melroy van den Berg > > > > > > I haven't got back to your mail, I am sorry. > > > Unfortunately, the host hosting gitlab.x2go.org has been taken offline by > > > the provide due to some NIC misconfiguration. We are investigating on > > > that. > > > I'd like to use gitlab.x2go.org starting next week for some new projects > > > related to X2Go. Melroy, do you think the system is already usable (once > > > it's online again)? > > > Sorry, for having not followed up on your work, but I was really busy the > > > last bit of June. > > > Mike > > > > > > DAS-NETZWERKTEAM > > > c\o Technik- und Ökologiezentrum Eckernförde > > > Mike Gabriel, Marienthaler Str. 17, 24340 Eckernförde > > > mobile: +49 (1520) 1976 148 > > > landline: +49 (4351) 850 8940 > > > GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22 0782 9AF4 6B30 2577 1B31 > > > mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de > > > > x2go-dev mailing list > > x2go-dev@lists.x2go.org > > https://lists.x2go.org/listinfo/x2go-dev ___ x2go-dev mailing list x2go-dev@lists.x2go.org https://lists.x2go.org/listinfo/x2go-dev
Re: [X2Go-Dev] X2go client window misplaced in LXQt
Hi Ulrich Sorry, but there are no settings for apps in Lubuntu i.e. under LXQt or under Openbox. The right-click just opens the application. I tried to check this myself, but as Ubuntu 20.04 has dropped Qt4 development support in favor of Qt5, I could not compile the client. I would have added traces on places, where the "sizes" file is read and written. BR, Kalle On Wed, 31 Mar 2021 at 13:57, Ulrich Sibiller wrote: > I am not ware of this specific problem but I have such crude behaviour > with the NX window in Windows, too. > > https://stackoverflow.com/questions/42473554/windows-10-screen-coordinates-are-offset-by-7 > says that Windows changed behaviour regarding border width. Maybe this > can be solved in the compatibility settings for the app (right click > on Icon, Properties, Compatiblity). > > Uli > > On Wed, Mar 31, 2021 at 12:29 PM Kalle Tuulos > wrote: > > > > I'm running Lubuntu 20.04, which has LXQt. The X2go client has been > installed using apt method, current version is 4.1.2.2. > > > > When the X2Go client is opened and closed, on the next time, it will > open on 30 pixels higher and 2 pixels left position, than the earlier > position. This can be seen from file ~/.x2goclient/sizes: > > > > Before opened: > > [mainwindow] > > maximized=false > > pos=@Point(275 170) > > size=@Size(1017 600) > > > > Window is not moved, just closed: > > [mainwindow] > > maximized=false > > pos=@Point(273 140) > > size=@Size(1017 600) > > > > Opened and closed again, not moved: > > [mainwindow] > > maximized=false > > pos=@Point(271 110) > > size=@Size(1017 600) > > > > This same problem is in many Qt based applications, so this is not X2go > problem as such, but on the Qt framework. Also, this same problem was > already on 18.04 version of Ubuntu, on another computers. I have a > workaround for this - the sizes files is overwritten on each login with a > valid one. > > > > Is there any more clever fix for this? > > > > BR, > >Kalle > > > > -- > > - Kalle > > ___ > > x2go-dev mailing list > > x2go-dev@lists.x2go.org > > https://lists.x2go.org/listinfo/x2go-dev > ___ x2go-dev mailing list x2go-dev@lists.x2go.org https://lists.x2go.org/listinfo/x2go-dev
Re: [X2Go-Dev] GitLab Install LXC - Update (issue)
Hi, any progress on this? Uli On Tue, Jul 14, 2020 at 6:58 PM Melroy van den Berg wrote: > > Hi Mike and others, > > The latest state is that the installation is indeed working except the httpS > (SSL) by Let's Encrypt. For some reason the installation fails to > authenticate/verify itself correctly to the Let's encrypt server. Normally > this works fine, and you will get a free Let's Encrypt certificate that is > used by GitLab instance. > For now the instance is using a self-signed certificate (which is not ideal). > > You can execute: 'gitlab-ctl reconfigure' on the VM to trigger a certificate > deployment of Let's Encrypt. > Maybe somebody knows why is goes wrong in this VM? > > More info: https://docs.gitlab.com/omnibus/settings/ssl.html > > Off-topic: Too bad I also hurt by wrist, so that is why I take it a bit easy > now. > Sorry about that, a wrist injury is taking some time to heal again. :\ > > > Kind regards, > Melroy van den Berg > > ‐‐‐ Original Message ‐‐‐ > Op dinsdag, juli 7, 2020 11:06 PM, Mike Gabriel > schreef: > > > HI Melroy, > > > > On Di 09 Jun 2020 23:01:24 CEST, Melroy van den Berg wrote: > > > > > Hi, > > > I just discovered that GitLab tries to also set the following during > > > > "sysctl -e --system" command: > > > cat /etc/sysctl.d/90-omnibus-gitlab-kernel.sem.conf > > > kernel.sem = 250 32000 32 262 > > > And also: > > > cat /etc/sysctl.d/protect-links.conf > > > ### > > > > > > Protected links > > > > > > > > > > > > == > > > > > > Protects against creating or following links under certain conditions > > > > > > == > > > > > > Debian kernels have both set to 1 (restricted) > > > > > > === > > > > > > See https://www.kernel.org/doc/Documentation/sysctl/fs.txt > > > > > > === > > > > > > fs.protected_hardlinks = 1 > > > fs.protected_symlinks = 1 > > > You maybe want to change this as well in the host & container? > > > I disabled the command "reload all sysctrl conf" for now in in the > > > > GitLab recipes (Ruby code): > > > /opt/gitlab/embedded/cookbooks/package/recipes/sysctl.rb > > > As well as, I commented-out where "reload all sysctrl conf" is used in: > > > /opt/gitlab/embedded/cookbooks/package/resources/gitlab_sysctl.rb > > > I will create a GitLab issue or comment on an existing GitLab issue > > > > regarding support LXC containers without this much hassle. > > > Next issue I'm facing is regarding Let's Encrypt. But the terminal > is > > > now in use by somebody else... > > > Regards, > > > Melroy van den Berg > > > > I haven't got back to your mail, I am sorry. > > > > Unfortunately, the host hosting gitlab.x2go.org has been taken offline by > > the provide due to some NIC misconfiguration. We are investigating on that. > > > > I'd like to use gitlab.x2go.org starting next week for some new projects > > related to X2Go. Melroy, do you think the system is already usable (once > > it's online again)? > > > > Sorry, for having not followed up on your work, but I was really busy the > > last bit of June. > > > > Mike > > > > > > > > DAS-NETZWERKTEAM > > c\o Technik- und Ökologiezentrum Eckernförde > > Mike Gabriel, Marienthaler Str. 17, 24340 Eckernförde > > mobile: +49 (1520) 1976 148 > > landline: +49 (4351) 850 8940 > > > > GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22 0782 9AF4 6B30 2577 1B31 > > mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de > > > ___ > x2go-dev mailing list > x2go-dev@lists.x2go.org > https://lists.x2go.org/listinfo/x2go-dev ___ x2go-dev mailing list x2go-dev@lists.x2go.org https://lists.x2go.org/listinfo/x2go-dev
[X2Go-Dev] Bug#1533: Bug#1533: Mac client: connection timeout 30 seconds after session start
Try to upgrade nxagent on the server to 3.5.99.26 and see it this helps. See https://github.com/ArcticaProject/nx-libs/blob/3.6.x/README.md for instructions where to find a current binary package. Uli On Fri, Mar 19, 2021 at 5:50 PM Ricky Charlet wrote: > > Package: unknown > Version: 4.1.2.2 > > > Howdy, > > When I connect from Mac client to ubuntu server, I get a “connection timeout” > 30 seconds after “connection start.” Other people can connect to my server. > > Error message is: > Loop: WARNING! Overriding auxiliary X11 port with new value '1'. > Warning: Overriding auxiliary X11 port with new value '1'. > Info: Connecting to remote host 'localhost:36652'. > Info: Connected to remote proxy on FD#11. > Info: Connection with remote proxy completed. > Loop: WARNING! Unrecognized session type 'unix-kde-depth_32'. Assuming agent > session. > Warning: Unrecognized session type 'unix-kde-depth_32'. Assuming agent > session. > Info: Using ADSL link parameters 1408/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.E12k8P0IX6/org.xquartz:0'. > Info: Forwarding auxiliary X11 connections to display > '/private/tmp/com.apple.launchd.E12k8P0IX6/org.xquartz:0'. > Session: Session started at 'Fri Mar 19 09:38:16 2021'. > Connection timeout, abortingSession: Terminating session at 'Fri Mar 19 > 09:38:46 2021'. > Info: Waiting the cleanup timeout to complete. > Session: Session terminated at 'Fri Mar 19 09:38:47 2021'. > > > > On the server, in /var/log/messages, I get what appears to be a success > report: > Mar 19 09:38:16 hpnsw4371 /usr/bin/x2gostartagent: successfully started X2Go > Agent session with ID charletr-50-1616171893_stDMATE_dp32 > > > I have a tcpdump (is in an ssh tunnel, to a little vague) which shows client > sending dup packet not quite, but almost 30 seconds into session attempt. > 116 33.763841 15.116.49.166 16.99.147.244 SSHv2 108 Server: [TCP Spurious > Retransmission] , Encrypted packet (len=64) > 117 33.763941 16.99.147.244 15.116.49.166 TCP 56 [TCP Dup ACK 114#1] 64138 → > 22 [ACK] Seq=3239 Ack=5027 Win=262144 Len=0 SLE=4963 SRE=5027 > > > Client = MacOS 10.15.7 (Catalina…and due to corp policy, I cannot upgrade); > x2go 4.1.2.2 with qt 4.8.7 with xquartz 2.7.11 with xorg 1.18.4 > > Server : x2goversion > : 1.0.2.4 > : 0.0.1.6 > : 4.1.0.3 > : 4.1.0.3 > : 4.1.0.3 > : 4.1.0.3 > : 4.1.0.3 > : 3.5.99.22 > : 4.1.0.3 > > > ___ > x2go-dev mailing list > x2go-dev@lists.x2go.org > https://lists.x2go.org/listinfo/x2go-dev ___ x2go-dev mailing list x2go-dev@lists.x2go.org https://lists.x2go.org/listinfo/x2go-dev
Re: [X2Go-Dev] x2goagent segfaults with x2goclient from ubuntu 20.10
Oh, I am just seeing this mail today! There's a logfile of x2goagent on the server side. You can find it in ~/.x2go/C-.../session.log I am not sure if it will be deleted in your scenario so please try to find it for a crashing session and post the last then or so lines. Uli On Sun, Mar 7, 2021 at 4:59 PM Kenneth Johansson wrote: > > so I have been using x2go for years and its works fine for what I need > but today it stopped working. > > the error message was not really clear so I deleted and reinstalled > (server and client) but still no go. Turns out its the x2goagent that > segfaults on the server side. > > The client is an ubuntu 20.10 and the servers I tested with is debian 10 > and ubuntu 20.04. To make sure that there was no version mismatch I then > installed the server on the ubuntu 20.10 computer and tried to connect > to localhost and still get the segfault. > > how to debug this ?? what I try to do is use a single application and > start "command=/usr/bin/xterm" > > since its not working even to localhost this should be something that a > lot more people have a problem with than just me. I have deleted all > configurations for both server and client and the only thing I change > when I create a new session is the > > host > > login > > session type. > > So I do not see how I could have made something wrong here. > > > ___ > x2go-dev mailing list > x2go-dev@lists.x2go.org > https://lists.x2go.org/listinfo/x2go-dev ___ x2go-dev mailing list x2go-dev@lists.x2go.org https://lists.x2go.org/listinfo/x2go-dev
