This only seems to be affecting one user. He has a NIS account and has tried 2 NIS accounts to make sure. He's running a Mac with the latest X2Go (2.7.11) connecting to a Fedora 25 server with NIS, choosing the MATE desktop and audio disabled. We made sure to check the security settings as per this older post screenshot <http://lists.x2go.org/pipermail/x2go-dev/attachments/20151013/f02b140a/attachment-0001.png> and confirmed the .Xauthority permissions problem <http://lists.x2go.org/pipermail/x2go-dev/2015-October/010733.html> does not exist. Here are some debug-enabled logs.
Feb 16 21:11:57 ourserver /usr/bin/x2gostartagent: x2gostartagent called with options: 800x600 adsl 16m-jpeg-9 unix-kde-depth_32 us query 0 D MATE both Feb 16 21:11:57 ourserver /usr/bin/x2gosessionlimit[25474]: x2gosessionlimit has been called Feb 16 21:11:57 ourserver /usr/bin/x2golistsessions[25477]: x2golistsessions has been called with options: --all-servers Feb 16 21:11:59 ourserver /usr/sbin/x2gocleansessions[26305]: NISuser-64-1487297518_stDMATE_dp32: state file for this session does not exist: /tmp/.x2go-NISuser/C-NISuser-64-1487297518_stDMATE_dp32/state (this can be ignored during session startups) Feb 16 21:12:00 ourserver /usr/bin/x2gofeature: x2gofeature called with options: X2GO_RUN_EXTENSIONS Feb 16 21:12:00 ourserver /usr/share/x2go/x2gofeature.d/x2goserver-extensions.features: x2goserver-extensions.features called with options: X2GO_RUN_EXTENSIONS Feb 16 21:12:00 ourserver /usr/bin/x2goserver-run-extensions: x2goserver-run-extensions called with options: NISuser-64-1487297518_stDMATE_dp32 pre-start Feb 16 21:12:00 ourserver /usr/bin/x2gostartagent: successfully started X2Go agent session with ID NISuser-64-1487297518_stDMATE_dp32 Feb 16 21:12:00 ourserver /usr/bin/x2gofeature: x2gofeature called with options: X2GO_RUN_EXTENSIONS Feb 16 21:12:00 ourserver /usr/share/x2go/x2gofeature.d/x2goserver-extensions.features: x2goserver-extensions.features called with options: X2GO_RUN_EXTENSIONS Feb 16 21:12:00 ourserver /usr/bin/x2goserver-run-extensions: x2goserver-run-extensions called with options: NISuser-64-1487297518_stDMATE_dp32 post-start Feb 16 21:12:01 ourserver /usr/bin/x2gostartagent: blocking creation of agent's keyboard file /tmp/.x2go-NISuser/C-NISuser-64-1487297518_stDMATE_dp32/keyboard as requested by session startup command Feb 16 21:12:05 ourserver audit: CRYPTO_KEY_USER pid=25308 uid=0 auid=xxxx ses=916 msg='op=destroy kind=server fp=SHA256:ed:ac:95:b9:6d:a7:65:a8:79:a8:79:4e:41:3c:6b:58:c8:5b:37:10:c1:6a:bc:8f:2f:1c:f1:00:98:4f:2a:78 direction=? spid=25774 suid=xxxx exe="/usr/sbin/sshd" hostname=? addr=? terminal=? res=success' Feb 16 21:12:05 ourserver /usr/bin/x2gocmdexitmessage: x2gocmdexitmessage called with options: NISuser-64-1487297518_stDMATE_dp32 Feb 16 21:12:05 ourserver audit: USER_END pid=25308 uid=0 auid=xxxx ses=916 msg='op=PAM:session_close grantors=pam_selinux,pam_loginuid,pam_selinux,pam_namespace,pam_keyinit,pam_keyinit,pam_limits,pam_systemd,pam_unix acct="NISuser" exe="/usr/sbin/sshd" hostname=ipaddress addr=ipaddress terminal=ssh res=success' Feb 16 21:12:05 ourserver audit: CRED_DISP pid=25308 uid=0 auid=xxxx ses=916 msg='op=PAM:setcred grantors=pam_unix acct="NISuser" exe="/usr/sbin/sshd" hostname=ipaddress addr=ipaddress terminal=ssh res=success' Feb 16 21:12:05 ourserver audit: USER_END pid=25308 uid=0 auid=xxxx ses=916 msg='op=login id=xxxx exe="/usr/sbin/sshd" hostname=ipaddress addr=ipaddress terminal=ssh res=success' Feb 16 21:12:05 ourserver audit: USER_LOGOUT pid=25308 uid=0 auid=xxxx ses=916 msg='op=login id=xxxx exe="/usr/sbin/sshd" hostname=ipaddress addr=ipaddress terminal=ssh res=success'
On 17.02.2017 07:41 PM, Robert Kudyba wrote:
This only seems to be affecting one user. He has a NIS account and has tried 2 NIS accounts to make sure. He's running a Mac with the latest X2Go (2.7.11)
You probably meant XQuartz here.
connecting to a Fedora 25 server with NIS, choosing the MATE desktop and audio disabled. We made sure to check the security settings as per this older post screenshot <http://lists.x2go.org/pipermail/x2go-dev/attachments/20151013/f02b140a/attachment-0001.png> and confirmed the .Xauthority permissions problem <http://lists.x2go.org/pipermail/x2go-dev/2015-October/010733.html> does not exist. Here are some debug-enabled logs.
What exactly does crash and when? The client? x2goagent on the server?
Mihai
I am not on a Mac, running Ubuntu with the very latest 4.0.0.1 nightly
build x2go client and connecting to Fedora, and only Fedora also with the Mate desktop, nxagent cores on Fedora on a regular basis. I do not have this problem with Centos 6/7, Scientific Linux 6/7, all of which are Redhat releases, only with Fedora. Mint, Deb, and Ubuntu are all stable for me now, the only other OS I have issues with is OpenSuse and that because I can't run the latest release owing to the inavailability of a modern LibNX there.
-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_- 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, Mihai Moldovan wrote:
Date: Sun, 26 Feb 2017 05:38:51 +0100 From: Mihai Moldovan <ionic@ionic.de> To: Robert Kudyba <rkudyba@fordham.edu>, x2go-user@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 17.02.2017 07:41 PM, Robert Kudyba wrote:
This only seems to be affecting one user. He has a NIS account and has tried 2 NIS accounts to make sure. He's running a Mac with the latest X2Go (2.7.11)
You probably meant XQuartz here.
connecting to a Fedora 25 server with NIS, choosing the MATE desktop and audio disabled. We made sure to check the security settings as per this older post screenshot <http://lists.x2go.org/pipermail/x2go-dev/attachments/20151013/f02b140a/attachment-0001.png> and confirmed the .Xauthority permissions problem <http://lists.x2go.org/pipermail/x2go-dev/2015-October/010733.html> does not exist. Here are some debug-enabled logs.
What exactly does crash and when? The client? x2goagent on the server?
Mihai
Actually that's not entirely true when I say I am not on a Mac, I am on
a Mac Pro 1,1 but it is running the 64-bit version of Ubuntu 16.10.
-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_- 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 Sat, 25 Feb 2017, Robert Dinse wrote:
Date: Sat, 25 Feb 2017 20:44:07 -0800 (PST) From: Robert Dinse <nanook@eskimo.com> To: Mihai Moldovan <ionic@ionic.de> Cc: x2go-user@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
I am not on a Mac, running Ubuntu with the very latest 4.0.0.1 nightly
build x2go client and connecting to Fedora, and only Fedora also with the Mate desktop, nxagent cores on Fedora on a regular basis. I do not have this problem with Centos 6/7, Scientific Linux 6/7, all of which are Redhat releases, only with Fedora. Mint, Deb, and Ubuntu are all stable for me now, the only other OS I have issues with is OpenSuse and that because I can't run the latest release owing to the inavailability of a modern LibNX there.
-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_- 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, Mihai Moldovan wrote:
Date: Sun, 26 Feb 2017 05:38:51 +0100 From: Mihai Moldovan <ionic@ionic.de> To: Robert Kudyba <rkudyba@fordham.edu>, x2go-user@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 17.02.2017 07:41 PM, Robert Kudyba wrote:
This only seems to be affecting one user. He has a NIS account and has tried 2 NIS accounts to make sure. He's running a Mac with the latest X2Go (2.7.11)
You probably meant XQuartz here.
connecting to a Fedora 25 server with NIS, choosing the MATE desktop and audio disabled. We made sure to check the security settings as per this older post screenshot <http://lists.x2go.org/pipermail/x2go-dev/attachments/20151013/f02b140a/attachment-0001.png> and confirmed the .Xauthority permissions problem <http://lists.x2go.org/pipermail/x2go-dev/2015-October/010733.html> does not exist. Here are some debug-enabled logs.
What exactly does crash and when? The client? x2goagent on the server?
Mihai
x2go-user mailing list x2go-user@lists.x2go.org http://lists.x2go.org/listinfo/x2go-user
connecting to a Fedora 25 server with NIS, choosing the MATE desktop and audio disabled. We made sure to check the security settings as per this older post screenshot <http://lists.x2go.org/pipermail/x2go-dev/attachments/20151013/f02b140a/ attachment-0001.png> and confirmed the .Xauthority permissions problem <http://lists.x2go.org/pipermail/x2go-dev/2015-October/010733.html> does not exist. Here are some debug-enabled logs.
What exactly does crash and when? The client? x2goagent on the server?
The X2Go client on his Mac desktop just goes black and kicks him out.
We have been working around it with XFCE and then using the work around for DBUS when the same user is logged in via ssh and X2go.
On 26.02.2017 05:51 AM, Robert Kudyba wrote:
The X2Go client on his Mac desktop just goes black and kicks him out.
That would be the new black proxy window with the "X2GO" branding in dark grey letters, right? It's not a real crash, it just terminates? (I.e., OS X doesn't show an appcrash dialog.)
Normally, mate-session should start in there.
Maybe taking a look at ~NISuser/.xsession-x2go-errors might show something interesting.
We have been working around it with XFCE and then using the work around for DBUS when the same user is logged in via ssh and X2go.
So XFCE is working, while MATE is not?
Mihai
That would be the new black proxy window with the "X2GO" branding in dark grey letters, right? It's not a real crash, it just terminates? (I.e., OS X doesn't show an appcrash dialog.)
Yes just terminates.
Maybe taking a look at ~NISuser/.xsession-x2go-errors might show something interesting.
working around it with XFCE and then using the work around for DBUS
when the same user is logged in via ssh and X2go.
So XFCE is working, while MATE is not?
Well kind of had to build in the XFCE work around mentioned in this bug <http://bugs.x2go.org/cgi-bin/bugreport.cgi?bug=1083>.
Here's what in the log with XFCE:
xfce4-session-Message: SSH authentication agent is already running
gpg-agent[14125]: WARNING: "--write-env-file" is an obsolete option - it has no effect
gpg-agent[14126]: gpg-agent (GnuPG) 2.1.13 started
(xfce4-session:14115): xfce4-session-WARNING **: gpg-agent returned no PID in the variables
(xfce4-session:14115): xfce4-session-WARNING **: xfsm_manager_load_session: Something wrong with /u/sobolev/agw/.cache/sessions/xfce4-session-erdos. dsm.fordham.edu:85, Does it exist? Permissions issue?
(xfwm4:14130): xfwm4-WARNING **: The display does not support the XComposite extension.
(xfwm4:14130): xfwm4-WARNING **: The display does not support the XFixes extension.
(xfwm4:14130): xfwm4-WARNING **: Compositing manager disabled.
Starting Dropbox...
(xfwm4:14130): xfwm4-WARNING **: Error opening /dev/dri/card0: Permission denied
vmware-user: could not open /proc/fs/vmblock/dev
SELinux Troubleshooter: Applet requires SELinux be enabled to run.
(xfsettingsd:14147): xfsettingsd-CRITICAL **: Your XI is too old (1.3) version 1.4 is required.
(xfsettingsd:14147): xfsettingsd-CRITICAL **: Failed to change the keyboard repeat
** (zeitgeist-datahub:14476): WARNING **: kde-recent-document-provider.vala:174: Couldn't find actor for 'kolourpaint'.
(xfwm4:14130): xfwm4-WARNING **: Unmanaged net_wm_state (window 0x340000e, atom "_NET_WM_STATE_STAYS_ON_TOP")
(xfce4-panel:14136): Gtk-CRITICAL **: IA__gtk_widget_show: assertion 'GTK_IS_WIDGET (widget)' failed
(xfce4-panel:14136): Gtk-CRITICAL **: gtk_box_pack: assertion 'GTK_IS_WIDGET (child)' failed
(xfce4-panel:14136): Gtk-CRITICAL **: IA__gtk_widget_show: assertion 'GTK_IS_WIDGET (widget)' failed
(xfce4-panel:14136): Gtk-CRITICAL **: gtk_box_pack: assertion 'GTK_IS_WIDGET (child)' failed
(xfce4-panel:14136): Gtk-CRITICAL **: IA__gtk_widget_show: assertion 'GTK_IS_WIDGET (widget)' failed
(xfce4-panel:14136): Gtk-CRITICAL **: gtk_box_pack: assertion 'GTK_IS_WIDGET (child)' failed
(xfce4-panel:14136): Gtk-CRITICAL **: IA__gtk_widget_show: assertion 'GTK_IS_WIDGET (widget)' failed
(xfce4-panel:14136): Gtk-CRITICAL **: gtk_box_pack: assertion 'GTK_IS_WIDGET (child)' failed
** (xfdesktop:14140): CRITICAL **: xfce_backdrop_loader_closed_cb: assertion 'XFCE_IS_BACKDROP(backdrop)' failed
(xfce4-terminal:16430): GLib-WARNING **: GChildWatchSource: Exit status of a child process was requested but ECHILD was received by waitpid(). Most likely the process is ignoring SIGCHLD, or some other thread is invoking waitpid() with a nonpositive first argument; either behavior can break applications that use g_child_watch_add()/g_spawn_sync() either directly or indirectly.
(xfce4-session:14115): Gtk-CRITICAL **: IA__gtk_widget_set_visible: assertion 'GTK_IS_WIDGET (widget)' failed
(xfce4-session:14115): GLib-GObject-CRITICAL **: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
/usr/local/sbin/start-xfce: line 4: EOF: command not found
Thunar: Fatal IO error 11 (Resource temporarily unavailable) on X server :85.0.
Gdk-Message: nm-applet: Fatal IO error 11 (Resource temporarily unavailable) on X server :85.0.
xfce-polkit: Fatal IO error 11 (Resource temporarily unavailable) on X server :85.0.
Gdk-Message: blueman-applet: Fatal IO error 11 (Resource temporarily unavailable) on X server :85.0.
Gdk-Message: abrt: Fatal IO error 11 (Resource temporarily unavailable) on X server :85.0.
Gdk-Message: evolution-alarm-notify: Fatal IO error 11 (Resource temporarily unavailable) on X server :85.0.
** (zeitgeist-datahub:14476): WARNING **: zeitgeist-datahub.vala:226: Unable to get name "org.gnome.zeitgeist.datahub" on the bus!
Received signal:15->'Terminated'
On 26.02.2017 06:29 AM, Robert Kudyba wrote:
Well kind of had to build in the XFCE work around mentioned in this bug <http://bugs.x2go.org/cgi-bin/bugreport.cgi?bug=1083>.
Here's what in the log with XFCE:
The non-working MATE log would be more interesting, given that XFCE actually works in your setup. :)
Mihai
I can't find a core and I did my best to make it crash but it does not
seem to be in the mood tonight however dmesg did reveal this:
[168764.604757] x2goagent[2794]: segfault at c1 ip 000055fa1ed65ccc sp 00007ffedf8a7c40 error 4 in nxagent[55fa1ed22000+42f000]
This is on a mate spin of fedora-25 running in a KVM/Qemu virtual machine
on i7-6700k platform. If I can find a core file I'll do a backtrace and forward it but did not find one in any of the directories I normally work in.
-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_- 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, Mihai Moldovan wrote:
Date: Sun, 26 Feb 2017 06:36:24 +0100 From: Mihai Moldovan <ionic@ionic.de> To: Robert Kudyba <rkudyba@fordham.edu> Cc: x2go-user@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 26.02.2017 06:29 AM, Robert Kudyba wrote:
Well kind of had to build in the XFCE work around mentioned in this bug <http://bugs.x2go.org/cgi-bin/bugreport.cgi?bug=1083>.
Here's what in the log with XFCE:
The non-working MATE log would be more interesting, given that XFCE actually works in your setup. :)
Mihai
On Feb 26, 2017, at 12:36 AM, Mihai Moldovan <ionic@ionic.de> wrote:
On 26.02.2017 06:29 AM, Robert Kudyba wrote:
Well kind of had to build in the XFCE work around mentioned in this bug <http://bugs.x2go.org/cgi-bin/bugreport.cgi?bug=1083>.
Here's what in the log with XFCE:
The non-working MATE log would be more interesting, given that XFCE actually works in your setup. :)
My colleague is giving up on MATE. And XFCE has been having intermittent issues and here are some errors/logs. Anything stick out?
xfce4-session-Message: SSH authentication agent is already running gpg-agent[27604]: WARNING: "--write-env-file" is an obsolete option - it has no effect gpg-agent: a gpg-agent is already running - not starting a new one
(xfce4-session:27589): xfce4-session-WARNING **: gpg-agent returned no PID in the variables
(xfce4-session:27589): xfce4-session-WARNING **: xfsm_manager_load_session: Something wrong with /path/.cache/sessions/xfce4-session-erdos.dsm.fordham.edu:90, Does it exist? Permissions issue?
(xfwm4:27607): xfwm4-WARNING **: The display does not support the XComposite extension.
(xfwm4:27607): xfwm4-WARNING **: The display does not support the XFixes extension.
(xfwm4:27607): xfwm4-WARNING **: Compositing manager disabled.
(xfwm4:27607): xfwm4-WARNING **: Error opening /dev/dri/card0: Permission denied Starting Dropbox... (tracker-extract:27814): Tracker-WARNING **: Could not open pdf file ‘/path/midterm.pdf': No such file or directory
** (zeitgeist-datahub:27892): WARNING **: kde-recent-document-provider.vala:174: Couldn't find actor for 'kolourpaint'. vmware-user: could not open /proc/fs/vmblock/dev KCrash: Application 'kgpg' crashing... KCrash: Attempting to start /usr/libexec/drkonqi from kdeinit Warning: connect() failed: : No such file or directory KCrash: Attempting to start /usr/libexec/drkonqi directly SELinux Troubleshooter: Applet requires SELinux be enabled to run.
(xfsettingsd:27617): xfsettingsd-CRITICAL **: Your XI is too old (1.3) version 1.4 is required.
(xfsettingsd:27617): xfsettingsd-CRITICAL **: Failed to change the keyboard repeat KCrash: Application 'drkonqi' crashing... KCrash: Attempting to start /usr/libexec/drkonqi from kdeinit Warning: connect() failed: : No such file or directory KCrash: Attempting to start /usr/libexec/drkonqi directly KCrash: Application 'drkonqi' crashing... Dropbox isn't running! Done!
(xfwm4:27607): xfwm4-WARNING **: Unmanaged net_wm_state (window 0x1c0000e, atom "_NET_WM_STATE_STAYS_ON_TOP")
(xfce4-panel:27611): Gtk-CRITICAL **: IA__gtk_widget_show: assertion 'GTK_IS_WIDGET (widget)' failed
(xfce4-panel:27611): Gtk-CRITICAL **: gtk_box_pack: assertion 'GTK_IS_WIDGET (child)' failed
(xfce4-panel:27611): Gtk-CRITICAL **: IA__gtk_widget_show: assertion 'GTK_IS_WIDGET (widget)' failed
(xfce4-panel:27611): Gtk-CRITICAL **: gtk_box_pack: assertion 'GTK_IS_WIDGET (child)' failed
(xfce4-panel:27611): Gtk-CRITICAL **: IA__gtk_widget_show: assertion 'GTK_IS_WIDGET (widget)' failed
(xfce4-panel:27611): Gtk-CRITICAL **: gtk_box_pack: assertion 'GTK_IS_WIDGET (child)' failed
(xfce4-panel:27611): Gtk-CRITICAL **: IA__gtk_widget_show: assertion 'GTK_IS_WIDGET (widget)' failed
(xfce4-panel:27611): Gtk-CRITICAL **: gtk_box_pack: assertion 'GTK_IS_WIDGET (child)' failed
** (zeitgeist-datahub:27892): WARNING **: downloads-directory-provider.vala:120: Couldn't process /path/.dropbox-dist-old-GHFOH6: Error when getting information for file '/path/.dropbox-dist-old-GHFOH6': No such file or directory
** (xfdesktop:27615): CRITICAL **: xfce_backdrop_loader_closed_cb: assertion 'XFCE_IS_BACKDROP(backdrop)' failed
** (zeitgeist-datahub:27892): WARNING **: zeitgeist-datahub.vala:209: Error during inserting events: GDBus.Error:org.gnome.zeitgeist.EngineError.InvalidArgument: Incomplete event: interpretation, manifestation and actor are required
** (zeitgeist-datahub:27892): WARNING **: zeitgeist-datahub.vala:209: Error during inserting events: GDBus.Error:org.gnome.zeitgeist.EngineError.InvalidArgument: Incomplete event: interpretation, manifestation and actor are required
On 28.02.2017 05:31 PM, Robert Kudyba wrote:
My colleague is giving up on MATE. And XFCE has been having intermittent issues and here are some errors/logs. Anything stick out?
Difficult to say without knowing what to look for?
I've seen kgpg crashing in that log, but that may or may not be a problem.
The missing Composite and Fixes extensions are normal - you won't get any compositing effects, but that's okay.
Other than that, there's no major problem recorded in there.
This said, I've had a user on FC25 yesterday on IRC and he has reported problems with Emacs - which was built with GTK3 support. After he rebuilt it with GTK2, it started to work.
I also (ab)used him to test MATE and found out that mate-session is crashing upon start. Any GTK3 application crashes, basically, because of a bug in al ibrary used by GTK3 (libepoxy), that has been filed in Red Hats bugtracker for Fedora 24 already and fixed upstream for a while.
The root cause of that is that for some reason the GLX version is not reported correctly - instead a NULL pointer is thrown out. I don't see this behavior on Debian Jessie, which hints at a deeper problem with our nx-libs builds on Fedora 25 (and maybe even 24?)
I haven't yet been able to figure out why nxagent isn't doing what it should be doing, though.
Mihai
On Feb 28, 2017, at 11:51 AM, Mihai Moldovan <ionic@ionic.de> wrote:
On 28.02.2017 05:31 PM, Robert Kudyba wrote:
My colleague is giving up on MATE. And XFCE has been having intermittent issues and here are some errors/logs. Anything stick out?
Difficult to say without knowing what to look for?
I've seen kgpg crashing in that log, but that may or may not be a problem.
The missing Composite and Fixes extensions are normal - you won't get any compositing effects, but that's okay.
Other than that, there's no major problem recorded in there.
This said, I've had a user on FC25 yesterday on IRC and he has reported problems with Emacs - which was built with GTK3 support. After he rebuilt it with GTK2, it started to work.
I also (ab)used him to test MATE and found out that mate-session is crashing upon start. Any GTK3 application crashes, basically, because of a bug in al ibrary used by GTK3 (libepoxy), that has been filed in Red Hats bugtracker for Fedora 24 already and fixed upstream for a while.
The root cause of that is that for some reason the GLX version is not reported correctly - instead a NULL pointer is thrown out. I don't see this behavior on Debian Jessie, which hints at a deeper problem with our nx-libs builds on Fedora 25 (and maybe even 24?)
I haven't yet been able to figure out why nxagent isn't doing what it should be doing, though.
Yes that emacs crash has been an issue for quite a while: https://bugzilla.redhat.com/show_bug.cgi?id=1349412 <https://bugzilla.redhat.com/show_bug.cgi?id=1349412>
Now I have a core dump to share with MATE and some logs from the server side. No errors under my user name but hope these are helpful:
Feb 28 15:27:18 myworkstation systemd-logind: New session 2039 of user myuser. Feb 28 15:27:18 myworkstation /usr/bin/x2gostartagent: x2gostartagent called with options: 800x600 adsl 16m-jpeg-9 unix-kde-depth_32 us query 0 D MATE both Feb 28 15:27:18 myworkstation /usr/bin/x2gosessionlimit[13047]: x2gosessionlimit has been called Feb 28 15:27:18 myworkstation /usr/bin/x2golistsessions[13050]: x2golistsessions has been called with options: --all-servers Feb 28 15:27:20 myworkstation /usr/sbin/x2gocleansessions[15005]: myuser-59-1488313639_stDMATE_dp32: state file for this session does not exist: /tmp/.x2go-myuser/C-myuser-59-1488313639_stDMATE_dp32/state (this can be ignored during session startups) Feb 28 15:27:21 myworkstation /usr/bin/x2gofeature: x2gofeature called with options: X2GO_RUN_EXTENSIONS Feb 28 15:27:21 myworkstation /usr/share/x2go/x2gofeature.d/x2goserver-extensions.features: x2goserver-extensions.features called with options: X2GO_RUN_EXTENSIONS Feb 28 15:27:21 myworkstation /usr/bin/x2goserver-run-extensions: x2goserver-run-extensions called with options: myuser-59-1488313639_stDMATE_dp32 pre-start Feb 28 15:27:21 myworkstation /usr/bin/x2gostartagent: successfully started X2Go agent session with ID myuser-59-1488313639_stDMATE_dp32 Feb 28 15:27:21 myworkstation /usr/bin/x2gofeature: x2gofeature called with options: X2GO_RUN_EXTENSIONS Feb 28 15:27:21 myworkstation /usr/share/x2go/x2gofeature.d/x2goserver-extensions.features: x2goserver-extensions.features called with options: X2GO_RUN_EXTENSIONS Feb 28 15:27:21 myworkstation /usr/bin/x2goserver-run-extensions: x2goserver-run-extensions called with options: myuser-59-1488313639_stDMATE_dp32 post-start Feb 28 15:27:22 myworkstation /usr/bin/x2gostartagent: blocking creation of agent's keyboard file /tmp/.x2go-myuser/C-myuser-59-1488313639_stDMATE_dp32/keyboard as requested by session startup command Feb 28 15:27:22 myworkstation /usr/bin/x2goruncommand: x2goruncommand called with options: 59 13246 myuser-59-1488313639_stDMATE_dp32 35964 mate-session nosnd D Feb 28 15:27:22 myworkstation /usr/bin/x2gofeature: x2gofeature called with options: X2GO_RUN_EXTENSIONS Feb 28 15:27:22 myworkstation /usr/share/x2go/x2gofeature.d/x2goserver-extensions.features: x2goserver-extensions.features called with options: X2GO_RUN_EXTENSIONS Feb 28 15:27:22 myworkstation /usr/bin/x2goserver-run-extensions: x2goserver-run-extensions called with options: myuser-59-1488313639_stDMATE_dp32 pre-runcommand Feb 28 15:27:22 myworkstation /usr/bin/x2gosetkeyboard: x2gosetkeyboard called with options: Feb 28 15:27:22 myworkstation /usr/bin/x2gofeature: x2gofeature called with options: X2GO_XSESSION Feb 28 15:27:23 myworkstation /usr/bin/x2gosetkeyboard: /u/erdos/myuser/.x2go/C-myuser-59-1488313639_stDMATE_dp32/keyboard is blocked, not setting keyboard parameters from client-side settings Feb 28 15:27:23 myworkstation /usr/share/x2go/x2gofeature.d/x2goserver-extensions.features: x2goserver-extensions.features called with options: X2GO_XSESSION Feb 28 15:27:23 myworkstation /usr/share/x2go/x2gofeature.d/x2goserver.features: x2goserver.features called with options: X2GO_XSESSION Feb 28 15:27:23 myworkstation /usr/sbin/x2gocleansessions[15005]: myuser-59-1488313579_stDXFCE_dp32: found stale X-server process (11415), sending SIGKILL Feb 28 15:27:23 myworkstation /usr/sbin/x2gocleansessions[15005]: myuser-59-1488313579_stDXFCE_dp32, pid 11415: cleaning up stale X11 socket file: /tmp/.X11-unix/X59 Feb 28 15:27:23 myworkstation /usr/sbin/x2gocleansessions[15005]: myuser-59-1488313579_stDXFCE_dp32, pid 11415: cleaning up stale X11 lock file: /tmp/.X59-lock Feb 28 15:27:23 myworkstation su: (to myuser) root on none Feb 28 15:27:23 myworkstation systemd: Started Session c27 of user myuser. Feb 28 15:27:23 myworkstation /usr/bin/x2goumount-session[13528]: x2goumount-session has been called with options: myuser-59-1488313579_stDXFCE_dp32 Feb 28 15:27:23 myworkstation su: (to myuser) root on none Feb 28 15:27:23 myworkstation systemd: Started Session c28 of user myuser. Feb 28 15:27:25 myworkstation kernel: mate-session[13511]: segfault at 0 ip 00007f5c1789635f sp 00007fff07f02758 error 4 in libc-2.24.so[7f5c177ff000+1bd000] Feb 28 15:27:25 myworkstation systemd: Started Process Core Dump (PID 13551/UID 0). Feb 28 15:27:25 myworkstation systemd-coredump: Process 13511 (mate-session) of user 6105 dumped core.#012#012Stack trace of thread 13511:#012#0 0x00007f5c1789635f __rawmemchr (libc.so.6)#012#1 0x00007f5c1787e832 _IO_str_init_static_internal (libc.so.6)#012#2 0x00007f5c1786bcc7 __isoc99_vsscanf (libc.so.6)#012#3 0x00007f5c1786bc67 __isoc99_sscanf (libc.so.6)#012#4 0x00007f5c1672a8e2 epoxy_glx_version (libepoxy.so.0)#012#5 0x00007f5c1977a1e9 gdk_x11_screen_init_gl (libgdk-3.so.0)#012#6 0x00007f5c1977a59a _gdk_x11_screen_update_visuals_for_gl (libgdk-3.so.0)#012#7 0x00007f5c197831f6 _gdk_x11_screen_init_visuals (libgdk-3.so.0)#012#8 0x00007f5c19780230 _gdk_x11_screen_new (libgdk-3.so.0)#012#9 0x00007f5c197700c8 _gdk_x11_display_open (libgdk-3.so.0)#012#10 0x00007f5c19744b85 gdk_display_manager_open_display (libgdk-3.so.0)#012#11 0x00007f5c19c2eb40 gtk_init_with_args (libgtk-3.so.0)#012#12 0x000056162a6195ee main (mate-session)#012#13 0x00007f5c1781f401 __libc_start_main (libc.so.6)#012#14 0x000056162a61a12a _start (mate-session) Feb 28 15:27:25 myworkstation /usr/bin/x2gofeature: x2gofeature called with options: X2GO_RUN_EXTENSIONS Feb 28 15:27:25 myworkstation /usr/share/x2go/x2gofeature.d/x2goserver-extensions.features: x2goserver-extensions.features called with options: X2GO_RUN_EXTENSIONS Feb 28 15:27:25 myworkstation /usr/bin/x2goserver-run-extensions: x2goserver-run-extensions called with options: myuser-59-1488313639_stDMATE_dp32 post-runcommand Feb 28 15:27:25 myworkstation /usr/bin/x2gofeature: x2gofeature called with options: X2GO_DESKTOPSHARING Feb 28 15:27:25 myworkstation /usr/share/x2go/x2gofeature.d/x2goserver-extensions.features: x2goserver-extensions.features called with options: X2GO_DESKTOPSHARING Feb 28 15:27:25 myworkstation /usr/share/x2go/x2gofeature.d/x2goserver.features: x2goserver.features called with options: X2GO_DESKTOPSHARING Feb 28 15:27:25 myworkstation /usr/bin/x2goumount-session[13631]: x2goumount-session has been called with options: myuser-59-1488313639_stDMATE_dp32 Feb 28 15:27:26 myworkstation /usr/bin/x2gocmdexitmessage: x2gocmdexitmessage called with options: myuser-59-1488313639_stDMATE_dp32 Feb 28 15:27:26 myworkstation systemd-logind: Removed session 2039.
With Fedora 25 it was working with Mate fine for me until very recently,
as recently as February 7th. Then some update broke it. Because several things were updated simultaneously, x2go, mate, and libc, it is hard to know which was the cause but mate-session and many xfce programs all core with a segfault in libc.
I am now in the process of restoring the machine from a February 7th
backup and will update things individually to determine which broke.
-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_- 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 Tue, 28 Feb 2017, Robert Kudyba wrote:
Date: Tue, 28 Feb 2017 15:37:19 -0500 From: Robert Kudyba <rkudyba@fordham.edu> To: Mihai Moldovan <ionic@ionic.de> Cc: x2go-user@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 Feb 28, 2017, at 11:51 AM, Mihai Moldovan <ionic@ionic.de> wrote:
On 28.02.2017 05:31 PM, Robert Kudyba wrote:
My colleague is giving up on MATE. And XFCE has been having intermittent issues and here are some errors/logs. Anything stick out?
Difficult to say without knowing what to look for?
I've seen kgpg crashing in that log, but that may or may not be a problem.
The missing Composite and Fixes extensions are normal - you won't get any compositing effects, but that's okay.
Other than that, there's no major problem recorded in there.
This said, I've had a user on FC25 yesterday on IRC and he has reported problems with Emacs - which was built with GTK3 support. After he rebuilt it with GTK2, it started to work.
I also (ab)used him to test MATE and found out that mate-session is crashing upon start. Any GTK3 application crashes, basically, because of a bug in al ibrary used by GTK3 (libepoxy), that has been filed in Red Hats bugtracker for Fedora 24 already and fixed upstream for a while.
The root cause of that is that for some reason the GLX version is not reported correctly - instead a NULL pointer is thrown out. I don't see this behavior on Debian Jessie, which hints at a deeper problem with our nx-libs builds on Fedora 25 (and maybe even 24?)
I haven't yet been able to figure out why nxagent isn't doing what it should be doing, though.
Yes that emacs crash has been an issue for quite a while: https://bugzilla.redhat.com/show_bug.cgi?id=1349412 <https://bugzilla.redhat.com/show_bug.cgi?id=1349412>
Now I have a core dump to share with MATE and some logs from the server side. No errors under my user name but hope these are helpful:
Feb 28 15:27:18 myworkstation systemd-logind: New session 2039 of user myuser. Feb 28 15:27:18 myworkstation /usr/bin/x2gostartagent: x2gostartagent called with options: 800x600 adsl 16m-jpeg-9 unix-kde-depth_32 us query 0 D MATE both Feb 28 15:27:18 myworkstation /usr/bin/x2gosessionlimit[13047]: x2gosessionlimit has been called Feb 28 15:27:18 myworkstation /usr/bin/x2golistsessions[13050]: x2golistsessions has been called with options: --all-servers Feb 28 15:27:20 myworkstation /usr/sbin/x2gocleansessions[15005]: myuser-59-1488313639_stDMATE_dp32: state file for this session does not exist: /tmp/.x2go-myuser/C-myuser-59-1488313639_stDMATE_dp32/state (this can be ignored during session startups) Feb 28 15:27:21 myworkstation /usr/bin/x2gofeature: x2gofeature called with options: X2GO_RUN_EXTENSIONS Feb 28 15:27:21 myworkstation /usr/share/x2go/x2gofeature.d/x2goserver-extensions.features: x2goserver-extensions.features called with options: X2GO_RUN_EXTENSIONS Feb 28 15:27:21 myworkstation /usr/bin/x2goserver-run-extensions: x2goserver-run-extensions called with options: myuser-59-1488313639_stDMATE_dp32 pre-start Feb 28 15:27:21 myworkstation /usr/bin/x2gostartagent: successfully started X2Go agent session with ID myuser-59-1488313639_stDMATE_dp32 Feb 28 15:27:21 myworkstation /usr/bin/x2gofeature: x2gofeature called with options: X2GO_RUN_EXTENSIONS Feb 28 15:27:21 myworkstation /usr/share/x2go/x2gofeature.d/x2goserver-extensions.features: x2goserver-extensions.features called with options: X2GO_RUN_EXTENSIONS Feb 28 15:27:21 myworkstation /usr/bin/x2goserver-run-extensions: x2goserver-run-extensions called with options: myuser-59-1488313639_stDMATE_dp32 post-start Feb 28 15:27:22 myworkstation /usr/bin/x2gostartagent: blocking creation of agent's keyboard file /tmp/.x2go-myuser/C-myuser-59-1488313639_stDMATE_dp32/keyboard as requested by session startup command Feb 28 15:27:22 myworkstation /usr/bin/x2goruncommand: x2goruncommand called with options: 59 13246 myuser-59-1488313639_stDMATE_dp32 35964 mate-session nosnd D Feb 28 15:27:22 myworkstation /usr/bin/x2gofeature: x2gofeature called with options: X2GO_RUN_EXTENSIONS Feb 28 15:27:22 myworkstation /usr/share/x2go/x2gofeature.d/x2goserver-extensions.features: x2goserver-extensions.features called with options: X2GO_RUN_EXTENSIONS Feb 28 15:27:22 myworkstation /usr/bin/x2goserver-run-extensions: x2goserver-run-extensions called with options: myuser-59-1488313639_stDMATE_dp32 pre-runcommand Feb 28 15:27:22 myworkstation /usr/bin/x2gosetkeyboard: x2gosetkeyboard called with options: Feb 28 15:27:22 myworkstation /usr/bin/x2gofeature: x2gofeature called with options: X2GO_XSESSION Feb 28 15:27:23 myworkstation /usr/bin/x2gosetkeyboard: /u/erdos/myuser/.x2go/C-myuser-59-1488313639_stDMATE_dp32/keyboard is blocked, not setting keyboard parameters from client-side settings Feb 28 15:27:23 myworkstation /usr/share/x2go/x2gofeature.d/x2goserver-extensions.features: x2goserver-extensions.features called with options: X2GO_XSESSION Feb 28 15:27:23 myworkstation /usr/share/x2go/x2gofeature.d/x2goserver.features: x2goserver.features called with options: X2GO_XSESSION Feb 28 15:27:23 myworkstation /usr/sbin/x2gocleansessions[15005]: myuser-59-1488313579_stDXFCE_dp32: found stale X-server process (11415), sending SIGKILL Feb 28 15:27:23 myworkstation /usr/sbin/x2gocleansessions[15005]: myuser-59-1488313579_stDXFCE_dp32, pid 11415: cleaning up stale X11 socket file: /tmp/.X11-unix/X59 Feb 28 15:27:23 myworkstation /usr/sbin/x2gocleansessions[15005]: myuser-59-1488313579_stDXFCE_dp32, pid 11415: cleaning up stale X11 lock file: /tmp/.X59-lock Feb 28 15:27:23 myworkstation su: (to myuser) root on none Feb 28 15:27:23 myworkstation systemd: Started Session c27 of user myuser. Feb 28 15:27:23 myworkstation /usr/bin/x2goumount-session[13528]: x2goumount-session has been called with options: myuser-59-1488313579_stDXFCE_dp32 Feb 28 15:27:23 myworkstation su: (to myuser) root on none Feb 28 15:27:23 myworkstation systemd: Started Session c28 of user myuser. Feb 28 15:27:25 myworkstation kernel: mate-session[13511]: segfault at 0 ip 00007f5c1789635f sp 00007fff07f02758 error 4 in libc-2.24.so[7f5c177ff000+1bd000] Feb 28 15:27:25 myworkstation systemd: Started Process Core Dump (PID 13551/UID 0). Feb 28 15:27:25 myworkstation systemd-coredump: Process 13511 (mate-session) of user 6105 dumped core.#012#012Stack trace of thread 13511:#012#0 0x00007f5c1789635f __rawmemchr (libc.so.6)#012#1 0x00007f5c1787e832 _IO_str_init_static_internal (libc.so.6)#012#2 0x00007f5c1786bcc7 __isoc99_vsscanf (libc.so.6)#012#3 0x00007f5c1786bc67 __isoc99_sscanf (libc.so.6)#012#4 0x00007f5c1672a8e2 epoxy_glx_version (libepoxy.so.0)#012#5 0x00007f5c1977a1e9 gdk_x11_screen_init_gl (libgdk-3.so.0)#012#6 0x00007f5c1977a59a _gdk_x11_screen_update_visuals_for_gl (libgdk-3.so.0)#012#7 0x00007f5c197831f6 _gdk_x11_screen_init_visuals (libgdk-3.so.0)#012#8 0x00007f5c19780230 _gdk_x11_screen_new (libgdk-3.so.0)#012#9 0x00007f5c197700c8 _gdk_x11_display_open (libgdk-3.so.0)#012#10 0x00007f5c19744b85 gdk_display_manager_open_display (libgdk-3.so.0)#012#11 0x00007f5c19c2eb40 gtk_init_with_args (libgtk-3.so.0)#012#12 0x000056162a6195ee main (mate-session)#012#13 0x00007f5c1781f401 __libc_start_main (li bc.so.6)#012#14 0x000056162a61a12a _start (mate-session) Feb 28 15:27:25 myworkstation /usr/bin/x2gofeature: x2gofeature called with options: X2GO_RUN_EXTENSIONS Feb 28 15:27:25 myworkstation /usr/share/x2go/x2gofeature.d/x2goserver-extensions.features: x2goserver-extensions.features called with options: X2GO_RUN_EXTENSIONS Feb 28 15:27:25 myworkstation /usr/bin/x2goserver-run-extensions: x2goserver-run-extensions called with options: myuser-59-1488313639_stDMATE_dp32 post-runcommand Feb 28 15:27:25 myworkstation /usr/bin/x2gofeature: x2gofeature called with options: X2GO_DESKTOPSHARING Feb 28 15:27:25 myworkstation /usr/share/x2go/x2gofeature.d/x2goserver-extensions.features: x2goserver-extensions.features called with options: X2GO_DESKTOPSHARING Feb 28 15:27:25 myworkstation /usr/share/x2go/x2gofeature.d/x2goserver.features: x2goserver.features called with options: X2GO_DESKTOPSHARING Feb 28 15:27:25 myworkstation /usr/bin/x2goumount-session[13631]: x2goumount-session has been called with options: myuser-59-1488313639_stDMATE_dp32 Feb 28 15:27:26 myworkstation /usr/bin/x2gocmdexitmessage: x2gocmdexitmessage called with options: myuser-59-1488313639_stDMATE_dp32 Feb 28 15:27:26 myworkstation systemd-logind: Removed session 2039.
On 01.03.2017 09:01 AM, Robert Dinse wrote:
With Fedora 25 it was working with Mate fine for me until very recently,
as recently as February 7th. Then some update broke it. Because several things were updated simultaneously, x2go, mate, and libc, it is hard to know which was the cause but mate-session and many xfce programs all core with a segfault in libc.
I am now in the process of restoring the machine from a February 7th
backup and will update things individually to determine which broke.
Please check the other messages to the thread, it looks like a MESA upgrade provoked these failures.
Mihai
This might be the update to Mesa in Fedora
https://bugzilla.redhat.com/show_bug.cgi?id=1427174
A lot of programs won't start in my XFCE desktop under x2go. Even xfce4-terminal
The temporary fix is to downgrade mesa:
dnf downgrade mesa-libGL --allowerasing
On 1 March 2017 at 03:51, Mihai Moldovan <ionic@ionic.de> wrote:
On 28.02.2017 05:31 PM, Robert Kudyba wrote:
My colleague is giving up on MATE. And XFCE has been having intermittent issues and here are some errors/logs. Anything stick out?
Difficult to say without knowing what to look for?
I've seen kgpg crashing in that log, but that may or may not be a problem.
The missing Composite and Fixes extensions are normal - you won't get any compositing effects, but that's okay.
Other than that, there's no major problem recorded in there.
This said, I've had a user on FC25 yesterday on IRC and he has reported problems with Emacs - which was built with GTK3 support. After he rebuilt it with GTK2, it started to work.
I also (ab)used him to test MATE and found out that mate-session is crashing upon start. Any GTK3 application crashes, basically, because of a bug in al ibrary used by GTK3 (libepoxy), that has been filed in Red Hats bugtracker for Fedora 24 already and fixed upstream for a while.
The root cause of that is that for some reason the GLX version is not reported correctly - instead a NULL pointer is thrown out. I don't see this behavior on Debian Jessie, which hints at a deeper problem with our nx-libs builds on Fedora 25 (and maybe even 24?)
I haven't yet been able to figure out why nxagent isn't doing what it should be doing, though.
Mihai
x2go-user mailing list x2go-user@lists.x2go.org http://lists.x2go.org/listinfo/x2go-user
-- Norman Gaywood, Computer Systems Officer School of Science and Technology University of New England Armidale NSW 2351, Australia
ngaywood@une.edu.au http://turing.une.edu.au/~ngaywood Phone: +61 (0)2 6773 2412 Mobile: +61 (0)4 7862 0062
Please avoid sending me Word or Power Point attachments. See http://www.gnu.org/philosophy/no-word-attachments.html
On 28.02.2017 11:43 PM, Norman Gaywood wrote:
This might be the update to Mesa in Fedora
https://bugzilla.redhat.com/show_bug.cgi?id=1427174
A lot of programs won't start in my XFCE desktop under x2go. Even xfce4-terminal
The temporary fix is to downgrade mesa:
dnf downgrade mesa-libGL --allowerasing
Very useful information, thanks!
I had the user run glxinfo and on Fedora 25, he got the exact same message.
I wasn't able to reproduce it on Debian Jessie. There, glxinfo could query the GLX version information correctly and also reported working direct rendering via SGI 1.2/MESA 1.4 Gallium software renderer (or the like, I don't remember the specifics, but certainly not an error.)
Initially I thought this might be a problem with nx-libs. If it's really a bug in MESA, that would be good, because is a chance this problem can be fixed by fixing up MESA itself.
Mihai
I applied all the upgrades, and downgraded mesa-libGL and everything
worked. Added the following to /etc/dnf/dnf.conf:
exclude=mesa-libGL
To prevent it from being upgraded until such time as that issue is
resolved.
-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_- 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 Wed, 1 Mar 2017, Mihai Moldovan wrote:
Date: Wed, 1 Mar 2017 10:02:31 +0100 From: Mihai Moldovan <ionic@ionic.de> To: Norman Gaywood <ngaywood@une.edu.au> Cc: x2go-user@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 28.02.2017 11:43 PM, Norman Gaywood wrote:
This might be the update to Mesa in Fedora
https://bugzilla.redhat.com/show_bug.cgi?id=1427174
A lot of programs won't start in my XFCE desktop under x2go. Even xfce4-terminal
The temporary fix is to downgrade mesa:
dnf downgrade mesa-libGL --allowerasing
Very useful information, thanks!
I had the user run glxinfo and on Fedora 25, he got the exact same message.
I wasn't able to reproduce it on Debian Jessie. There, glxinfo could query the GLX version information correctly and also reported working direct rendering via SGI 1.2/MESA 1.4 Gallium software renderer (or the like, I don't remember the specifics, but certainly not an error.)
Initially I thought this might be a problem with nx-libs. If it's really a bug in MESA, that would be good, because is a chance this problem can be fixed by fixing up MESA itself.
Mihai
I applied all the upgrades, and downgraded mesa-libGL and everything
worked. Added the following to /etc/dnf/dnf.conf:
exclude=mesa-libGL To prevent it from being upgraded until such time as that issue is
resolved.
Hm I get this error with this command:
Total 1.1 MB/s | 694 kB 00:00
Running transaction check
Transaction check succeeded.
Running transaction test
The downloaded packages were saved in cache until the next successful transaction.
You can remove cached packages by executing 'dnf clean packages'.
Error: Transaction check error:
file /usr/include/glvnd/GLdispatchABI.h from install of libglvnd-devel-0.2.999-6.git28867bb.fc25.x86_64 conflicts with file from package libglvnd-core-devel-1:0.2.999-10.gitdc16f8c.fc25.x86_64
Very odd.
-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_- 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 Wed, 1 Mar 2017, Robert Kudyba wrote:
Date: Wed, 1 Mar 2017 09:26:03 -0500 From: Robert Kudyba <rkudyba@fordham.edu> To: Robert Dinse <nanook@eskimo.com> Cc: Mihai Moldovan <ionic@ionic.de>, "x2go-user@lists.x2go.org" <x2go-user@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
I applied all the upgrades, and downgraded mesa-libGL and everything
worked. Added the following to /etc/dnf/dnf.conf:
exclude=mesa-libGL To prevent it from being upgraded until such time as that issue is
resolved.
Hm I get this error with this command:
[SKIPPED] mesa-libGL-12.0.3-3.fc25.x86_64.rpm: Already downloaded [SKIPPED] mesa-libglapi-12.0.3-3.fc25.x86_64.rpm: Already downloaded [SKIPPED] mesa-libGL-12.0.3-3.fc25.i686.rpm: Already downloaded [SKIPPED] mesa-libglapi-12.0.3-3.fc25.i686.rpm: Already downloaded [SKIPPED] mesa-libGLES-12.0.3-3.fc25.x86_64.rpm: Already downloaded [SKIPPED] mesa-libGL-devel-12.0.3-3.fc25.x86_64.rpm: Already downloaded [SKIPPED] mesa-libOSMesa-12.0.3-3.fc25.x86_64.rpm: Already downloaded (8/12): libglvnd-devel-0.2.999-6.git28867bb.fc25.x86_64.rpm 437 kB/s | 19 kB 00:00 (9/12): libglvnd-0.2.999-6.git28867bb.fc25.x86_64.rpm 2.7 MB/s | 238 kB 00:00 (10/12): libglvnd-0.2.999-6.git28867bb.fc25.i686.rpm 2.7 MB/s | 241 kB 00:00 (11/12): mesa-libEGL-12.0.3-3.fc25.x86_64.rpm 1.4 MB/s | 96 kB 00:00 (12/12): mesa-libEGL-12.0.3-3.fc25.i686.rpm 2.6 MB/s | 100 kB 00:00
Total 1.1 MB/s | 694 kB 00:00 Running transaction check Transaction check succeeded. Running transaction test The downloaded packages were saved in cache until the next successful transaction. You can remove cached packages by executing 'dnf clean packages'. Error: Transaction check error: file /usr/include/glvnd/GLdispatchABI.h from install of libglvnd-devel-0.2.999-6.git28867bb.fc25.x86_64 conflicts with file from package libglvnd-core-devel-1:0.2.999-10.gitdc16f8c.fc25.x86_64
On Mar 1, 2017, at 9:29 AM, Robert Dinse <nanook@eskimo.com> wrote:
Very odd.
What a mess there are a couple of moving targets:
MATE is working again. Oye.
On Sat, 25 Feb 2017, Robert Kudyba wrote:
connecting to a Fedora 25 server with NIS, choosing the MATE desktop and audio disabled. We made sure to check the security settings as per this older post screenshot <http://lists.x2go.org/pipermail/x2go-dev/attachments/20151013/f02b140a/ attachment-0001.png> and confirmed the .Xauthority permissions problem <http://lists.x2go.org/pipermail/x2go-dev/2015-October/010733.html> does not exist. Here are some debug-enabled logs.
What exactly does crash and when? The client? x2goagent on the server?
In my case it is the x2goagent on the server. I can not find a core
however.
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?
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.)
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.
The general place to look at is probably /etc/security/limits.conf for core dumping permissions and then figure out what ABRT exactly does.
If you want to have ABRT out of the way, echo "core" > /proc/sys/kernel/core_pattern will take care of that.
Mihai
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:
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
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@eskimo.com> To: Mihai Moldovan <ionic@ionic.de> Cc: x2go-user@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@lists.x2go.org http://lists.x2go.org/listinfo/x2go-user