Bug 1399357 - mate crashes when logging in via x2go
Summary: mate crashes when logging in via x2go
Keywords:
Status: CLOSED DUPLICATE of bug 1427174
Alias: None
Product: Fedora
Classification: Fedora
Component: mesa
Version: 25
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Adam Jackson
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-11-28 20:57 UTC by Andy Wang
Modified: 2017-05-16 20:37 UTC (History)
12 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-03-13 14:57:51 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
dnf history info (24.67 KB, text/plain)
2017-03-05 16:27 UTC, Schefi
no flags Details
X2Go core with MATE (834.67 KB, application/octet-stream)
2017-05-16 20:37 UTC, RobbieTheK
no flags Details

Description Andy Wang 2016-11-28 20:57:45 UTC
Description of problem:
When trying to log into a mate-session, mate session doesn't start properly.

Following messages show up in dmesg:
   80.568604] mate-settings-d[4973]: segfault at 8 ip 00007fa76bef50a8 sp 00007fffc8daa330 error 4 in libmate-desktop-2.so.17.1.4[7fa76bed8000+46000]

repeated numerous times.

versions:

mate-settings-daemon-1.16.0-1.fc25.x86_64
x2goserver-4.0.1.19-11.fc25.x86_64

I'm not sure what additional information to gather.  This was working fine until upgrading to f25.

Comment 1 Orion Poplawski 2016-11-28 21:38:27 UTC
Re-assigning to mate-desktop since the crash is there.  We'll need to see a full backtrace from the crash.  Either abrtd or systemd-coredump should have collected a coredump from which you can extract the backtrace with gdb.

Comment 2 Andy Wang 2016-11-28 21:44:11 UTC
It's not just happening with mate-desktop.  I just tried with lxde and it's desktop filemanager also crashes.

[ 2956.455839] traps: pcmanfm[17832] trap int3 ip:7f30680bba21 sp:7ffc0033dfd0 error:0 in libglib-2.0.so.0.5000.1[7f306806c000+110000]

Comment 3 Andy Wang 2016-11-28 21:46:50 UTC
backtrace for mate-session-daemon:
https://retrace.fedoraproject.org/faf/reports/1388904/

backtrace for pcmanfm
https://retrace.fedoraproject.org/faf/reports/1394912/

Comment 4 Wolfgang Ulbrich 2016-11-28 21:52:21 UTC
(In reply to Orion Poplawski from comment #1)
> Re-assigning to mate-desktop since the crash is there.  We'll need to see a
> full backtrace from the crash.  Either abrtd or systemd-coredump should have
> collected a coredump from which you can extract the backtrace with gdb.

Is there a reson why you re-assigning it to the wrong package?
I don't see libmate-desktop in log.
...complete useless action.

Comment 5 Wolfgang Ulbrich 2016-11-28 21:53:48 UTC
PS: i don't use x2go, don't expect that i can reproduce it.

Comment 6 Andy Wang 2016-11-28 23:13:39 UTC
both the pcmanfm backtrace and the mate-settings-daemon backtrace seem to point to some issue trying to get the screen size/data.

So it does look like the two are somewhat related.

Comment 7 Andy Wang 2016-11-29 03:36:50 UTC
Installed a fresh fedora 25 system in a libvirt vm.

This is my user .bash_history:
    1  sudo systemctl enable sshd
    2  sudo systemctl start sshd
    3  sudo dnf -y update
    4  sudo dnf install x2goserver @"MATE Desktop"

Attempted to create a MATE x2go session remotely and the problem was immediately reproducible.

made sure to log out of the console X session to ensure that the dbus session collision doesn't occur.

Comment 8 Orion Poplawski 2016-11-29 05:01:30 UTC
Yeah, I see this too.  Lots of errors in .xsession-x2go-errors too:

mate-session[7931]: WARNING: GSIdleMonitor: IDLETIME counter not found
mate-session[7931]: GLib-GObject-CRITICAL: object GSIdleMonitor 0x55a988e62920 finalized while still in-construction
mate-session[7931]: GLib-GObject-CRITICAL: Custom constructor for class GSIdleMonitor returned NULL (which is invalid). Please use GInitable instead.
mate-session[7931]: GLib-GObject-CRITICAL: object GsmAutostartApp 0x7fd010018400 finalized while still in-construction
mate-session[7931]: GLib-GObject-CRITICAL: Custom constructor for class GsmAutostartApp returned NULL (which is invalid). Please use GInitable instead.
mate-session[7931]: GLib-GObject-CRITICAL: object GsmAutostartApp 0x7fd0100184d0 finalized while still in-construction
mate-session[7931]: GLib-GObject-CRITICAL: Custom constructor for class GsmAutostartApp returned NULL (which is invalid). Please use GInitable instead.
mate-session[7931]: GLib-GObject-CRITICAL: object GsmAutostartApp 0x55a988e91f20 finalized while still in-construction
mate-session[7931]: GLib-GObject-CRITICAL: Custom constructor for class GsmAutostartApp returned NULL (which is invalid). Please use GInitable instead.
** (mate-settings-daemon:8132): WARNING **: Unable to start xrandr manager: RANDR extension is too old (must be at least 1.3)
(mate-panel:8136): Gtk-WARNING **: Allocating size to GtkAlignment 0x55804e0ba660 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate?
(mate-panel:8136): GLib-GObject-CRITICAL **: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
(mate-settings-daemon:8132): GdkPixbuf-CRITICAL **: gdk_pixbuf_new: assertion 'width > 0' failed
(mate-settings-daemon:8132): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_width: assertion 'GDK_IS_PIXBUF (pixbuf)' failed
(mate-settings-daemon:8132): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_height: assertion 'GDK_IS_PIXBUF (pixbuf)' failed
(mate-settings-daemon:8132): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_rowstride: assertion 'GDK_IS_PIXBUF (pixbuf)' failed

Looks like the RANDR requirement might be the trigger here.

Comment 9 Orion Poplawski 2016-11-29 05:06:37 UTC
looks like draw_each_monitor->gdk_screen_get_monitor_geometry returns a rect with zero sizes and we go downhill from there.

Comment 10 Andy Wang 2016-11-29 17:39:37 UTC
Not sure if this is related, but with xfce, the majority of applications don't display their drop down menus.  The menu bar (File Edit Etc...) are there but clicking on them doesn't display anything although if you know where the menu entry is you can blindly keyboard navigate (down arrow a couple of times - enter for example will execute the entry on the menu even htough you can't see it).

At this point, I haven't been able to get any of the usual lighterweight DM environments (lxde, xfce, mate) to work in an x2go session properly on f25.

Comment 11 Andy Wang 2016-12-01 20:15:24 UTC
* Sun Nov 20 2016 Orion Poplawski <orion.com> - 4.0.1.20-1
- Update to 4.0.1.20
- Drop patches applied upstream

Is that known to fix this problem?  Because it appears to :)

Comment 12 Orion Poplawski 2016-12-01 21:40:08 UTC
No, I was not expecting that to have any effect, but it does seem to have fixed things for me too.

Comment 13 Dylan Graham 2017-03-05 03:40:00 UTC
I have a fresh (and updated) f25 install which has this problem.
x2goserver is already at 4.0.1.20-1.

mate-session[6020]: segfault at 0 ip 00007f41243df35f sp 00007ffe9832d788 error 4 in libc-2.24.so[7f4124348000+1bd000]

Comment 14 Schefi 2017-03-05 15:20:25 UTC
Same as Dylan. I also have a fresh install with the same error. Local MATE session works, but get segfault over x2go. 
Also tested on one of my computers, which was offline for the past 1-2 months: mate over x2go worked. But 10 minutes ago I did a dnf upgrade for other reasons: now it segfaults too.

Comment 15 Wolfgang Ulbrich 2017-03-05 16:17:15 UTC
(In reply to Schefi from comment #14)
> Same as Dylan. I also have a fresh install with the same error. Local MATE
> session works, but get segfault over x2go. 
> Also tested on one of my computers, which was offline for the past 1-2
> months: mate over x2go worked. But 10 minutes ago I did a dnf upgrade for
> other reasons: now it segfaults too.
dnf history
dnf history info <id>

Comment 16 Schefi 2017-03-05 16:27:24 UTC
Created attachment 1260076 [details]
dnf history info

Comment 17 Wolfgang Ulbrich 2017-03-05 19:17:11 UTC
Try downgrading all mentioned mate packages, or better
dnf history undo <id>
after that update all mentioned packages stepp by step, to see what package causes the issue.

Comment 18 Schefi 2017-03-05 20:12:50 UTC
I found out that downgrading mesa-libGL and mesa-libglapi restrores functioning mate desktop over x2go.
It is only possible to downgrade them both together due to dependencies. The downgrade also requires the removal of libglvnd-glx package. (You can see from dnf history, that is was not installed on my system with mesa-libGL 13.0.3-5.fc25.x86_64, but was installed with the upgrade to 13.0.4-1.fc25.x86_64, so it became a dependency with version change)
Anyways, I checked back and forth: re-upgrading to latest version breaks it again. So it should be definitely something wrong with latest libgl and/or libglapi.

Comment 19 Wolfgang Ulbrich 2017-03-05 20:30:46 UTC
(In reply to Schefi from comment #18)
> I found out that downgrading mesa-libGL and mesa-libglapi restrores
> functioning mate desktop over x2go.
> It is only possible to downgrade them both together due to dependencies. The
> downgrade also requires the removal of libglvnd-glx package. (You can see
> from dnf history, that is was not installed on my system with mesa-libGL
> 13.0.3-5.fc25.x86_64, but was installed with the upgrade to
> 13.0.4-1.fc25.x86_64, so it became a dependency with version change)
> Anyways, I checked back and forth: re-upgrading to latest version breaks it
> again. So it should be definitely something wrong with latest libgl and/or
> libglapi.

Thank for investigation to find out the culprit.
I don't want to say that the problem is causeed by mesa, maybe mase-settings-daemon or x2go needs an update.
But i will reassign this mesa to see what his maintainer says.
Maybe x2go maintainer have an idea yet?

Comment 20 Norman Gaywood 2017-03-06 01:43:42 UTC
This is probably the same as bug #1427174 

The solution for the xfce4 apps (and others) seg faulting was to:

dnf downgrade mesa-libGL --allowerasing

Comment 21 Orion Poplawski 2017-03-13 14:57:51 UTC

*** This bug has been marked as a duplicate of bug 1427174 ***

Comment 23 RobbieTheK 2017-05-16 20:37:09 UTC
Created attachment 1279414 [details]
X2Go core with MATE

Any reason why this is still happening?

rpm -q x2goserver
x2goserver-4.0.1.20-1.fc25.x86_64

rpm -q mesa-libEGL
mesa-libEGL-17.0.5-2.fc25.x86_64
mesa-libEGL-17.0.5-2.fc25.i686


May 16 13:53:56 ourserver kernel: mate-session[11263]: segfault at 0 ip 00007f52cc5f1754 sp 00007ffc95dcc400 error 4 in libgdk-3.so.0.2200.12[7f52cc5bf000+eb000]
May 16 13:53:56 ourserver systemd: Created slice system-systemd\x2dcoredump.slice.
May 16 13:53:56 ourserver systemd: Started Process Core Dump (PID 11359/UID 0).
May 16 13:53:57 ourserver systemd-coredump: Process 11263 (mate-session) of user 1201 dumped core.#012#012Stack trace of thread 11263:#012#0  0x00007f52cc5f1754 gdk_error_trap_push (libgdk-3.so.0)#012#1  0x0000555d99833492 msm_gnome_start (mate-session)#012#2  0x0000555d99822b87 main (mate-session)#012#3  0x00007f52ca6cc401 __libc_start_main (libc.so.6)#012#4  0x0000555d998234ca _start (mate-session)#012#012Stack trace of thread 11349:#012#0  0x00007f52ca7a801d poll (libc.so.6)#012#1  0x00007f52caabc166 g_main_context_iterate.isra.24 (libglib-2.0.so.0)#012#2  0x00007f52caabc27c g_main_context_iteration (libglib-2.0.so.0)#012#3  0x00007f52c2249fad dconf_gdbus_worker_thread (libdconfsettings.so)#012#4  0x00007f52caae3b93 g_thread_proxy (libglib-2.0.so.0)#012#5  0x00007f52c8bb76ca start_thread (libpthread.so.0)#012#6  0x00007f52ca7b3f7f __clone (libc.so.6)#012#012Stack trace of thread 11347:#012#0  0x00007f52ca7a801d poll (libc.so.6)#012#1  0x00007f52caabc166 g_main_context_iterate.isra.24 (libglib-2.0.so.0)#012#2  0x00007f52caabc27c g_main_context_iteration (libglib-2.0.so.0)#012#3  0x00007f52caabc2c1 glib_worker_main (libglib-2.0.so.0)#012#4  0x00007f52caae3b93 g_thread_proxy (libglib-2.0.so.0)#012#5  0x00007f52c8bb76ca start_thread (libpthread.so.0)#012#6  0x00007f52ca7b3f7f __clone (libc.so.6)#012#012Stack trace of thread 11348:#012#0  0x00007f52ca7a801d poll (libc.so.6)#012#1  0x00007f52caabc166 g_main_context_iterate.isra.24 (libglib-2.0.so.0)#012#2  0x00007f52caabc4f2 g_main_loop_run (libglib-2.0.so.0)#012#3  0x00007f52cb51da76 gdbus_shared_thread_func (libgio-2.0.so.0)#012#4  0x00007f52caae3b93 g_thread_proxy (libglib-2.0.so.0)#012#5  0x00007f52c8bb76ca start_thread (libpthread.so.0)#012#6  0x00007f52ca7b3f7f __clone (libc.so.6)


Note You need to log in before you can comment on or make changes to this bug.