[X2Go-User] CentOS7/EPEL package?

[Roderick Johnstone]

On 04/11/14 09:45, Mike Gabriel wrote:
> Hi Roderick,
>
> On  Di 04 Nov 2014 09:25:59 CET, Roderick Johnstone wrote:
>
>> On 03/11/2014 20:50, Orion Poplawski wrote:
>>> On 11/03/2014 11:08 AM, Roderick Johnstone wrote:
>>>> On 03/11/14 17:51, Orion Poplawski wrote:
>>>>> On 11/03/2014 04:12 AM, Roderick Johnstone wrote:
>>>>>>
>>>>>> Mike
>>>>>>
>>>>>> Curiously, for me, with Orion's 4.0.1.18-3 packages on Fedora 20 a
>>>>>> KDE session
>>>>>> fails to start if I have x2goserver-xsession installed, but works
>>>>>> fine if
>>>>>> x2goserver-xsession is not installed.
>>>>>>
>>>>>> Roderick
>>
>>
>> So I tested it with a Terminal session. That works fine. I tested the
>> KDE session as root. That fails.
>>
>> What happens is that, very briefly, the remote screen pops up. Its
>> black with the x2go logo and disappears in a fraction of a second.
>>
>> By the way,  I was able to reconnect to an already running session
>> that had been created without the x2goserver-xsession package
>> installed when the x2goserver-xsession packages was installed.
>>
>> Let me know if I can run any more tests that might be helpful for
>> debugging.
>>
>> Roderick
>
> Please edit /usr/bin/x2goruncommand and add extra debug messages. Place
> them everywhere, so to say and look which of the messages appear in the
> messages log file and which don't. You need to track down the code path
> that is gone while running x2goruncommand.
>
> Thanks+greets,
> mike
>

Mike

Thanks for your input.

I've actually started on a different tack in this debugging.

Having identified which files are installed by x2goserver-xsession, I've 
been systematically renaming these files so that they are not found.

Using this technique I have found that the session works fine when I move
/etc/x2go/xinitrc.d/50-input.sh
to
/etc/x2go/xinitrc.d.off/50-input.sh
so I think this file is where the problem lies.

50-input.sh is quite a busy file, so I suppose I'll have to pepper it 
with echo's to find out at what point the session evaporates.

Where would I expect to find the output from an echo command in that 
file logged?

Given what I have found so far, do you think there is still merit in 
putting debugging statements into /usr/bin/x2goruncommand?

Thanks

Roderick