I hope this doesn't mean the pure CLI client is being abandoned. I just discovered it in getting a completely scripted solution for my thin clients. I'd be happy to help test should you need help with that.

Thanks. Seth

On 02/23/2017 04:26 PM, Mike Gabriel wrote:

Hi Brian,

On So 12 Feb 2017 22:24:13 CET, brian town wrote:

...

Is there any port of the python-x2go to be useable by Python3?

Unfortunately no. My biggest mistake ever was sticking too long with Python2. I don't yet have any plans for porting to Python3 because I am working on a rewrite outside of the X2Go context and not in Python. Still all uncooked.

Mike

-- Seth Galitzer Systems Coordinator Computing and Information Sciences Kansas State University sgsax@ksu.edu 785-532-7790

Hmm i'll have to give that a look too. I wrote a broker in python that calls the x2goclient and passes a bunch of commands along to it but it would be great to not have the client window open up at all and just do it all via CLI. Right now my setup is using LTSP to push down the image to the clients, and from that they use x2go to connect to remote VMs. It's a huge pain but our environment is really weird.

On Tue, Feb 28, 2017 at 7:04 PM, Stefan Baur <X2Go-ML-1@baur-itcs.de> wrote:

Am 28.02.2017 um 21:24 schrieb Seth Galitzer:

...

I hope this doesn't mean the pure CLI client is being abandoned. I just discovered it in getting a completely scripted solution for my thin clients. I'd be happy to help test should you need help with that.

What exactly are you trying to achieve with the scripted PyHoca-CLI? There may be ways to achieve the same result using our new X2Go-ThinClientEditon (see <http://wiki.x2go.org/doku.php/doc:howto:tce>, or <http://x2go.baur-itcs.de/x2go-tce-stable/> for builds you can start tinkering with), which uses the stock X2GoClient.

Please let us know your use case, and we'll see what we can come up with.

Also, as always, once you're happy with X2Go, please drop us a few lines we can publish on our "Success Stories" page (<http://wiki.x2go.org/doku.php/doc:success-stories:start#success_stories

...

).

-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

---

x2go-user mailing list x2go-user@lists.x2go.org http://lists.x2go.org/listinfo/x2go-user

Taking a look at it all now, got the image and PXE booting it properly however it seems to get stuck at the loading screen for "X2Go TCE" where it finishes out and then just sits there with nothing going on. Trying to figure out why now.

On Wed, Mar 1, 2017 at 8:31 AM, Stefan Baur <X2Go-ML-1@baur-itcs.de> wrote:

Am 01.03.2017 um 14:17 schrieb brian town:

...

Hmm i'll have to give that a look too. I wrote a broker in python that calls the x2goclient and passes a bunch of commands along to it but it would be great to not have the client window open up at all and just do it all via CLI.

You're aware that X2Go has an official Session Broker written in Python, and there's even a bunch of automated installation scripts for a demo setup using LDAP, NFS, Postgres, one Broker and two X2GoServers? See: <http://wiki.x2go.org/doku.php/doc:howto:x2gobroker>

Also, quoting "man x2goclient": --hide Hide client (start hidden, default: false).

--> No visible X2GoClient window.

...

Right now my setup is using LTSP to push down the image to the clients, and from that they use x2go to connect to remote VMs. It's a huge pain but our environment is really weird.

I think you should really evaluate our new Debian-Live based TCE. It can be booted over the net as well as installed on local storage or removable media.

As already stated in my previous post, see: <http://wiki.x2go.org/doku.php/doc:howto:tce> As well as <http://x2go.baur-itcs.de/x2go-tce-stable/> for some demo builds you can tinker with.

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

Using a VM and the TFTP boot method, could be the issue there then with squashfs not working due to it.

On Wed, Mar 1, 2017 at 10:34 AM, Stefan Baur <X2Go-ML-1@baur-itcs.de> wrote:

Am 01.03.2017 um 16:27 schrieb brian town:

...

Taking a look at it all now, got the image and PXE booting it properly however it seems to get stuck at the loading screen for "X2Go TCE" where it finishes out and then just sits there with nothing going on. Trying to figure out why now.

Please post the boot parameters used and try to make a screenshot of the screen where it freezes - if you're running the test client as virtual machine, your host should have a screenshot feature; if you're using real hardware, try to capture it with your smartphone camera.

Also, if you've tried to make any changes to the squashfs file, please try an unchanged file first, and see if that boots.

Not sure how you're trying to boot, so just some general reminders/hints:

• squashfs via TFTP usually won't work, and even if it does, it will take ages to load
• if you're using http(s)/ftp as you should, make sure you can download the files manually - if you can't, then it's a sign that you probably need to adjust ownership and/or permissions on the server.
• if you end up with a black screen once the boot messages scrolled by, try passing a parameter specifying the screen size or an alternative xorg.conf file. (they're documented in the Wiki).

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

Long story short: In my thin client lab, we use an RDP client to connect to Windows Remote Desktop Servers and have been using XDMCP to connect to Linux X desktops. I want to use X2go for the superior performance, reliability, and security over XDMCP, but am unable to do so due to limitations by the thin client platform vendor. The hardware is apparently ordinary x86 so I'm working on rolling my own minimal image to accomplish this.

With the current platform, we have desktop shortcuts that to run the RDP/XDMCP clients to various hosts. I'd like to try and duplicate that with my new image so I don't have to retrain my users. I'm scripting freerdp-x11 for RDP connections (with NLA). After trying various ways to script x2goclient, I finally discovered pyhoca-cli and it works exactly the way I want it to.

So that's why I hope it stays available in some form for a while. If there's a better way to run x2goclient completely "headless" or transparent to the user, I'd be happy to hear it. I've been searching through documentation and haven't found a way yet to do it the way that I want.

I already have my PXE server setup, but haven't decided yet if I'm going to boot from a network image, or push the image down to the clients to pre-load for booting. My minimal debian image with all necessary tools is currently just over 2GB uncompressed. I'm not opposed to TCE, but I'd like to be able to at least customize the skin with our own branding.

I'd love to hear anyone's thoughts on this. I'm relatively new to X2go, so I'm sure there are ways to use it to help with this project I haven't thought of yet.

Thanks. Seth

On 02/28/2017 06:04 PM, Stefan Baur wrote:

Am 28.02.2017 um 21:24 schrieb Seth Galitzer:

...

I hope this doesn't mean the pure CLI client is being abandoned. I just discovered it in getting a completely scripted solution for my thin clients. I'd be happy to help test should you need help with that.

What exactly are you trying to achieve with the scripted PyHoca-CLI? There may be ways to achieve the same result using our new X2Go-ThinClientEditon (see <http://wiki.x2go.org/doku.php/doc:howto:tce>, or <http://x2go.baur-itcs.de/x2go-tce-stable/> for builds you can start tinkering with), which uses the stock X2GoClient.

Please let us know your use case, and we'll see what we can come up with.

Also, as always, once you're happy with X2Go, please drop us a few lines we can publish on our "Success Stories" page (<http://wiki.x2go.org/doku.php/doc:success-stories:start#success_stories>).

-Stefan Baur

---

x2go-user mailing list x2go-user@lists.x2go.org http://lists.x2go.org/listinfo/x2go-user

-- Seth Galitzer Systems Coordinator Computing and Information Sciences Kansas State University http://www.cis.ksu.edu/~sgsax sgsax@ksu.edu 785-532-7790

Wyse (Dell) D50D, running embedded Suse Linux, which seems to be a special compressed minimal image based on that distro. I have 56 of them in my lab. After trying for a year to find out if/how I could build my own X2go package, I finally talked to a tech who said it wouldn't be possible and they were in the process of rolling out a new Linux image across their product line. That's the one who also told me it was ordinary x86 hardware and there wasn't any reason I couldn't roll my own.

Wyse used to have a pretty nice forum and wiki with user-contributed documentation, and I seem to recall finding info on building custom packages for the platform there. That all eventually disappeared when Dell acquired the company and I apparently didn't save anything I had gathered previously. That's why I'm building my own platform now.

Seth

On 03/01/2017 11:42 AM, brian town wrote:

What thinclients are you using if you don't mind my asking

On Mar 1, 2017 12:31 PM, "Seth Galitzer" <sgsax@ksu.edu <mailto:sgsax@ksu.edu>> wrote:

Long story short: In my thin client lab, we use an RDP client to
connect to Windows Remote Desktop Servers and have been using XDMCP
to connect to Linux X desktops. I want to use X2go for the superior
performance, reliability, and security over XDMCP, but am unable to
do so due to limitations by the thin client platform vendor. The
hardware is apparently ordinary x86 so I'm working on rolling my own
minimal image to accomplish this.

With the current platform, we have desktop shortcuts that to run the
RDP/XDMCP clients to various hosts. I'd like to try and duplicate
that with my new image so I don't have to retrain my users. I'm
scripting freerdp-x11 for RDP connections (with NLA). After trying
various ways to script x2goclient, I finally discovered pyhoca-cli
and it works exactly the way I want it to.

So that's why I hope it stays available in some form for a while. If
there's a better way to run x2goclient completely "headless" or
transparent to the user, I'd be happy to hear it. I've been
searching through documentation and haven't found a way yet to do it
the way that I want.

I already have my PXE server setup, but haven't decided yet if I'm
going to boot from a network image, or push the image down to the
clients to pre-load for booting. My minimal debian image with all
necessary tools is currently just over 2GB uncompressed. I'm not
opposed to TCE, but I'd like to be able to at least customize the
skin with our own branding.

I'd love to hear anyone's thoughts on this. I'm relatively new to
X2go, so I'm sure there are ways to use it to help with this project
I haven't thought of yet.

Thanks.
Seth

On 02/28/2017 06:04 PM, Stefan Baur wrote:

    Am 28.02.2017 um 21:24 schrieb Seth Galitzer:

        I hope this doesn't mean the pure CLI client is being
        abandoned. I just
        discovered it in getting a completely scripted solution for
        my thin
        clients. I'd be happy to help test should you need help with
        that.


    What exactly are you trying to achieve with the scripted PyHoca-CLI?
    There may be ways to achieve the same result using our new
    X2Go-ThinClientEditon (see
    <http://wiki.x2go.org/doku.php/doc:howto:tce
    <http://wiki.x2go.org/doku.php/doc:howto:tce>>, or
    <http://x2go.baur-itcs.de/x2go-tce-stable/
    <http://x2go.baur-itcs.de/x2go-tce-stable/>> for  builds you can
    start
    tinkering with), which uses the stock X2GoClient.

    Please let us know your use case, and we'll see what we can come
    up with.

    Also, as always, once you're happy with X2Go, please drop us a
    few lines
    we can publish on our "Success Stories" page
    (<http://wiki.x2go.org/doku.php/doc:success-stories:start#success_stories
    <http://wiki.x2go.org/doku.php/doc:success-stories:start#success_stories>>).

    -Stefan Baur



    _______________________________________________
    x2go-user mailing list
    x2go-user@lists.x2go.org <mailto:x2go-user@lists.x2go.org>
    http://lists.x2go.org/listinfo/x2go-user
    <http://lists.x2go.org/listinfo/x2go-user>


--
Seth Galitzer
Systems Coordinator
Computing and Information Sciences
Kansas State University
http://www.cis.ksu.edu/~sgsax
sgsax@ksu.edu <mailto:sgsax@ksu.edu>
785-532-7790 <tel:785-532-7790>
_______________________________________________
x2go-user mailing list
x2go-user@lists.x2go.org <mailto:x2go-user@lists.x2go.org>
http://lists.x2go.org/listinfo/x2go-user
<http://lists.x2go.org/listinfo/x2go-user>

-- Seth Galitzer Systems Coordinator Computing and Information Sciences Kansas State University http://www.cis.ksu.edu/~sgsax sgsax@ksu.edu 785-532-7790

Am 01.03.2017 um 18:30 schrieb Seth Galitzer:

Long story short: In my thin client lab, we use an RDP client to connect to Windows Remote Desktop Servers and have been using XDMCP to connect to Linux X desktops. I want to use X2go for the superior performance, reliability, and security over XDMCP, but am unable to do so due to limitations by the thin client platform vendor. The hardware is apparently ordinary x86 so I'm working on rolling my own minimal image to accomplish this.

Save for that vendor's lock-in stupidity, it sounds straightforward enough.

With the current platform, we have desktop shortcuts that to run the RDP/XDMCP clients to various hosts. I'd like to try and duplicate that with my new image so I don't have to retrain my users.

Well, it depends how bad that "retraining" would be. X2Go in TCE mode can serve as a frontend to xfreerdp for RDP and also to Xephyr for XDMCP (that feature isn't in the stable release yet, but an image based on a recent nightly build is available).

That way, when starting X2GoClient in fullscreen mode (as is the default with TCE) there's just a few white tiles on the right that list the various connections. No matter if they're X2Go, RDP, or XDMCP - all share the same look.

You can deploy configuration (i.e. which tiles appear and which not) either static via HTTP(S)/FTP, or using a simple server-side script for TTP(S), or you can use the full-fledged session broker, which allows you to define tile/session visibility depending on user name, group membership, and IP range (plus the broker also does load balancing).

However, this frontend-only mode doesn't involve X2GoServer at all for RDP and XDMCP connections, so there's no performance increase for these.

If you want to accelerate things for RDP and XDMCP, you need an X2GoServer inbetween.

You could proceed just as described above, with individual tiles for each remote server (now using the X2GoServer as an accelerating proxy instead of connecting directly), or offer a minimal desktop (say, LXDE or XFCE, or a trimmed-down MATE) from the X2GoServer machine, with the desired connections as desktop shortcuts.

I'm scripting freerdp-x11 for RDP connections (with NLA). After trying various ways to script x2goclient, I finally discovered pyhoca-cli and it works exactly the way I want it to.

So that's why I hope it stays available in some form for a while. If there's a better way to run x2goclient completely "headless" or transparent to the user, I'd be happy to hear it. I've been searching through documentation and haven't found a way yet to do it the way that I want.

To get started, use a regular Linux machine (not a ThinClient), install X2GoClient, configure a session. Make sure to use Public Key authentication, run an SSH-agent, load your keyfile into it (don't specify the actual keyfile in the session configuration, just check the box that X2GoClient should attempt auto-login via SSH-Agent or Key). Try if it works (clicking on the tile should then connect you to your server, without asking for credentials). If that works, log out of the session again. If you now see a login box that prompts for username and password, click cancel. If not, just read on. Look at the tile of the session you just configured. Depending on which X2GoClient version you use, there's either a small grey downward-pointing triangle or a "hamburger icon" like on an Android smartphone in the lower left corner of the tile. Click "Create Session Icon on Desktop". Note the little checkbox in the lower left corner of that message.

If you examine the desktop link afterwards, you will see that X2GoClient is called with --hide --sessionid=20110913020213584 and optionally --tray-icon as well, if you checked the box mentioned earlier. The sessionid number corresponds to the session in your sessions file. You can also use --session=SessionName instead.

(Double-)Click that desktop link and see if it does what you are looking for - it should.

Now that you've got a working setup, you can deploy the sessions config file and the "--"parameters to your clients.

I already have my PXE server setup, but haven't decided yet if I'm going to boot from a network image, or push the image down to the clients to pre-load for booting. My minimal debian image with all necessary tools is currently just over 2GB uncompressed.

Our TCE image - which does nothing more than fire up X2GoClient in fullscreen mode, and some background stuff for audio and removable media automounting - is currently about 200 Megabytes in size, rather than 2GB. It uncompresses into a RAM disk when booting over the network. With local storage, you don't need to load the entire image into RAM.

I'm not opposed to TCE, but I'd like to be able to at least customize the skin with our own branding.

Well, with a fullscreen X2GoClient, there isn't much "skin" to brand - you'd brand the desktop on the X2GoServer instead.

I'd love to hear anyone's thoughts on this. I'm relatively new to X2go, so I'm sure there are ways to use it to help with this project I haven't thought of yet.

If all of the above still didn't convince you and you'd still prefer a minimal desktop environment running directly on the ThinClient (again, I would recommend against this as it means *zero* performance increase if you run RDP or XDMCP sessions from desktop shortcuts starting xfreerdp or "Xephyr -query", rather than through an X2GoServer acting as a proxy)

• "stay tuned". We're working on reviving Mike#1's "minidesktop" for X2Go-TCE. Currently, that's only a hobby project of mine, but hey, Linus Torvalds wrote something similar when he started working on Linux, so who knows. ;-)

As always, if you have a budget for X2Go deployment, we can speed up development by working on it during office hours, rather than in our free time.

<shameless plug> X2Go also has a commercial side, where various companies - including my own - offer support contracts with guaranteed response times as well as consultancy and paid-for development work if someone wants to see a bug fixed or a new feature added in a certain time frame.

What makes my company special is, IMHO:

1. I'm the current X2Go Project/Community Coordinator, so the development lead and the developers tend to listen to me.
2. As far as I know, we are the only company providing X2Go support that isn't a one-man-show. Oh, and we already have US customers.
3. We sub-contract other developers from the X2Go community on demand, so you only have one person you need to talk to - me - and you will only receive one invoice, even if the task involved several freelance or part-time X2Go developers.

Our hourly rate for consultancy work and fixing issues outside of a support contract is 110 EUR. With a support contract, you get guaranteed response times (starting at 400 EUR/month for 24h response time during business hours in the CET/CEST time zone from Monday to Friday, German holidays excluded) and lower hourly rates if you buy a certain amount of hours in advance. </shameless plug>

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

I've been playing with this a bit the last couple of days and have a working PXE boot using your pre-built images (thanks for sharing). My plan is to replace XDMCP entirely with X2go native client, and it looks like I can setup custom immutable connections for that and my RDP sessions use the TCE. The end result will not be all that different from what we have now, so user training should not be an issue.

I'd like to customize or brand the client workspace. It looks like this isn't possible with OOTB configuration, so I dove into the code and found where the graphics are set and where the resource files are in the source tree. Making my changes are trivial enough (I think), so I plan to hack in my changes and replace the binaries in the squashfs image to deploy to my clients. Right now I'm trying to build the client with my changes and am running into problems.

I'm trying to follow http://wiki.x2go.org/doku.php/wiki:development:build-howto-linux:x2goclient and getting stuck. I can clone the x2goclient git repo just fine (step 2a), but am unable to clone the nxproxy repo (step 1). I get "access denied or repository not exported". I was able to clone the nx-libs repos, but am not finding documentation on how to build that. I also looked at http://wiki.x2go.org/doku.php/wiki:development:deb-buildguide to setup my build environment.

Could I get some help getting my dev environment setup? If there's a better way to accomplish what I want to do with branding, or a better list/forum to inquire, please let me know.

Thanks. Seth

On 03/01/2017 12:13 PM, Stefan Baur wrote:

Am 01.03.2017 um 18:30 schrieb Seth Galitzer:

...

Long story short: In my thin client lab, we use an RDP client to connect to Windows Remote Desktop Servers and have been using XDMCP to connect to Linux X desktops. I want to use X2go for the superior performance, reliability, and security over XDMCP, but am unable to do so due to limitations by the thin client platform vendor. The hardware is apparently ordinary x86 so I'm working on rolling my own minimal image to accomplish this.

Save for that vendor's lock-in stupidity, it sounds straightforward enough.

...

With the current platform, we have desktop shortcuts that to run the RDP/XDMCP clients to various hosts. I'd like to try and duplicate that with my new image so I don't have to retrain my users.

Well, it depends how bad that "retraining" would be. X2Go in TCE mode can serve as a frontend to xfreerdp for RDP and also to Xephyr for XDMCP (that feature isn't in the stable release yet, but an image based on a recent nightly build is available).

That way, when starting X2GoClient in fullscreen mode (as is the default with TCE) there's just a few white tiles on the right that list the various connections. No matter if they're X2Go, RDP, or XDMCP - all share the same look.

You can deploy configuration (i.e. which tiles appear and which not) either static via HTTP(S)/FTP, or using a simple server-side script for TTP(S), or you can use the full-fledged session broker, which allows you to define tile/session visibility depending on user name, group membership, and IP range (plus the broker also does load balancing).

However, this frontend-only mode doesn't involve X2GoServer at all for RDP and XDMCP connections, so there's no performance increase for these.

If you want to accelerate things for RDP and XDMCP, you need an X2GoServer inbetween.

You could proceed just as described above, with individual tiles for each remote server (now using the X2GoServer as an accelerating proxy instead of connecting directly), or offer a minimal desktop (say, LXDE or XFCE, or a trimmed-down MATE) from the X2GoServer machine, with the desired connections as desktop shortcuts.

...

I'm scripting freerdp-x11 for RDP connections (with NLA). After trying various ways to script x2goclient, I finally discovered pyhoca-cli and it works exactly the way I want it to.

So that's why I hope it stays available in some form for a while. If there's a better way to run x2goclient completely "headless" or transparent to the user, I'd be happy to hear it. I've been searching through documentation and haven't found a way yet to do it the way that I want.

To get started, use a regular Linux machine (not a ThinClient), install X2GoClient, configure a session. Make sure to use Public Key authentication, run an SSH-agent, load your keyfile into it (don't specify the actual keyfile in the session configuration, just check the box that X2GoClient should attempt auto-login via SSH-Agent or Key). Try if it works (clicking on the tile should then connect you to your server, without asking for credentials). If that works, log out of the session again. If you now see a login box that prompts for username and password, click cancel. If not, just read on. Look at the tile of the session you just configured. Depending on which X2GoClient version you use, there's either a small grey downward-pointing triangle or a "hamburger icon" like on an Android smartphone in the lower left corner of the tile. Click "Create Session Icon on Desktop". Note the little checkbox in the lower left corner of that message.

If you examine the desktop link afterwards, you will see that X2GoClient is called with --hide --sessionid=20110913020213584 and optionally --tray-icon as well, if you checked the box mentioned earlier. The sessionid number corresponds to the session in your sessions file. You can also use --session=SessionName instead.

(Double-)Click that desktop link and see if it does what you are looking for - it should.

Now that you've got a working setup, you can deploy the sessions config file and the "--"parameters to your clients.

...

I already have my PXE server setup, but haven't decided yet if I'm going to boot from a network image, or push the image down to the clients to pre-load for booting. My minimal debian image with all necessary tools is currently just over 2GB uncompressed.

Our TCE image - which does nothing more than fire up X2GoClient in fullscreen mode, and some background stuff for audio and removable media automounting - is currently about 200 Megabytes in size, rather than 2GB. It uncompresses into a RAM disk when booting over the network. With local storage, you don't need to load the entire image into RAM.

...

I'm not opposed to TCE, but I'd like to be able to at least customize the skin with our own branding.

Well, with a fullscreen X2GoClient, there isn't much "skin" to brand - you'd brand the desktop on the X2GoServer instead.

...

I'd love to hear anyone's thoughts on this. I'm relatively new to X2go, so I'm sure there are ways to use it to help with this project I haven't thought of yet.

If all of the above still didn't convince you and you'd still prefer a minimal desktop environment running directly on the ThinClient (again, I would recommend against this as it means *zero* performance increase if you run RDP or XDMCP sessions from desktop shortcuts starting xfreerdp or "Xephyr -query", rather than through an X2GoServer acting as a proxy)

• "stay tuned". We're working on reviving Mike#1's "minidesktop" for X2Go-TCE. Currently, that's only a hobby project of mine, but hey, Linus Torvalds wrote something similar when he started working on Linux, so who knows. ;-)

As always, if you have a budget for X2Go deployment, we can speed up development by working on it during office hours, rather than in our free time.

<shameless plug> X2Go also has a commercial side, where various companies - including my own - offer support contracts with guaranteed response times as well as consultancy and paid-for development work if someone wants to see a bug fixed or a new feature added in a certain time frame.

What makes my company special is, IMHO:

1. I'm the current X2Go Project/Community Coordinator, so the development lead and the developers tend to listen to me.
2. As far as I know, we are the only company providing X2Go support that isn't a one-man-show. Oh, and we already have US customers.
3. We sub-contract other developers from the X2Go community on demand, so you only have one person you need to talk to - me - and you will only receive one invoice, even if the task involved several freelance or part-time X2Go developers.

Our hourly rate for consultancy work and fixing issues outside of a support contract is 110 EUR. With a support contract, you get guaranteed response times (starting at 400 EUR/month for 24h response time during business hours in the CET/CEST time zone from Monday to Friday, German holidays excluded) and lower hourly rates if you buy a certain amount of hours in advance. </shameless plug>

Kind Regards, Stefan Baur

---

x2go-user mailing list x2go-user@lists.x2go.org http://lists.x2go.org/listinfo/x2go-user

-- Seth Galitzer Systems Coordinator Computing and Information Sciences Kansas State University http://www.cis.ksu.edu/~sgsax sgsax@ksu.edu 785-532-7790

Am 04.03.2017 um 00:10 schrieb Seth Galitzer:

I'd like to customize or brand the client workspace. It looks like this isn't possible with OOTB configuration, so I dove into the code...

Quoth the X2GoClient manpage:

--support-menu=<html-file> Add a "Support..." submenu item to X2Go Client's "Help" menu.

The support information is provided via a simple HTML file. Example:

            <html><body>
            <h1>IT-Support for X2Go</h1>
            DAS-NETZWERKTEAM | Mike Gabriel:<br />
            <a href="mailto:support@das-netzwerkteam.de">
                support@das-netzwerkteam.de
            </a><br />
            <br />
            Thanks for using X2Go...
            </body></html>

--background=<svg-file> Use a custom/branded background image (SVG format) for X2Go Client's main window (i.e. replace the blue gradient area in X2Go Client by some background of your own (business/workgroup/project).

These aren't good enough for you? What else did you have in mind?

-Stefan

-- 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

Am 10.03.2017 um 16:37 schrieb Seth Galitzer:

I missed that, thanks for pointing it out. I was also wanting to replace the seal logo with my own, and change the color of the hamburger icon, but those aren't critical. Now to go back to digging in TCE docs to figure out how to include and use my background image.

There's no option to do it with a simple boot parameter (yet), but we could include that in the future. In the meantime, you could set up your own TCE build environment and make the required changes, or take one of our pre-built ones, and use unsquashfs, apply your changes, then use mksquashfs again.

And again, let me remind you we're available for commercial support. I.e. if you'd like to see the feature included as boot parameters in an official TCE release rather sooner than later, we can offer that for a price.

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

Am 10.03.2017 um 23:49 schrieb Seth Galitzer:

Yes, I spent some time chatting on IRC today and think I've figured out how to hack the configs in the image to allow it. I even tried to make it extensible so it can be used for additional params. I'd be happy to send you my patch. I have some other ideas on further customizable elements of the desktop, but will need to read up on Qt for those. Thanks for the help.

I think I saw your patch somewhere - was it over on x2go-dev? - but I haven't had a chance to look at it so far. -> Flu, only starting to feel better these days. :o(

Sorry!

-Stefan

-- 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