marco crashed with signal 5 in _XReply()

[Phillip Dunstall]

When I did an Update

ProblemType: Crash
DistroRelease: Ubuntu 22.04
Package: marco 1.26.0-0ubuntu1
ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
Uname: Linux 5.13.0-19-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu74
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: MATE
Date: Fri Dec 10 10:38:56 2021
ExecutablePath: /usr/bin/marco
ProcCmdline: marco
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 5
SourcePackage: marco
StacktraceTop:
 ?? () from /lib/x86_64-linux-gnu/libX11.so.6
 ?? () from /lib/x86_64-linux-gnu/libX11.so.6
 _XReply () from /lib/x86_64-linux-gnu/libX11.so.6
 XSync () from /lib/x86_64-linux-gnu/libX11.so.6
 ?? () from /lib/x86_64-linux-gnu/libgdk-3.so.0
Title: marco crashed with signal 5 in _XReply()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
separator:

[Apport retracing service (apport)]

StacktraceTop:
 XSync (dpy=0x5573b8647250, discard=discard@entry=0) at ../../src/Sync.c:44
 gdk_x11_display_error_trap_pop_internal (display=0x5573b865d0e0, need_code=<optimized out>) at x11/../../../../../gdk/x11/gdkdisplay-x11.c:2886
 meta_screen_free (screen=0x5573b87423f0, timestamp=0) at core/screen.c:678
 meta_display_close (timestamp=0, display=0x5573b87fd400) at core/display.c:910
 meta_display_close (display=0x5573b87fd400, timestamp=0) at core/display.c:875

[Apport retracing service (apport)]

StacktraceSource:
 #0 0x00007f8fca3e6d5f in g_test_expect_message (log_domain=0x7 <error: Cannot access memory at address 0x7>, log_level=0, pattern=0x6 <error: Cannot access memory at address 0x6>) at ../../../glib/gmessages.c:3019
   [Error: gmessages.c was not found in source tree]
 #1 0x00007f8fca3e2a53 in g_log_structured_standard (log_domain=0x7 <error: Cannot access memory at address 0x7>, log_level=0, file=0x7f8fca2d8cc0 <main_arena+96> "\360\223\351\270sU", line=0x3f <error: Cannot access memory at address 0x3f>, func=0x5573b8a742c0 "\300\214-\312\217\177", message_format=0x7fff57b58e00 "eceived an X Window System error.\nThis probably reflects a bug in the program.\nThe error was 'BadRegion (invalid Region parameter)'.\n (Details: serial 570746 error_code 140 request_code 138 (XFIXES) "...) at ../../../glib/gmessages.c:1992
   [Error: gmessages.c was not found in source tree]
 #2 0x0000000000000000 in ?? ()
StacktraceTop:
 g_test_expect_message (log_domain=0x7 <error: Cannot access memory at address 0x7>, log_level=0, pattern=0x6 <error: Cannot access memory at address 0x6>) at ../../../glib/gmessages.c:3019
 g_log_structured_standard (log_domain=0x7 <error: Cannot access memory at address 0x7>, log_level=0, file=0x7f8fca2d8cc0 <main_arena+96> "\360\223\351\270sU", line=0x3f <error: Cannot access memory at address 0x3f>, func=0x5573b8a742c0 "\300\214-\312\217\177", message_format=0x7fff57b58e00 "eceived an X Window System error.\nThis probably reflects a bug in the program.\nThe error was 'BadRegion (invalid Region parameter)'.\n (Details: serial 570746 error_code 140 request_code 138 (XFIXES) "...) at ../../../glib/gmessages.c:1992
 ?? ()

[Marc Deslauriers (mdeslaur)]

Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find.

[Launchpad Janitor (janitor)]

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

[Kenneth Lavrsen (kennethlavrsen)]

I am seeting this exact same bug each time I log into Ubuntu Mate 22.04 and open a window. Each and every time. For a year. I think we are 1000s of users that would appreciate if this got some love.

[Konstantin (elink-7)]

The situation when "scary" message appears "every time" is abnormal for operating system and discredits the otherwise other good parts of this OS. I am (and may be others) thinking to go to the OS which does not make such sense of non-reliability. Something has to be done with this. Either not to show this message or make it less "crashy".

This goes on possibly for years.

This sort of message shows either lack of support for the OS or that something is not well designed.

"Marco bug" message appears on 2 different brand computers where Mate 22 is installed nearly every login and every day possibly during few months. Sending crash reports and update does not seem to help. Noone takes a priority for these crash reports.

Log of this message is hard to understand and solution is not found.

Thank you.