mate-maximus crashed with signal 5 in _XReply()

[ernsteiswuerfel]

Got that on my PowerMac G5 while recreating a document in LibreOffice.

ProblemType: Crash
DistroRelease: Ubuntu 16.10
Package: mate-netbook 1.14.0-1
ProcVersionSignature: Ubuntu 4.4.0-9134.53-powerpc64-smp 4.4.15
Uname: Linux 4.4.0-9134-powerpc64-smp ppc64
ApportVersion: 2.20.3-0ubuntu7
Architecture: powerpc
CurrentDesktop: MATE
Date: Mon Aug 22 02:11:12 2016
ExecutablePath: /usr/bin/mate-maximus
InstallationDate: Installed on 2016-03-26 (148 days ago)
InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Beta powerpc (20160326)
ProcCmdline: mate-maximus
ProcEnviron:
 LANGUAGE=de_AT:de
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=de_AT.UTF-8
 SHELL=/bin/bash
Signal: 5
SourcePackage: mate-netbook
StacktraceTop:
 ?? () from /usr/lib/powerpc-linux-gnu/libX11.so.6
 _XReply () from /usr/lib/powerpc-linux-gnu/libX11.so.6
 XGetWindowProperty () from /usr/lib/powerpc-linux-gnu/libX11.so.6
 ?? ()
 g_cclosure_marshal_VOID__OBJECTv () from /usr/lib/powerpc-linux-gnu/libgobject-2.0.so.0
Title: mate-maximus crashed with signal 5 in _XReply()
UpgradeStatus: Upgraded to yakkety on 2016-07-25 (27 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Apport retracing service (apport)]

StacktraceTop:
 XGetWindowProperty (dpy=0x208eae50, w=62916194, property=377, offset=0, length=5, delete=1, req_type=0, actual_type=0xffd2984c, actual_format=0xffd29850, nitems=0xffd29854, bytesafter=0xffd29858, prop=0xffd29848) at ../../src/GetProp.c:69
 ?? ()
 ?? ()
 ?? ()
 ?? ()

[Vlad Orlov (monsta)]

Well, the stacktrace is incomplete, and CoreDump from PowerPC arch can't be analyzed via gdb as I'm on an amd64 system. Also mate-netbook 1.14.0 is quite old. So, can anyone provide a complete stacktrace and/or CoreDump from amd64 installation of Ubuntu MATE 16.10 or 17.04?

[Brian Murray (brian-murray)]

StacktraceTop:
 XGetWindowProperty (dpy=0x208eae50, w=62916194, property=377, offset=0, length=5, delete=1, req_type=0, actual_type=0xffd2984c, actual_format=0xffd29850, nitems=0xffd29854, bytesafter=0xffd29858, prop=0xffd29848) at ../../src/GetProp.c:69
 ?? ()
 ?? ()
 ?? ()
 ?? ()

[Vlad Orlov (monsta)]

Thanks Brian - but unfortunately, this one is also incomplete... I think there are -dbg or -dbgsym packages missing for mate-netbook and libwnck-3.

[Török Edwin (edwintorok)]

Please see here for a full stack trace on x86-64 (which I obtained by installing apport-retrace and choosing to update the crash file with examine locally): https://bugs.launchpad.net/ubuntu/+source/mate-netbook/+bug/1687503

[I created a new bug instead because apport wouldn't add the stacktrace to this bug]

[Vlad Orlov (monsta)]

Thanks! I was also able to reproduce the bug, and the stacktrace looks similar. I'll try to fix it.

[Vlad Orlov (monsta)]

Ok, this patch should fix it... I'll be testing it for a while, and then it will be included in a new release.

[Ubuntu Foundations Team Bug Bot (crichton)]

The attachment "patch to fix mate-maximus crash" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.]

[Vlad Orlov (monsta)]

Fix is released upstream in mate-netbook 1.18.1 and 1.16.2.

[Launchpad Janitor (janitor)]

This bug was fixed in the package mate-netbook - 1.18.1-0ubuntu1

---------------
mate-netbook (1.18.1-0ubuntu1) artful; urgency=medium

  * New upstream release. (LP: #1615445)

 -- Martin Wimpress <email address hidden> Sun, 14 May 2017 14:28:59 +0100

[Vlad Orlov (monsta)]

Thanks, now we need a backport to 16.10 and 17.04...

[Vlad Orlov (monsta)]

After some updates I'm not able to reproduce it at all in 17.04. So it's not possible to make a proper SRU without reliable steps to reproduce the problem. Please upgrade to 17.10.

[Török Edwin (edwintorok)]

FWIW Ubuntu mate is still quite unstable on 17.10, mate-maximus is not crashing but other bits of the panel are, had to switch back to XFCE:
ERROR: apport (pid 1565) Sat Dec 2 18:05:15 2017: wrote report /var/crash/_usr_lib_x86_64-linux-gnu_brisk-menu_brisk-menu.1000.crash
ERROR: apport (pid 4908) Sat Dec 2 18:15:19 2017: wrote report /var/crash/_usr_bin_mate-tweak.1000.crash
ERROR: apport (pid 5073) Sat Dec 2 18:15:35 2017: wrote report /var/crash/_usr_lib_mate-indicator-applet_mate-indicator-applet-complete.1000.crash
ERROR: apport (pid 6945) Sat Dec 2 18:34:18 2017: wrote report /var/crash/_usr_lib_x86_64-linux-gnu_brisk-menu_brisk-menu.1000.crash

also these, which are blacklisted by apport:
/var/log/kern.log.2.gz:Dec 2 18:06:02 bolt kernel: [ 2725.744814] mate-panel[1532]: segfault at 18 ip 00007f4e055890ef sp 00007fff5a3afc70 error 4 in libgio-2.0.so.0.5400.1[7f4e0547b000+191000]
/var/log/kern.log.2.gz:Dec 2 18:06:39 bolt kernel: [ 2763.109650] mate-panel[1994]: segfault at 18 ip 00007f34305d90ef sp 00007ffc37a23910 error 4 in libgio-2.0.so.0.5400.1[7f34304cb000+191000]
/var/log/kern.log.2.gz:Dec 2 18:15:13 bolt kernel: [ 3277.192188] mate-panel[4750]: segfault at 7f3368a03020 ip 00007f33791d0cdf sp 00007fffe2f556e8 error 4 in libgobject-2.0.so.0.5400.1[7f337919b000+52000]

The crash reports apparently got submitted somewhere to errors.ubuntu.com and I don't have them in my /var/crash anymore.
Do you have access to see the crashes from https://errors.ubuntu.com/?package=mate-applet-brisk-menu&period=month https://errors.ubuntu.com/?package=mate-panel&period=month, or would it be useful to try to reproduce them and file launchpad bugs?

[Vlad Orlov (monsta)]

No, I don't have any access there. I don't really know the purpose of that restricted service. I'm used to good old bug reports with full stacktraces (and even better if they have the steps to reproduce).

[Brian Murray (brian-murray)]

@Vlad - the purpose of the service is that it collects crash reports from stable releases of Ubuntu without requiring user interaction. They don't need to open an account at Launchpad or provide any information about the crash. Full stacktraces should be available at errors.ubuntu.com and developers can request access here.

https://forms.canonical.com/reports/