On 05/29/2015 02:36 PM, Michael DePaulo wrote:
On Fri, May 29, 2015 at 3:33 AM, Q4OS Team <info@q4os.org> wrote:
Hi Mike, Mihai,
On 05/29/2015 04:31 AM, Michael DePaulo wrote:
Hi Pete,
On Thu, May 28, 2015 at 9:51 PM, Mihai Moldovan <ionic@ionic.de> wrote: [...] As long as the required (X2Go) packages are available on Q4OS, it should be working out of the box with Trinity. Unfortunately no, Q4OS needs to set env and take some tasks before launch a session. This is what our script does, see below.
What is /usr/bin/start-q4os-x2go supposed to do? This is small dash compatible script, it takes some Q4OS specific tasks, set Q4OS environment and then launches default Trinity 'starttde' script.
We can also modify the behavior of x2goserver to launch /usr/bin/start-q4os-x2go supposed if the user selects "TRINITY" in x2goclient Both methods look nice. I suppose the best way to detect Q4OS is to simply check /usr/bin/start-q4os-x2go to exist.
Pete I just made a commit to x2goserver on both the release/4.0.1.x branch (which will become 4.0.1.20) and the master branch (which will become 4.1.0.0) to do that: release/4.0.1.x: http://code.x2go.org/gitweb?p=x2goserver.git;a=commit;h=c8cee419bca5126323ab... master: http://code.x2go.org/gitweb?p=x2goserver.git;a=commit;h=9ec47ce0dfe7a9d4895d...
BTW, how does Q4OS install X2Go exactly? I downloaded the Q4OS 1.2.2 x64 iso. I don't see any x2goserver package, but I do see x2go-keyring_2011.12.07+wheezy~baikal~12~build1_all.deb . If Q4OS is accessing the baikal apt repo under http://packages.x2go.org/debian/ , then that is a problem because baikal provides x2goserver 4.0.0.x, which does not support trinity.
-Mike#2
Pretty quick, thanks .. the most preferred way to install X2Go Server in Q4OS is to use specific installer from 'Software Centre'. It will add debian-baikal repos and install X2Go Server from. We instructs our customers to set 'start-q4os-x2go' as 'Custom' command in Session preferences in X2Go Client now. It works perfectly for Trinity/Q4OS.
So the new feature could be accessible for most Q4OS users after transition into the new Server's branch, when baikal lifetime cycle will finish.
Pete