[X2Go-User] X2Go crash from Mac/MATE to Fedora 25 w NIS user getting x2gostartagent: blocking creation of agent's keyboard file
Robert Dinse
nanook at eskimo.com
Sun Feb 26 15:38:27 CET 2017
For what it's worth I applied same updates to a Ubuntu 16.10 machine and
things still worked with Mate afterwards.
-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-
Eskimo North Linux Friendly Internet Access, Shell Accounts, and Hosting.
Knowledgeable human assistance, not telephone trees or script readers.
See our web site: http://www.eskimo.com/ (206) 812-0051 or (800) 246-6874.
On Sun, 26 Feb 2017, Robert Dinse wrote:
> Date: Sun, 26 Feb 2017 06:08:42 -0800 (PST)
> From: Robert Dinse <nanook at eskimo.com>
> To: Mihai Moldovan <ionic at ionic.de>
> Cc: x2go-user at lists.x2go.org
> Subject: Re: [X2Go-User] X2Go crash from Mac/MATE to Fedora 25 w NIS user
> getting x2gostartagent: blocking creation of agent's keyboard file
>
>
> On Sun, 26 Feb 2017, Mihai Moldovan wrote:
>>
>> On 26.02.2017 10:25 AM, Robert Dinse wrote:
>>> In my case it is the x2goagent on the server. I can not find a core
>>> however.
>>
>> Do you have the same symptom? Is MATE not starting up at all?
>> Or is it crashing after the session has been running for some time already?
>
> Mate starts up and runs but it usually crashes when I'm opening a
> terminal, editing a file, or doing upgrades.
>
> However there was a new x2goserver and some related files tonight that
> installed during an upgrade and then after that a rather large update that
> involved 400 some packages and it didn't explode.
>
> I poked about, opened terminals, vi'd files, etc, could not get it to
> crash so not sure tonights update didn't fix it. If it crashes again and I
> can get a core dump, I will send a backtrace like I did for the problems I
> was
> having under Ubuntu.
>
> Thank you very much for fixing those BTW.
>
>> Normally, core files tend to sit in the user's home dir - but that depends
>> upon some circumstances (like whether creating core dumps at all is allowed
>> or not - with different systems utilizing different methods of getting this
>> to work.)
>
> Yes, that is where I usually find them but they were not in my home
> directory. I have to take a look at settings, might be the default has the
> core file size set to zero or turned off. I have not really changed much
> from
> the system defaults on that machine.
>
>> Fedora and RHEL-based distros use ABRT (Automatic Bug Reporting Tool),
>> which stashes the core dumps and can easily send them to Red Hat's Bugzilla
>> instance.
>
> If it is a developer other than RedHat it will not. It will instead
> just
> pop up a message telling you such and such crashed and is not a RedHat
> product
> and if you want it fixed to contact the developer.
>
>> The general place to look at is probably /etc/security/limits.conf for
>> core dumping permissions and then figure out what ABRT exactly does.
>
> Was limited to 10MB (10000K), increased to 100MB (core).
>
> Well looks like it's gotten more fun. Now the session will not start up
> at all. Blitzed and re-installed, these are the packages installed:
>
> Downloading Packages:
> (1/13): perl-Config-Simple-4.59-23.fc25.noarch. 126 kB/s | 39 kB 00:00
> (2/13): pwgen-2.07-3.fc24.x86_64.rpm 63 kB/s | 30 kB 00:00
> (3/13): x2goserver-4.1.0.0-0.0x2go1.0.git201702 116 kB/s | 92 kB 00:00
> (4/13): perl-X2Go-Log-4.1.0.0-0.0x2go1.0.git201 74 kB/s | 36 kB 00:00
> (5/13): perl-X2Go-Server-4.1.0.0-0.0x2go1.0.git 73 kB/s | 46 kB 00:00
> (6/13): x2goserver-common-4.1.0.0-0.0x2go1.0.gi 78 kB/s | 37 kB 00:00
> (7/13): perl-X2Go-Server-DB-4.1.0.0-0.0x2go1.0. 100 kB/s | 48 kB 00:00
> (8/13): x2goserver-extensions-4.1.0.0-0.0x2go1. 121 kB/s | 38 kB 00:00
> (9/13): x2goagent-3.5.0.33-0.0x2go1.0.git201611 34 kB/s | 17 kB 00:00
> (10/13): x2goserver-xsession-4.1.0.0-0.0x2go1.0 53 kB/s | 37 kB 00:00
> (11/13): libXcompshad3-3.5.99.3-0.0build1.fc25. 134 kB/s | 33 kB 00:00
> (12/13): libNX_X11-6-3.5.99.3-0.0build1.fc25.x8 190 kB/s | 608 kB 00:03
> (13/13): nxagent-3.5.99.3-0.0build1.fc25.x86_64 137 kB/s | 1.6 MB 00:11
> --------------------------------------------------------------------------------
> Total 194 kB/s | 2.6 MB 00:13
>
> Still will not start any longer.
>
> .xsession-x2go-fedora.eskimo.com-errors contained only:
> XSession-x2go: X session started for root at Sun Feb 26 05:23:02 PST 2017
>
> It is actually mate-session that is exploding thusly:
>
> gdb /usr/bin/mate-session core.2131
> GNU gdb (GDB) Fedora 7.12.1-46.fc25
> Copyright (C) 2017 Free Software Foundation, Inc.
> License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
> This is free software: you are free to change and redistribute it.
> There is NO WARRANTY, to the extent permitted by law. Type "show copying"
> and "show warranty" for details.
> This GDB was configured as "x86_64-redhat-linux-gnu".
> Type "show configuration" for configuration details.
> For bug reporting instructions, please see:
> <http://www.gnu.org/software/gdb/bugs/>.
> Find the GDB manual and other documentation resources online at:
> <http://www.gnu.org/software/gdb/documentation/>.
> For help, type "help".
> Type "apropos word" to search for commands related to "word"...
> Reading symbols from /usr/bin/mate-session...Reading symbols from
> /usr/bin/mate-session...(no debugging symbols found)...done.
> (no debugging symbols found)...done.
> [New LWP 2131]
> [Thread debugging using libthread_db enabled]
> Using host libthread_db library "/lib64/libthread_db.so.1".
> Core was generated by `mate-session'.
> Program terminated with signal SIGSEGV, Segmentation fault.
> #0 0x00007f11a26bf35f in rawmemchr () from /lib64/libc.so.6
> Missing separate debuginfos, use: dnf debuginfo-install
> mate-session-manager-1.16.1-1.fc25.x86_64
> (gdb) bt
> #0 0x00007f11a26bf35f in rawmemchr () at /lib64/libc.so.6
> #1 0x00007f11a26a7832 in _IO_str_init_static_internal () at /lib64/libc.so.6
> #2 0x00007f11a2694cc7 in __isoc99_vsscanf () at /lib64/libc.so.6
> #3 0x00007f11a2694c67 in __isoc99_sscanf () at /lib64/libc.so.6
> #4 0x00007f11a15538e2 in epoxy_glx_version () at /lib64/libepoxy.so.0
> #5 0x00007f11a45a21e9 in gdk_x11_screen_init_gl () at /lib64/libgdk-3.so.0
> #6 0x00007f11a45a259a in _gdk_x11_screen_update_visuals_for_gl ()
> at /lib64/libgdk-3.so.0
> #7 0x00007f11a45ab1f6 in _gdk_x11_screen_init_visuals ()
> at /lib64/libgdk-3.so.0
> #8 0x00007f11a45a8230 in _gdk_x11_screen_new () at /lib64/libgdk-3.so.0
> #9 0x00007f11a45980c8 in _gdk_x11_display_open () at /lib64/libgdk-3.so.0
> #10 0x00007f11a456cb85 in gdk_display_manager_open_display ()
> at /lib64/libgdk-3.so.0
> #11 0x00007f11a4a56b40 in gtk_init_with_args () at /lib64/libgtk-3.so.0
> #12 0x0000559da299d5ee in main ()
> (gdb)
>
> LXDE and XFCE kind of work which is to say the desktops come up but in
> LXDE applications except for the action button aren't working, however this
> may be because they aren't fully installed, and XFCE seems to be missing a
> lot of it's components, ICEWM works, kde isn't installed, gnome isn't
> installed. This
> was the mate spin of fedora and was mostly the system defaults.
>
> Although the core is on mate-session, it WAS working before tonights
> updates and they did not include update for mate. I can not test the machine
> locally because it is a virtual machine running under KVM/Qemu.
>
>> If you want to have ABRT out of the way,
>> echo "core" > /proc/sys/kernel/core_pattern
>> will take care of that.
>
> Yes, did that which is how I got the core. I still have it if you would
> like to examine further.
>
> I installed every other desktop available and the only one that worked
> properly was icewm.
>
>> Mihai
>>
>>
> _______________________________________________
> x2go-user mailing list
> x2go-user at lists.x2go.org
> http://lists.x2go.org/listinfo/x2go-user
>
More information about the x2go-user
mailing list