Re: [X2Go-User] X2Go TCE pxe complications

[ovt]

I want to clarify my previous post:The /opt/[2gothinkclient folder should be about 1.5 GB after the thin client image is created. 30.01.2022, 15:18, "o...@zaokknm.ru" :First of all, I inform you that the descriptions of the errors refer to the creation of a thin client image for OS Debian_10 64 bit. I got them comparing x2gothinclient_create script for 32bit and 64bit. I also report that Debian_10 32 bit had no image creation errors and booted normally the first time, but this was true for April 2020. In principle, I still have these scripts, but I cannot guarantee their performance at the moment.I want to note that the capacity of the image should be about 1.5 GB.Also... in your case with a weak thin client, I would recommend creating an image for 32 bit Debian OS. I insist on Debian.Or, as a proven option, hang up hdd or usb on a thin client, put Pupy and a regular x2go client there. 30.01.2022, 06:40, "MacGregor Family" :Thank you for this info, I've had a little break and now on back on theproject. As far as I can see these lines have been added to thex2gothinclient_create script already, perhaps when you reported theproblem. I have attached a couple of screen shots showing them. Arethese lines now correct or am I missing something?I recreated the thin client using "stretch" and the boot progressedfurther, but was still unsuccessful. This time the error message was:[FAILED] Failed to start. Create volatile files and directoriesI changed the operating system on the thin client to Tiny Core Linuxand it sped up the whole process, however reached the sameconclusion.I'm going to try to base the thin client on "Jessie" andchange all the repository references to the archived ones, however Idon't hold much hope. I looked for an x2goclient package for Tiny Corehowever it looks like if I want one I need to create the Tiny Coreextension myself and this may well be beyond my limited competance.Might give it a go if the all else fails.Thanks again for replying.RegardsStuart MacGregor On Wed, 2022-01-19 at 22:30 +0300, o...@zaokknm.ru wrote: I remember this trick with the pxelinux.cfg folder. :-)) If you are at this stage, then this is only the beginning of the journey. I do not know how to find my correspondence in the x2go-user thread, so I quote from my letter - --- Without waiting for an answer, I report the errors found in the /usr/sbin/x2gothinclient_create script. Skipped lines (206-207) [ $? -eq 0] && apt-get install gnupg -y [ $? -eq 0] && apt-key adv --recv-keys --keyserver keys.gnupg.net E1F958385BFE2B6E (251)[ $? -eq 0] && systemctl enable x2gothinclient-displaymanager   After adding these lines, x2gothinclient loads fine. Please make these corrections. --- P.S.The documentation says that the thin client RAM must be at least 512 MB. I haven't tried it with low RAM, but it makes sense   12.01.2022, 14:12, "MacGregor Family" : > Thank you for the excellent advice. I switched the virtual machine > acting as my tftp server to Debian 11 and pxe boot started. I > didn't event need to chainload ipxe with undionly.kpxe. Basically > using Ubuntu for my tftp server was the problem. > > Something of note, though. It was necessary create a new directory > /srv/tftp/pxelinux.cfg and copy /srv/tftp/default.cfg into it. I > discovered this by consulting professor Google. I did not read this > in the classic X2go-tce documentation. Perhaps this might be > explictly added to this documention to help nubes like myself? > > I am having more problems, though. The first, red X2go splash > screen comes up but I am unable to make any selections, not with > the highlighted hotkeys nor with the arrow keys or even TAB. Not a > real problem, after timeout it defaults to x2go-tce which is what I > want anyway. I just mention it in case it is a symptom of the other > problems I'm about to describe. The boot soon fails with the > following messages: > > [ 16.996870] Initramfs unpacking failed : write error > [ 17.488013] mce: Unable to init MCE device (rc: -5) > [ 19.959922] Failed to execute /init (error -2) > [ 19.190964] Kernel panic - not syncing: No working init found. Try > passing init =option to Kernel. See Linux Documentation/admin- > guide/initrst for guidance. > [ 19.961064] CPU: 0 PID : 1 Comm: swapper/0 Not tainted 5.10.0-10- > 686 #1 Debian 5.10.84-1 > [ 19.961135] Hardware name: /TK-3550, BIOS 6.00 PG 02/27/2009 > [ 19.961198] Call Trace: > [ 19.961283] dump_stack+0x54/0x68 > [ 19.961355] ? rest_init+0x30/0x97 > [ 19.961429] panic+0xa3/0x25b > [ 19.961495] ? rest_init+0xe0/0xe9 > [ 19.961630] ret_from_fork+0x1c/0x28 > [ 19.961705] Kernel Offset: disabled > [ 19.961775] ---[ end Kernel panic - not syncing: No working init > found. Try passing init =option to Kernel. See Linux > Documentation/admin-guide/initrst for guidance. ]--- > > Then the whole thing hangs up ind

Re: [X2Go-User] X2Go TCE pxe complications

[ovt]

First of all, I inform you that the descriptions of the errors refer to the creation of a thin client image for OS Debian_10 64 bit. I got them comparing x2gothinclient_create script for 32bit and 64bit. I also report that Debian_10 32 bit had no image creation errors and booted normally the first time, but this was true for April 2020. In principle, I still have these scripts, but I cannot guarantee their performance at the moment.I want to note that the capacity of the image should be about 1.5 GB.Also... in your case with a weak thin client, I would recommend creating an image for 32 bit Debian OS. I insist on Debian.Or, as a proven option, hang up hdd or usb on a thin client, put Pupy and a regular x2go client there. 30.01.2022, 06:40, "MacGregor Family" :Thank you for this info, I've had a little break and now on back on theproject. As far as I can see these lines have been added to thex2gothinclient_create script already, perhaps when you reported theproblem. I have attached a couple of screen shots showing them. Arethese lines now correct or am I missing something?I recreated the thin client using "stretch" and the boot progressedfurther, but was still unsuccessful. This time the error message was:[FAILED] Failed to start. Create volatile files and directoriesI changed the operating system on the thin client to Tiny Core Linuxand it sped up the whole process, however reached the sameconclusion.I'm going to try to base the thin client on "Jessie" andchange all the repository references to the archived ones, however Idon't hold much hope. I looked for an x2goclient package for Tiny Corehowever it looks like if I want one I need to create the Tiny Coreextension myself and this may well be beyond my limited competance.Might give it a go if the all else fails.Thanks again for replying.RegardsStuart MacGregor On Wed, 2022-01-19 at 22:30 +0300, o...@zaokknm.ru wrote: I remember this trick with the pxelinux.cfg folder. :-)) If you are at this stage, then this is only the beginning of the journey. I do not know how to find my correspondence in the x2go-user thread, so I quote from my letter - --- Without waiting for an answer, I report the errors found in the /usr/sbin/x2gothinclient_create script. Skipped lines (206-207) [ $? -eq 0] && apt-get install gnupg -y [ $? -eq 0] && apt-key adv --recv-keys --keyserver keys.gnupg.net E1F958385BFE2B6E (251)[ $? -eq 0] && systemctl enable x2gothinclient-displaymanager   After adding these lines, x2gothinclient loads fine. Please make these corrections. --- P.S.The documentation says that the thin client RAM must be at least 512 MB. I haven't tried it with low RAM, but it makes sense   12.01.2022, 14:12, "MacGregor Family" : > Thank you for the excellent advice. I switched the virtual machine > acting as my tftp server to Debian 11 and pxe boot started. I > didn't event need to chainload ipxe with undionly.kpxe. Basically > using Ubuntu for my tftp server was the problem. > > Something of note, though. It was necessary create a new directory > /srv/tftp/pxelinux.cfg and copy /srv/tftp/default.cfg into it. I > discovered this by consulting professor Google. I did not read this > in the classic X2go-tce documentation. Perhaps this might be > explictly added to this documention to help nubes like myself? > > I am having more problems, though. The first, red X2go splash > screen comes up but I am unable to make any selections, not with > the highlighted hotkeys nor with the arrow keys or even TAB. Not a > real problem, after timeout it defaults to x2go-tce which is what I > want anyway. I just mention it in case it is a symptom of the other > problems I'm about to describe. The boot soon fails with the > following messages: > > [ 16.996870] Initramfs unpacking failed : write error > [ 17.488013] mce: Unable to init MCE device (rc: -5) > [ 19.959922] Failed to execute /init (error -2) > [ 19.190964] Kernel panic - not syncing: No working init found. Try > passing init =option to Kernel. See Linux Documentation/admin- > guide/initrst for guidance. > [ 19.961064] CPU: 0 PID : 1 Comm: swapper/0 Not tainted 5.10.0-10- > 686 #1 Debian 5.10.84-1 > [ 19.961135] Hardware name: /TK-3550, BIOS 6.00 PG 02/27/2009 > [ 19.961198] Call Trace: > [ 19.961283] dump_stack+0x54/0x68 > [ 19.961355] ? rest_init+0x30/0x97 > [ 19.961429] panic+0xa3/0x25b > [ 19.961495] ? rest_init+0xe0/0xe9 > [ 19.961630] ret_from_fork+0x1c/0x28 > [ 19.961705] Kernel Offset: disabled > [ 19.961775] ---[ end Kernel panic - not syncing: No working init > found. Try passing init =option to Kernel. See Linux > Documentation/admin-guide/initrst for guidance. ]--- > > Then the whole thing hangs up indefinitely. It seems to me that the > old thin client (TK-3550 AMD GX III LX800 CPU, 256 MB ram) needs a > legacy BIOS boot and this is unavailable for some reason. Should I > redo my X2go-tce setup 

Re: [X2Go-User] X2Go TCE pxe complications

[ovt]

I remember this trick with the pxelinux.cfg folder. :-))If you are at this stage, then this is only the beginning of the journey.I do not know how to find my correspondence in the x2go-user thread, so I quote from my letter Without waiting for an answer, I report the errors found in the /usr/sbin/x2gothinclient_create script.Skipped lines (206-207)[ $? -eq 0] && apt-get install gnupg -y[ $? -eq 0] && apt-key adv --recv-keys --keyserver keys.gnupg.net E1F958385BFE2B6E(251)[ $? -eq 0] && systemctl enable x2gothinclient-displaymanager After adding these lines, x2gothinclient loads fine. Please make these corrections.---P.S.The documentation says that the thin client RAM must be at least 512 MB. I haven't tried it with low RAM, but it makes sense 12.01.2022, 14:12, "MacGregor Family" :Thank you for the excellent advice. I switched the virtual machine acting as my tftp server to Debian 11 and pxe boot started. I didn't event need to chainload ipxe with undionly.kpxe. Basically using Ubuntu for my tftp server was the problem. Something of note, though. It was necessary create a new directory /srv/tftp/pxelinux.cfg and copy /srv/tftp/default.cfg into it. I discovered this by consulting professor Google. I did not read this in the classic X2go-tce documentation. Perhaps this might be explictly added to this documention to help nubes like myself? I am having more problems, though. The first, red X2go splash screen comes up but I am unable to make any selections, not with the highlighted hotkeys nor with the arrow keys or even TAB. Not a real problem, after timeout it defaults to x2go-tce which is what I want anyway. I just mention it in case it is a symptom of the other problems I'm about to describe. The boot soon fails with the following messages: [  16.996870] Initramfs unpacking failed : write error[  17.488013] mce: Unable to init MCE device (rc: -5)[ 19.959922] Failed to execute /init (error -2)[ 19.190964] Kernel panic - not syncing: No working init found. Try passing init =option to Kernel. See Linux Documentation/admin-guide/initrst for guidance.[ 19.961064] CPU: 0 PID : 1 Comm: swapper/0 Not tainted 5.10.0-10-686 #1 Debian 5.10.84-1[ 19.961135] Hardware name: /TK-3550, BIOS 6.00 PG 02/27/2009[ 19.961198] Call Trace:[ 19.961283]  dump_stack+0x54/0x68[ 19.961355]  ? rest_init+0x30/0x97[ 19.961429]  panic+0xa3/0x25b[ 19.961495]  ? rest_init+0xe0/0xe9[ 19.961630]  ret_from_fork+0x1c/0x28[ 19.961705] Kernel Offset: disabled[ 19.961775] ---[ end Kernel panic - not syncing: No working init found. Try passing init =option to Kernel. See Linux Documentation/admin-guide/initrst for guidance. ]--- Then the whole thing hangs up indefinitely. It seems to me that the old thin client (TK-3550 AMD GX III LX800 CPU, 256 MB ram) needs a legacy BIOS boot and this is unavailable for some reason. Should I redo my X2go-tce setup (x2gothinclient_settings) and use an older version of Debian to create the chroot image? I used the default "Buster". If I need to go back enough versions of Debian will I need to change to archived repositories in the same file (rather than just http://ftp.debian.ors/debian  main)? Do I need to add to the APPEND line of x2go-tce.cfg instead with init=/sbin/ or some such (professor Google again)? Once again any help here would be appreciated. I recognise that the thin client I am using is rubbish but the price was right and having come so far I'm reluctant to give up now.   On Mon, 2022-01-10 at 10:01 +0300, o...@zaokknm.ru wrote:At one time, when, about a year ago, while installing x2go on ubuntu, I faced about the same problem. Nevertheless, in a week I was able to run x2go-server + pxe. Endless poking around in the configuration files gave me the idea to change the distribution kit. Imagine my surprise when, in 30-40 minutes, I installed and configured this bundle on Debian_10 without any problems and have already been using it with 20 clients for a whole year. I also did not find understanding and help in the x2go community.My advice to you is to change your distribution to Debian.  05.01.2022, 15:38, "MacGregor Family" :Hello,I posted an enquiry quite some time ago but it hasn't attractedanyone's interest. In the meantime I have contiued trying to solve theproblem on my own. I moved all my dchp functions from my cheap, rubbishrouter to my ubuntu 20.04 server. I spent some time fiddling with thesettings of isc-dhcp-server. I downloaded ipxe undionly.kpxe and put itin my tftp server (a virual box virtual machine with bridged netwrkingalso running a ubuntu 20.04 server) at /srv/tftp. When I boot up myTermtek TK3550 Thin Client (AMD GX III LX800 CPU, 256 MB ram, IntelUNDI network card PXE 2.0) undionly.kpxe is successfully booted viatftp and the new bootloder finds pxelinux.0 then just locks up. Nothinghappens and it continues to happen indefinitely. I have attached aph

Re: [X2Go-User] X2Go TCE pxe complications

[ovt]

At one time, when, about a year ago, while installing x2go on ubuntu, I faced about the same problem. Nevertheless, in a week I was able to run x2go-server + pxe. Endless poking around in the configuration files gave me the idea to change the distribution kit. Imagine my surprise when, in 30-40 minutes, I installed and configured this bundle on Debian_10 without any problems and have already been using it with 20 clients for a whole year. I also did not find understanding and help in the x2go community.My advice to you is to change your distribution to Debian.05.01.2022, 15:38, "MacGregor Family" :Hello,I posted an enquiry quite some time ago but it hasn't attractedanyone's interest. In the meantime I have contiued trying to solve theproblem on my own. I moved all my dchp functions from my cheap, rubbishrouter to my ubuntu 20.04 server. I spent some time fiddling with thesettings of isc-dhcp-server. I downloaded ipxe undionly.kpxe and put itin my tftp server (a virual box virtual machine with bridged netwrkingalso running a ubuntu 20.04 server) at /srv/tftp. When I boot up myTermtek TK3550 Thin Client (AMD GX III LX800 CPU, 256 MB ram, IntelUNDI network card PXE 2.0) undionly.kpxe is successfully booted viatftp and the new bootloder finds pxelinux.0 then just locks up. Nothinghappens and it continues to happen indefinitely. I have attached aphoto of the boot screen when it locks up.I have created a directory of the tftp server /srv/tftp/pxelinux.cfg .I copied /srv/tftp/default.cfg into this directory both as default.cfgand as simply default. I also copied x2go-tce-cfg, memtest.cfg andlocal-boot.cfg into this directory just in case. I am now at a loss. Ihave no way of checking/altering pxelinux.0 as it is in binary or codeof some sort. I have spent hours in my free time to get this far, butin reality the end goal of logging into my linux server on a thinclient seems no closer. Any help would be appreciated.Stuart MacGregormacgregorath...@iinet.net.au,___x2go-user mailing listx2go-user@lists.x2go.orghttps://lists.x2go.org/listinfo/x2go-user___
x2go-user mailing list
x2go-user@lists.x2go.org
https://lists.x2go.org/listinfo/x2go-user

Re: [X2Go-User] Turn off the computer after the time has elapsed.

[ovt]

Unfortunately, this method is unacceptable for thin clients, but suggested using crontab.Here is a working script for cron shutdown: # shutdown x2gothinclient if not X-sessionXSES=`ps ax | grep X |sed -n '/nxproxy/p'`[ -n "$XSES" ] && echo "XORG run ! " || shutdown -h now  21.08.2021, 18:41, "Mike Gabriel" :On Fr 20 Aug 2021 09:41:30 CEST, ovt wrote:  We need a script for a thin client: If within 10 minutes the user has not opened a session, turn off the computer.You could install shutdown-at-night [1] on those thinclients and callthe script every 20 minutes.The shutdown-at-night package might need some adjustments, though fordetecting that someone is logged in via X2Go or not. Theshutdown-at-night tool works great on desktop computers.Mike[1] https://packages.debian.org/sid/shutdown-at-night--DAS-NETZWERKTEAMc\o Technik- und Ökologiezentrum EckernfördeMike Gabriel, Marienthaler Str. 17, 24340 Eckernfördemobile: +49 (1520) 1976 148landline: +49 (4351) 850 8940GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22 0782 9AF4 6B30 2577 1B31mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de___
x2go-user mailing list
x2go-user@lists.x2go.org
https://lists.x2go.org/listinfo/x2go-user

[X2Go-User] Turn off the computer after the time has elapsed.

[ovt]

We need a script for a thin client:If within 10 minutes the user has not opened a session, turn off the computer.
___
x2go-user mailing list
x2go-user@lists.x2go.org
https://lists.x2go.org/listinfo/x2go-user

[X2Go-User] How to access a thin client computer via ssh for administrative tasks?

[ovt]

PXE -nfs.How to access a thin client computer via ssh for administrative tasks?
___
x2go-user mailing list
x2go-user@lists.x2go.org
https://lists.x2go.org/listinfo/x2go-user

[X2Go-User] x2gothinclient TCE-nfs -x-session break

[ovt]

 On x2gothinclients, the x session crashes randomly. Unexpectedly, a screen crashes on tty1, from which it is impossible to access the x-session x2gothinclient. In this case, the session on the server exists and you can connect via x2gosharingdesktop.It is impossible to find a pattern - this happens in the absence of actions and (or) when working in any program. Decision:Experimentally, I found out the reason for the loss of the display in the x-session. Increasing the poll up to 3 seconds in the file /opt/x2gothinclient/chroot/usr/sbin/x2gothinclientd in the block:Elsif ($ pid == 0) - line 87 Replace: while (sleep 1) -line 96On:         while (sleep 3) Solved the problem.
___
x2go-user mailing list
x2go-user@lists.x2go.org
https://lists.x2go.org/listinfo/x2go-user

[X2Go-User] x2gousbmounts fail

[ovt]

​On x2gothinclients, when a usb-disk is added, the / media folder is created in the client's home directory, and the name of the inserted disk appears for a second in the / rm folder, and then disappears. Writes to / var / log / usb that the disk is mounted. The / syslog also contains an entry about the mounted disk, but judging by the x2gousbmount script, a file should also appear in /var/run/sdb1.mounted, which is not there.There is a disk in the / media root, but the files are not there.P.S. At the first mount, the usb-disk was, but did not show the files, as if it was empty. On next reconnections, the disk no longer appears. Other discs behave the same way.Help me !!! x2goserver syslog:6 11:48:24 debian systemd[840]: run-user-1015-gvfs.mount: Succeeded.Jul  6 11:48:24 debian systemd[838]: run-user-1015-gvfs.mount: Succeeded.Jul  6 11:48:24 debian systemd[1024]: run-user-1015-gvfs.mount: Succeeded.Jul  6 11:48:24 debian systemd[836]: run-user-1015-gvfs.mount: Succeeded.Jul  6 11:48:24 debian systemd[834]: run-user-1015-gvfs.mount: Succeeded.Jul  6 11:48:24 debian systemd[837]: run-user-1015-gvfs.mount: Succeeded.Jul  6 11:48:24 debian systemd[1]: run-user-1015-gvfs.mount: Succeeded.Jul  6 11:48:24 debian systemd[833]: run-user-1015-gvfs.mount: Succeeded.Jul  6 11:48:36 debian systemd[1]: session-307.scope: Succeeded.Jul  6 11:48:47 debian systemd[1]: Started Session 315 of user tb.Jul  6 11:48:50 debian /usr/sbin/x2gocleansessions[986]: tb-51-1625561329_stDMATE_dp24: state file for this session does not exist: /tmp/.x2go-tb/C-tb-51-1625561329_stDMATE_dp24/state (this can be ignored during session startups)Jul  6 11:48:51 debian /usr/bin/x2gostartagent: successfully started X2Go Agent session with ID tb-51-1625561329_stDMATE_dp24Jul  6 11:48:53 debian systemd[834]: tmp-.x2go\x2dtb-spool-C\x2dtb\x2d51\x2d1625561329_stDMATE_dp24.mount: Succeeded.Jul  6 11:48:53 debian systemd[1024]: tmp-.x2go\x2dtb-spool-C\x2dtb\x2d51\x2d1625561329_stDMATE_dp24.mount: Succeeded.Jul  6 11:48:53 debian systemd[58140]: tmp-.x2go\x2dtb-spool-C\x2dtb\x2d51\x2d1625561329_stDMATE_dp24.mount: Succeeded.Jul  6 11:48:53 debian systemd[840]: tmp-.x2go\x2dtb-spool-C\x2dtb\x2d51\x2d1625561329_stDMATE_dp24.mount: Succeeded.Jul  6 11:48:53 debian systemd[838]: tmp-.x2go\x2dtb-spool-C\x2dtb\x2d51\x2d1625561329_stDMATE_dp24.mount: Succeeded.Jul  6 11:48:53 debian systemd[837]: tmp-.x2go\x2dtb-spool-C\x2dtb\x2d51\x2d1625561329_stDMATE_dp24.mount: Succeeded.Jul  6 11:48:53 debian systemd[1]: tmp-.x2go\x2dtb-spool-C\x2dtb\x2d51\x2d1625561329_stDMATE_dp24.mount: Succeeded.Jul  6 11:48:53 debian systemd[833]: tmp-.x2go\x2dtb-spool-C\x2dtb\x2d51\x2d1625561329_stDMATE_dp24.mount: Succeeded.Jul  6 11:48:53 debian systemd[836]: tmp-.x2go\x2dtb-spool-C\x2dtb\x2d51\x2d1625561329_stDMATE_dp24.mount: Succeeded.Jul  6 11:48:53 debian /usr/bin/x2gomountdirs[33362]: WARNING: mounting of /var/lib/x2gothinclient/.x2go/S-tb-51-1625561329_stDMATE_dp24/spool failedJul  6 11:48:53 debian /usr/bin/x2goruncommand: launching session with Xsession-x2go mechanism, using STARTUP="mate-session"Jul  6 11:48:53 debian /usr/bin/x2goruncommand: dbus wrapper available as /usr/bin/dbus-run-sessionJul  6 11:48:55 debian mate-session[33552]: WARNING: Unable to find provider '' of required component 'dock'Jul  6 11:48:55 debian systemd[837]: Starting Sound Service Jul  6 12:03:07 debian systemd[836]: tmp-.x2go\x2dtb-media-rm-_media__USB_DISK_30X_sdb1.mount: Succeeded.Jul  6 12:03:07 debian systemd[840]: tmp-.x2go\x2dtb-media-rm-_media__USB_DISK_30X_sdb1.mount: Succeeded.Jul  6 12:03:07 debian systemd[1]: tmp-.x2go\x2dtb-media-rm-_media__USB_DISK_30X_sdb1.mount: Succeeded.Jul  6 12:03:07 debian systemd[1024]: tmp-.x2go\x2dtb-media-rm-_media__USB_DISK_30X_sdb1.mount: Succeeded.Jul  6 12:03:07 debian systemd[833]: tmp-.x2go\x2dtb-media-rm-_media__USB_DISK_30X_sdb1.mount: Succeeded.Jul  6 12:03:07 debian systemd[834]: tmp-.x2go\x2dtb-media-rm-_media__USB_DISK_30X_sdb1.mount: Succeeded.Jul  6 12:03:07 debian systemd[58140]: tmp-.x2go\x2dtb-media-rm-_media__USB_DISK_30X_sdb1.mount: Succeeded.Jul  6 12:03:07 debian systemd[837]: tmp-.x2go\x2dtb-media-rm-_media__USB_DISK_30X_sdb1.mount: Succeeded.Jul  6 12:03:07 debian systemd[838]: tmp-.x2go\x2dtb-media-rm-_media__USB_DISK_30X_sdb1.mount: Succeeded.Jul  6 12:03:07 debian systemd[834]: tmp-.x2go\x2dtb-media-rm-_media__USB_DISK_30X_multisystem.mount: Succeeded.Jul  6 12:03:07 debian systemd[833]: tmp-.x2go\x2dtb-media-rm-_media__USB_DISK_30X_multisystem.mount: Succeeded.Jul  6 12:03:07 debian systemd[1024]: tmp-.x2go\x2dtb-media-rm-_media__USB_DISK_30X_multisystem.mount: Succeeded.Jul  6 12:03:07 debian systemd[840]: tmp-.x2go\x2dtb-media-rm-_media__USB_DISK_30X_multisystem.mount: Succeeded.Jul  6 12:03:07 debian systemd[1]: tmp-.x2go\x2dtb-media-rm-_media__USB_DISK_30X_multisystem.mount: Succeeded.Jul  6 12:03:07 debian systemd[58140]: tmp-.x2go\x2dtb-media-rm-_media__USB_DISK_30X_multisystem.mount: Succeeded.Jul  6 12:03:07 d

[X2Go-User] x2gothinclient TCE-nfs x2gothinclient_usbmount

[ovt]

On x2gothinclients, when a usb-disk is added, a /media folder is created in the client's home directory, and the name of the inserted disk appears for a second in the /rm folder, and then disappears. Writes to /var /log /usb that the disk is mounted. The  syslog also contains an entry about the mounted disk, but judging by the x2gousbmount script, a file should also have appeared in /var/run/sdb1.mounted, which is not there.There is a disk in the /media root, but the files are not there.P.S. At the first mount, the usb-disk was, but did not show the files, as if it was empty. On next reconnections, the disk no longer appears. Other discs behave the same way.___
x2go-user mailing list
x2go-user@lists.x2go.org
https://lists.x2go.org/listinfo/x2go-user

[X2Go-User] x2gothinclient TCE-nfs -x-session break

[ovt]

On x2gothinclients, the x session is terminated randomly. The screen crashes unexpectedly on tty1, from which it is impossible to access the x-session x2gothinclient. In this case, the session on the server exists and you can connect via x2gosharingdesktop.It is not possible to find a pattern - this happens in the absence of actions and (or) when working in any program. Sometimes there are no failures in a few hours of operation. How and where can you calculate the reason for the failure of the x-session?
___
x2go-user mailing list
x2go-user@lists.x2go.org
https://lists.x2go.org/listinfo/x2go-user

[X2Go-User] x2gothinclient TCE-nfs -Session break

[ovt]

On x2gothinclients, the x-session is broken randomly. The screen drops unexpectedly in tty1 from which x2gothinclient cannot be accessed. It is not possible to find a pattern - this happens in the absence of actions and (or) while working in any program. Sometimes there are no failures for several hours of operation. How can you trace the reason for the failure of the x-session?
___
x2go-user mailing list
x2go-user@lists.x2go.org
https://lists.x2go.org/listinfo/x2go-user

[X2Go-User] poweroff x2gothinclient

[ovt]

Logging out of the x2gothinclient session to the main screen is not permissible for a long time - more than 1-2 minutes.How to turn off x2gothinclient from openbox-session. Or how to push haltbtn from openbox-session.
___
x2go-user mailing list
x2go-user@lists.x2go.org
https://lists.x2go.org/listinfo/x2go-user

[X2Go-User] x2gothinclient +pxe

[ovt]

About a year ago, I struggled with ubuntu + x2go + pxe for a long time. Spat on ubuntu and installed debian10. Imagine my surprise when I was able to build x2go-server and x2gothinclient with pxe download in 30 minutes. Everything worked fine, but ... I installed debian 32-bit which crashed frequently due to PAE issues, I think. Then I decided to install 64-bit server debian10 and thinclients + pxe. I ended up with another headache and hemorrhoids. Chroot environment for thinclient is not built because it does not pass security check.After 'apt-get update --allow-insecure-repositories' the environment has grown significantly, but the thinclient loading crashes with errors -'tmpfs:Bad value 'statd' for mount option 'uid'.Failed to mount /var/lib/nfs/Can't create cache dirrectory /var/cache/apparmor/...And much more...The manulas on https://wiki.x2go.org/ are untrue and out of date. The # x2go branch on freenode is not available. How to explain the complete collapse of a seemingly promising project?I ask for help starting x2gothinclient + pxe. Without waiting for an answer, I report the errors found in the / usr / sbin / x2gothinclient_create script.Skipped lines (206-207)[ $? -eq 0] && apt-get install gnupg -y[ $? -eq 0] && apt-key adv --recv-keys --keyserver keys.gnupg.net E1F958385BFE2B6E(251)[ $? -eq 0] && systemctl enable x2gothinclient-displaymanager After adding these lines, x2gothinclient loads fine. Please make these corrections.___
x2go-user mailing list
x2go-user@lists.x2go.org
https://lists.x2go.org/listinfo/x2go-user

[X2Go-User] Locale tty1 to x2gothinclient

[ovt]

How do I change the locale to root-console (tty1) to x2gothinclient? Cyrillic utf8 is needed.Some messages mc shows unreadable character and the interface is framed with some symbols that should not be  
___
x2go-user mailing list
x2go-user@lists.x2go.org
https://lists.x2go.org/listinfo/x2go-user

Re: [X2Go-User] scanner x2gothinclient , usb-pendrive

[ovt]

I tried connecting usbip to the scanner and it was easy, but ...The scanner can only be used with root privileges, which the thinclient user does not have.It is also unclear how to automatically connect usbip devices with different thinclients.30.10.2020, 16:33, "Ulrich Sibiller" :There's no such thing as USB forwarding for x2go currently. You cantry getting that at work by using something like this:https://www.linux-magazine.com/Issues/2018/208/Tutorial-USB-IPWe appreciate patches for USB/IP in x2go as this is a long-standingfeature request.Uli
___
x2go-user mailing list
x2go-user@lists.x2go.org
https://lists.x2go.org/listinfo/x2go-user

[X2Go-User] scanner x2gothinclient , usb-pendrive

[ovt]

+ x2go-user@- все 1. Debian 10.Thinclient desktop - openbox.Doesn't see usb-scanner under the x2gothinclient. If I log in as root on the thinclient, I can scan, but I cannot save anywhere, because there is no access to the file system for writing. Saned and Xsane is installed on the server , but  don't see the thin client usb-ports. I set up printing with thinclient via p910nd and it sees the printer fine on thinclient, why not find a similar method for the scanner?2. The x2gothinclient-usbmount package is installed. When connecting usb-flash, the thinclient creates a folder ~/.media/bla-bla ..., but there is no access to it even for reading - everything is empty there.  
___
x2go-user mailing list
x2go-user@lists.x2go.org
https://lists.x2go.org/listinfo/x2go-user

[X2Go-User] irc #x2go

[ovt]

I am subscribed to x2go-user and want help and communication on setting up x2gothinclient. In the irc channel # x2go, I observe complete silence and the response to my messages is '# x2go: Cannot send to nick / channel'. Since I am new to irc, please clarify for entering channel # x2go. My nickname for x2go-user is igor_
___
x2go-user mailing list
x2go-user@lists.x2go.org
https://lists.x2go.org/listinfo/x2go-user