Am 25.08.2018 um 03:58 schrieb Brian Lam:
> Note that this issue seems to only happen with Windows client. My
> colleague working on the Mac client never had this problem.
Keyboard detection and setting on the Mac uses a different approach, as
$SOMETHING on the Mac side of things is brain-dead
Uli,
That did it SOLVED! Thanks sooo much for your help.
After looking at x2gosetkeyboard script for a while, I realized that there
was an option to manually set the keyboard in the preferences instead of
relying on auto-detect.
[image: image.png]
I was only able to connect 10% of the
On Fri, Aug 24, 2018 at 10:23 PM, Brian Lam wrote:
>> This is messages I get in /var/log/messages when I try to open a terminal.
>>
>> Aug 24 12:10:50 pleth01 /usr/bin/x2gostartagent: successfully started X2Go
>> Agent session with ID eminami-56-1535127048_stRTERMINAL_dp32
>> Aug 24 12:10:55
The crash happens ind XkbSendMap(). So I suspect some client in your
session asking nxagent for the xkb keyboard configuration. You can
look if you can disable that client. I suspect running a simple xterm
via x2go will not crash the session. Can you confirm?
Uli
On Fri, Aug 24, 2018 at 8:40 PM,
Hi Brian,
Am 24.08.2018 um 20:10 schrieb Brian Lam:
> Okay so after reinstall, I'm back to square 1.
>
> But at least it helped identify a bug. Thanks for both of your help.
>
> Unfortunately, I still need to get unstuck urgently ... deadline
> approaching. Do you know any other system
On Fri, Aug 24, 2018 at 8:10 PM, Brian Lam wrote:
> Okay so after reinstall, I'm back to square 1.
>
> But at least it helped identify a bug. Thanks for both of your help.
>
> Unfortunately, I still need to get unstuck urgently ... deadline
> approaching. Do you know any other system like x2go
Okay so after reinstall, I'm back to square 1.
But at least it helped identify a bug. Thanks for both of your help.
Unfortunately, I still need to get unstuck urgently ... deadline
approaching. Do you know any other system like x2go that's free or low
cost? I tried Xming but it's too slow to
On Fri, Aug 24, 2018 at 5:18 PM, Brian Lam wrote:
> Yes I forgot the bt. This is what I get after I installed the rpm and ran
> gdb
>
> [root@pleth01 ~]# rpm -i
> ./nx-libs-debuginfo-3.5.99.16-0.0build1.1.git20180719.2988.main.el6.x86_64.rpm
> [root@pleth01 ~]# gdb /usr/bin/nxagent
Tried abrt-cli list. Last problem lists was 2 weeks ago.
Here is the re-run of gdb as you specified -
[root@pleth01 cchu]# gdb /usr/bin/nxagent core.15672
GNU gdb (GDB) Red Hat Enterprise Linux (7.2-92.el6)
Copyright (C) 2010 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or
Yes I forgot the bt. This is what I get after I installed the rpm and ran
gdb
[root@pleth01 ~]# rpm -i
./nx-libs-debuginfo-3.5.99.16-0.0build1.1.git20180719.2988.main.el6.x86_64.rpm
[root@pleth01 ~]# gdb /usr/bin/nxagent ~cchu/core.15672
GNU gdb (GDB) Red Hat Enterprise Linux (7.2-92.el6)
On Fri, Aug 24, 2018 at 2:24 PM, Brian Lam wrote:
>
> With the new errors about failed connection and x2gocheckport (see screenshot
> in previous email), I can no longer generate core dump.
> However, if I look at one of the older cored dumps, I get this -
Did you have a look at the abrt-cli
With the new errors about failed connection and x2gocheckport (see
screenshot in previous email), I can no longer generate core dump.
However, if I look at one of the older cored dumps, I get this -
[root@pleth01 cchu]# gdb core.15672
GNU gdb (GDB) Red Hat Enterprise Linux (7.2-92.el6)
Copyright
On Fri, Aug 24, 2018 at 3:00 PM, Brian Lam wrote:
> Tried abrt-cli list. Last problem lists was 2 weeks ago.
>
> Here is the re-run of gdb as you specified -
>
> [root@pleth01 cchu]# gdb /usr/bin/nxagent core.15672
> GNU gdb (GDB) Red Hat Enterprise Linux (7.2-92.el6)
> Copyright (C) 2010 Free
The logs from one of the previous mails show a crashing nxagent. Which is a
bug. Please run gdb against the coredump in the mentioned abrt directory
and post the output of gdb's bt command . We can then see where it crashes.
Uli
Brian Lam schrieb am Fr., 24. Aug. 2018, 06:33:
> After running
After running the command and cleaning /var/lib/x2go, I'm getting a
completely different message
[image: image.png]
Any suggestions? Thanks.
- Eric
On Thu, Aug 23, 2018 at 7:32 PM Paul Borowicz wrote:
> Try running 'sudo pkill -u user'. After making sure the folders are
> cleaned.
>
>
Try running 'sudo pkill -u user'. After making sure the folders are
cleaned.
Also delete files in /var/lib/x2go/
But not the directory itself.
On Thu, Aug 23, 2018, 10:11 PM Brian Lam wrote:
> Hi Paul,
>
> Still have the same problem after I delete .x2go and cleans up /tmp
>
> From
Hi Paul,
Still have the same problem after I delete .x2go and cleans up /tmp
>From /var/log/messages -
Aug 23 18:11:21 pleth01 /usr/bin/x2goruncommand: launching session with
Xsession-x2go mechanism, using STARTUP="/usr/bin/gnome-session"
Aug 23 18:11:21 pleth01 /usr/bin/x2goruncommand: dbus
I usually see this when there are stuck session files. Make sure you don't
have any processes running for that user.
Clean out ~/.x2go. You may also have to delete some stuff in /tmp.
Paul
On Thu, Aug 23, 2018, 5:10 PM Brian Lam wrote:
> Hello,
>
> I have been having intermittent problems with
Hello,
I have been having intermittent problems with getting into x2go on RH6
machine. Recently, after update of x2go server and client, I am not having
any success in connecting. I saw the same message before but I was able
to connect after I tried multiple times (usually success rate about
19 matches
Mail list logo
