Internal error "usr/bin/marco"

jaybo · 29 March 2021 19:01

Am I the only one getting several internal errors related to usr/bin/macro?

I get several on two different PCs. One was a fresh install, the other an upgrade from 18.04.

I submit them all to the developers.

saivinob · 30 March 2021 12:51

No issues for me on 20.04 and 21.04 machines. I'm on generic Intel PC with integrated graphics though.

Bernie · 31 March 2021 00:23

occasionally I think, but they don't seem to have any effect so I haven't worried about them and on AMD with integrated graphics

gordon · 31 March 2021 00:50

BTW, it's /usr/bin/marco, not /usr/bin/macro... unless you're talking about something else.

Bernie · 31 March 2021 20:46

yes I assumed that's what we were talking about .

ricmarques · 2 April 2021 18:06

Hi @jaybo ,

For what it's worth, today (2nd April 2021) I had a "marco" related crash in a laptop that I had upgraded, a few weeks ago, from Ubuntu MATE 18.04.5 LTS to Ubuntu MATE 20.04.2 LTS

The crash file in the "/var/crash" directory (folder) has the following information:

ProblemType: Crash
Architecture: amd64
CrashCounter: 1
CurrentDesktop: MATE
Date: Fri Apr  2 15:19:23 2021
DistroRelease: Ubuntu 20.04
ExecutablePath: /usr/bin/marco
(...)
Package: marco 1.24.0-1ubuntu1
PackageArchitecture: amd64
(...)
Title: marco crashed with SIGSEGV in cairo_region_num_rectangles()
UnreportableReason:
 You have some obsolete package versions installed. Please upgrade the following packages and check if the problem still occurs:

 libsystemd0, libudev1, ubuntu-keyring
UpgradeStatus: Upgraded to focal on 2021-03-13 (19 days ago)
XsessionErrors:
 mate-session[1621]: WARNING: Unable to find provider '' of required component 'dock'
 (process:2081): indicator-sound-WARNING **: 15:03:06.991: volume-control-pulse.vala:744: Unable to connect to dbus server at 'unix:path=/run/user/1000/pulse/dbus-socket': Could not connect: No such file or directory
 (caja:1893): Gtk-WARNING **: 15:03:06.995: Failed to register client: GDBus.Error:org.gnome.SessionManager.AlreadyRegistered: Unable to register client
 (process:2081): indicator-sound-WARNING **: 15:03:07.002: media-player-list-mpris.vala:66: unable to find application 'io.github.GnomeMpv.desktop'
 (nm-applet:1982): Gdk-CRITICAL **: 15:03:07.169: gdk_window_thaw_toplevel_updates: assertion 'window->update_and_descendants_freeze_count > 0' failed
 (process:2120): Indicator-Datetime-WARNING **: 15:03:14.563: Unrecognized TZID: 'Etc/Utc'

Because I saw, in the above crash report, that I had some obsolete package versions installed (namely libsystemd0, libudev1 and ubuntu-keyring), I ran the commands "sudo apt autoremove", followed by "sudo apt update", "sudo apt list --upgradable" (which listed 10 packages that could be upgraded) and then followed by "sudo apt upgrade". That updated 10 packages but none of them was related to "marco". Since then I rebooted the machine. Let's see if the crash happens again.

I did find the following related bug reported by @Wimpy himself, on the 15th February 2020:

Bug #1863392 “marco crashed with SIGSEGV in INT marco crashed with SIGSEGV in INT_cairo_region_num_rectangles()” : Bugs : marco package : Ubuntu

... which includes a comment (dated 24th March 2020) that says that "This bug was fixed in the package "marco - 1.24.0-1ubuntu1" and includes the corresponding patch:

... HOWEVER, there's a much more recent comment (dated 15th March 2021), by Jared Punzel - Comment #8 : Bug #1863392 : Bugs : marco package : Ubuntu - that says that:

(...) This appears to have not been fixed in 1.24.0-1ubuntu1 on the latest 20.04. It happens at occasional times when I close a window. There are some similar recent reports on the github page:
marco SEGV · Issue #617 · mate-desktop/marco · GitHub
Firefox closing triggers marco crash · Issue #661 · mate-desktop/marco · GitHub "

ricmarques · 9 May 2021 21:44

This "marco" crash ("Sorry, Ubuntu 20.04 has experienced an internal error.") - Title: marco crashed with SIGSEGV in cairo_region_num_rectangles() - using the 1.24.0-1 version of "marco" (Package: marco 1.24.0-1ubuntu1) happened again to me today (9th May 2021) in a machine that I upgraded from Ubuntu MATE 18.04.5 to Ubuntu MATE 20.04.2 ("Focal Fossa") about 2 months ago.

Here's the relevant info:

Screenshot:

Crash file :

The crash file "_usr_bin_marco.1000.crash" in the "/var/crash" directory (folder) has the following information:

ProblemType: Crash
Architecture: amd64
CrashCounter: 1
CurrentDesktop: MATE
Date: Sun May  9 22:18:51 2021
DistroRelease: Ubuntu 20.04
ExecutablePath: /usr/bin/marco
(...)
Package: marco 1.24.0-1ubuntu1
PackageArchitecture: amd64
(...)
SegvAnalysis:
 Segfault happened at: 0x7ff2bde6f9d4 <cairo_region_num_rectangles+4>:  mov    0x4(%rdi),%eax
 PC (0x7ff2bde6f9d4) ok
 source "0x4(%rdi)" (0x000000f5) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
SourcePackage: marco
Stacktrace:
 #0  0x00007ff2bde6f9d4 in cairo_region_num_rectangles () from /usr/lib/x86_64-linux-gnu/libcairo.so.2
 No symbol table info available.
 #1  0x00007ff2beb3b41e in ?? () from /usr/lib/x86_64-linux-gnu/libmarco-private.so.2
 No symbol table info available.
 #2  0x00007ff2beb3d944 in ?? () from /usr/lib/x86_64-linux-gnu/libmarco-private.so.2
 No symbol table info available.
 #3  0x00007ff2beb3eb1e in ?? () from /usr/lib/x86_64-linux-gnu/libmarco-private.so.2
 No symbol table info available.
 #4  0x00007ff2beb3ec28 in ?? () from /usr/lib/x86_64-linux-gnu/libmarco-private.so.2
 No symbol table info available.
 #5  0x00007ff2bec1104e in g_main_context_dispatch () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
 No symbol table info available.
 #6  0x00007ff2bec11400 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
 No symbol table info available.
 #7  0x00007ff2bec116f3 in g_main_loop_run () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
 No symbol table info available.
 #8  0x00005648099eb233 in main ()
 No symbol table info available.
StacktraceAddressSignature: /usr/bin/marco:11:/usr/lib/x86_64-linux-gnu/libcairo.so.2.11600.0+539d4:/usr/lib/x86_64-linux-gnu/libmarco-private.so.2.0.0+a41e:/usr/lib/x86_64-linux-gnu/libmarco-private.so.2.0.0+c944:/usr/lib/x86_64-linux-gnu/libmarco-private.so.2.0.0+db1e:/usr/lib/x86_64-linux-gnu/libmarco-private.so.2.0.0+dc28:/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.6400.6+3604e:/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.6400.6+36400:/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.6400.6+366f3:/usr/bin/marco+1233
(...)
Title: marco crashed with SIGSEGV in cairo_region_num_rectangles()
UpgradeStatus: Upgraded to focal on 2021-03-13 (56 days ago)
XsessionErrors:
 mate-session[1599]: WARNING: Unable to find provider '' of required component 'dock'
 (process:2047): indicator-sound-WARNING **: 15:18:20.262: volume-control-pulse.vala:744: Unable to connect to dbus server at 'unix:path=/run/user/1000/pulse/dbus-socket': Could not connect: No such file or directory
 (process:2047): indicator-sound-WARNING **: 15:18:20.272: media-player-list-mpris.vala:66: unable to find application 'io.github.GnomeMpv.desktop'
 (caja:1873): Gtk-WARNING **: 15:18:20.274: Failed to register client: GDBus.Error:org.gnome.SessionManager.AlreadyRegistered: Unable to register client
 (process:2047): indicator-sound-CRITICAL **: 15:37:39.453: media_player_list_mpris_insert: assertion 'desktop_id != NULL' failed
 (mate-power-manager:1925): GLib-CRITICAL **: 17:23:17.519: Source ID 85 was not found when attempting to remove it
 (mate-volume-control:12350): GLib-GIO-WARNING **: 20:24:11.875: Your application did not unregister from D-Bus before destruction. Consider using g_application_run().
(...)

theleftover · 15 August 2021 01:31

I am getting these too. Raspberry Pi ARM64. The crash file has different information than the one's posted here. I will be please to post them here if anyone can make use of them.

Best,

gordon · 16 August 2021 01:40

I can make use of the crash logs. Maybe I'll find something pertinent.

Please show me the crash logs.

theleftover · 16 August 2021 15:10

That is a kind offer. Here you go.

It does not feel like we are pushing any boundaries with Mate. It's Ubuntu ARM64 on a Pi. Then we load Mate Core using TaskSel. The crashes just come when logging in or switching IDs.

Obviously the unabridged crash file is available if you want the core dump. Ask, and you will receive!!

-rw-r----- 1 service whoopsie 2705871 Aug 15 00:50 _usr_bin_marco.1000.crash         <-- this one
-rw-r----- 1 root    whoopsie 2554675 Aug 16 14:12 _usr_lib_xorg_Xorg.0.crash
  
  
ProblemType: Crash
Architecture: arm64
CurrentDesktop: MATE
Date: Sun Aug 15 00:50:45 2021
DistroRelease: Ubuntu 20.04
ExecutablePath: /usr/bin/marco
ExecutableTimestamp: 1585005498
ProcCmdline: marco
ProcCwd: /home/service
ProcEnviron:
 LANGUAGE=en
 PATH=(custom, user)
 XDG_RUNTIME_DIR=<set>
 LANG=C.UTF-8
 SHELL=/bin/bash
ProcMaps:
 aaaae6f57000-aaaae6f5b000 r-xp 00000000 b3:02 83152                      /usr/bin/marco
 aaaae6f6a000-aaaae6f6b000 r--p 00003000 b3:02 83152                      /usr/bin/marco
 aaaae6f6b000-aaaae6f6c000 rw-p 00004000 b3:02 83152                      /usr/bin/marco
 aaaafadca000-aaaafb419000 rw-p 00000000 00:00 0                          [heap]
 ffff88000000-ffff8c000000 rw-s 00000000 00:01 120869                     /memfd:pulseaudio (deleted)
 ffff8c000000-ffff90000000 rw-s 00000000 00:01 96997                      /memfd:pulseaudio (deleted)
 ffff90000000-ffff94000000 rw-s 00000000 00:01 119329                     /memfd:pulseaudio (deleted)
 ffff94000000-ffff94021000 rw-p 00000000 00:00 0 
 ffff94021000-ffff98000000 ---p 00000000 00:00 0 
 ffff98000000-ffff98021000 rw-p 00000000 00:00 0 
 ffff98021000-ffff9c000000 ---p 00000000 00:00 0 
 ffff9c000000-ffffa0000000 rw-s 00000000 00:01 119329                     /memfd:pulseaudio (deleted)
 ffffa0000000-ffffa0021000 rw-p 00000000 00:00 0 
 ffffa0021000-ffffa4000000 ---p 00000000 00:00 0 
 ffffa4000000-ffffa4021000 rw-p 00000000 00:00 0 
 ffffa4021000-ffffa8000000 ---p 00000000 00:00 0 
 ffffa8000000-ffffa8021000 rw-p 00000000 00:00 0 
 ffffa8021000-ffffac000000 ---p 00000000 00:00 0 
 ffffac2cf000-ffffac34f000 rw-s 00000000 00:01 131108                     /SYSV00000000 (deleted)
 ffffac34f000-ffffac3a3000 r--p 00000000 b3:02 165298                     /usr/share/fonts/truetype/ubuntu/Ubuntu-M.ttf
 ffffac3a3000-ffffac3f7000 r--p 00000000 b3:02 165298                     /usr/share/fonts/truetype/ubuntu/Ubuntu-M.ttf    

                              < . . . and many more fonts . . . >    

 ffffac49b000-ffffac49f000 r--s 00000000 b3:02 158024                     /var/cache/fontconfig/c619d46c-c647-49ce-b13b-2a6f4bd95a8e-le64.cache-7
 ffffac49f000-ffffac4a0000 ---p 00000000 00:00 0 
 ffffac4a0000-ffffacca0000 rw-p 00000000 00:00 0 
 ffffacca0000-ffffacd28000 r-xp 00000000 b3:02 15127                      /usr/lib/aarch64-linux-gnu/libvorbisenc.so.2.0.11
 ffffacd28000-ffffacd38000 ---p 00088000 b3:02 15127                      /usr/lib/aarch64-linux-gnu/libvorbisenc.so.2.0.11
 ffffacd38000-ffffacd4f000 r--p 00088000 b3:02 15127                      /usr/lib/aarch64-linux-gnu/libvorbisenc.so.2.0.11
 ffffacd4f000-ffffacd50000 rw-p 0009f000 b3:02 15127                      /usr/lib/aarch64-linux-gnu/libvorbisenc.so.2.0.11
 ffffacd50000-ffffacd81000 r-xp 00000000 b3:02 17128                      /usr/lib/aarch64-linux-gnu/libFLAC.so.8.3.0
 ffffacd81000-ffffacd91000 ---p 00031000 b3:02 17128                      /usr/lib/aarch64-linux-gnu/libFLAC.so.8.3.0
 ffffacd91000-ffffacd92000 r--p 00031000 b3:02 17128                      /usr/lib/aarch64-linux-gnu/libFLAC.so.8.3.0
 ffffacd92000-ffffacd93000 rw-p 00032000 b3:02 17128                      /usr/lib/aarch64-linux-gnu/libFLAC.so.8.3.0
 ffffacd93000-ffffacda9000 r-xp 00000000 b3:02 3146                       /usr/lib/aarch64-linux-gnu/libnsl-2.31.so
 ffffacda9000-ffffacdb8000 ---p 00016000 b3:02 3146                       /usr/lib/aarch64-linux-gnu/libnsl-2.31.so
 ffffacdb8000-ffffacdb9000 r--p 00015000 b3:02 3146                       /usr/lib/aarch64-linux-gnu/libnsl-2.31.so
 ffffacdb9000-ffffacdba000 rw-p 00016000 b3:02 3146                       /usr/lib/aarch64-linux-gnu/libnsl-2.31.so
 ffffacdba000-ffffacdbc000 rw-p 00000000 00:00 0 
 ffffacdbc000-ffffacdcd000 r-xp 00000000 b3:02 2842                       /usr/lib/aarch64-linux-gnu/libapparmor.so.1.6.1
 ffffacdcd000-ffffacddc000 ---p 00011000 b3:02 2842                       /usr/lib/aarch64-linux-gnu/libapparmor.so.1.6.1
 ffffacddc000-ffffacddd000 r--p 00010000 b3:02 2842                       /usr/lib/aarch64-linux-gnu/libapparmor.so.1.6.1
 ffffacddd000-ffffacdde000 rw-p 00011000 b3:02 2842                       /usr/lib/aarch64-linux-gnu/libapparmor.so.1.6.1
  
                              < . . . and much much more . . . >
  
 ffffb1401000-ffffb1402000 rw-p 0001b000 b3:02 3222                       /usr/lib/aarch64-linux-gnu/libpthread-2.31.so
 ffffb1402000-ffffb1406000 rw-p 00000000 00:00 0 
 ffffb1406000-ffffb1467000 r-xp 00000000 b3:02 3189                       /usr/lib/aarch64-linux-gnu/libpcre.so.3.13.3
 ffffb1467000-ffffb1476000 ---p 00061000 b3:02 3189                       /usr/lib/aarch64-linux-gnu/libpcre.so.3.13.3
 ffffb1476000-ffffb1477000 r--p 00060000 b3:02 3189                       /usr/lib/aarch64-linux-gnu/libpcre.so.3.13.3
 ffffb1477000-ffffb1478000 rw-p 00061000 b3:02 3189                       /usr/lib/aarch64-linux-gnu/libpcre.so.3.13.3
 ffffb1478000-ffffb15d2000 r-xp 00000000 b3:02 2879                       /usr/lib/aarch64-linux-gnu/libc-2.31.so
 ffffb15d2000-ffffb15e2000 ---p 0015a000 b3:02 2879                       /usr/lib/aarch64-linux-gnu/libc-2.31.so
 ffffb15e2000-ffffb15e5000 r--p 0015a000 b3:02 2879                       /usr/lib/aarch64-linux-gnu/libc-2.31.so
 ffffb15e5000-ffffb15e8000 rw-p 0015d000 b3:02 2879                       /usr/lib/aarch64-linux-gnu/libc-2.31.so
 ffffb15e8000-ffffb15eb000 rw-p 00000000 00:00 0 
 ffffb15eb000-ffffb1685000 r-xp 00000000 b3:02 81629                      /usr/lib/aarch64-linux-gnu/libmarco-private.so.2.0.0
 ffffb1685000-ffffb1695000 ---p 0009a000 b3:02 81629                      /usr/lib/aarch64-linux-gnu/libmarco-private.so.2.0.0
 ffffb1695000-ffffb1698000 r--p 0009a000 b3:02 81629                      /usr/lib/aarch64-linux-gnu/libmarco-private.so.2.0.0
 ffffb1698000-ffffb169a000 rw-p 0009d000 b3:02 81629                      /usr/lib/aarch64-linux-gnu/libmarco-private.so.2.0.0
 ffffb169a000-ffffb17c1000 r-xp 00000000 b3:02 21536                      /usr/lib/aarch64-linux-gnu/libglib-2.0.so.0.6400.6
 ffffb17c1000-ffffb17d1000 ---p 00127000 b3:02 21536                      /usr/lib/aarch64-linux-gnu/libglib-2.0.so.0.6400.6
 ffffb17d1000-ffffb17d2000 r--p 00127000 b3:02 21536                      /usr/lib/aarch64-linux-gnu/libglib-2.0.so.0.6400.6
 ffffb17d2000-ffffb17d3000 rw-p 00128000 b3:02 21536                      /usr/lib/aarch64-linux-gnu/libglib-2.0.so.0.6400.6
 ffffb17d3000-ffffb17d4000 rw-p 00000000 00:00 0 
 ffffb17d4000-ffffb17d5000 r--s 00000000 00:2d 37                         /run/user/1000/dconf/user
 ffffb17d5000-ffffb17d6000 r--p 00000000 b3:02 8010                       /usr/lib/locale/C.UTF-8/LC_NUMERIC
 ffffb17d6000-ffffb17d7000 r--p 00000000 b3:02 8013                       /usr/lib/locale/C.UTF-8/LC_TIME
 ffffb17d7000-ffffb17d8000 r--p 00000000 b3:02 8008                       /usr/lib/locale/C.UTF-8/LC_MONETARY
 ffffb17d8000-ffffb17d9000 r--p 00000000 b3:02 8007                       /usr/lib/locale/C.UTF-8/LC_MESSAGES/SYS_LC_MESSAGES
 ffffb17d9000-ffffb17da000 r--p 00000000 b3:02 8011                       /usr/lib/locale/C.UTF-8/LC_PAPER
 ffffb17da000-ffffb17db000 r--p 00000000 b3:02 8009                       /usr/lib/locale/C.UTF-8/LC_NAME
 ffffb17db000-ffffb17dc000 r--p 00000000 b3:02 8001                       /usr/lib/locale/C.UTF-8/LC_ADDRESS
 ffffb17dc000-ffffb17dd000 r--p 00000000 b3:02 8012                       /usr/lib/locale/C.UTF-8/LC_TELEPHONE
 ffffb17dd000-ffffb17de000 r--p 00000000 b3:02 8005                       /usr/lib/locale/C.UTF-8/LC_MEASUREMENT
 ffffb17de000-ffffb17e5000 r--s 00000000 b3:02 2782                       /usr/lib/aarch64-linux-gnu/gconv/gconv-modules.cache
 ffffb17e5000-ffffb17e6000 r--p 00000000 b3:02 8004                       /usr/lib/locale/C.UTF-8/LC_IDENTIFICATION
 ffffb17e6000-ffffb1807000 r-xp 00000000 b3:02 2818                       /usr/lib/aarch64-linux-gnu/ld-2.31.so
 ffffb1807000-ffffb1815000 rw-p 00000000 00:00 0 
 ffffb1815000-ffffb1816000 r--p 00000000 00:00 0                          [vvar]
 ffffb1816000-ffffb1817000 r-xp 00000000 00:00 0                          [vdso]
 ffffb1817000-ffffb1818000 r--p 00021000 b3:02 2818                       /usr/lib/aarch64-linux-gnu/ld-2.31.so
 ffffb1818000-ffffb181a000 rw-p 00022000 b3:02 2818                       /usr/lib/aarch64-linux-gnu/ld-2.31.so
 ffffc3e2c000-ffffc3e4d000 rw-p 00000000 00:00 0                          [stack]
 Name:	marco
 Umask:	0002
 State:	S (sleeping)
 Tgid:	6704
 Ngid:	0
 Pid:	6704
 PPid:	1
 TracerPid:	0
 Uid:	1000	1000	1000	1000
 Gid:	1000	1000	1000	1000
 FDSize:	64
 Groups:	0 24 27 100 117 1000 
 NStgid:	6704
 NSpid:	6704
 NSpgid:	6456
 NSsid:	6456
 VmPeak:	  683780 kB
 VmSize:	  683780 kB
 VmLck:	       0 kB
 VmPin:	       0 kB
 VmHWM:	   30948 kB
 VmRSS:	   30948 kB
 RssAnon:	    8216 kB
 RssFile:	   22720 kB
 RssShmem:	      12 kB
 VmData:	   49028 kB
 VmStk:	     132 kB
 VmExe:	      16 kB
 VmLib:	   31336 kB
 VmPTE:	     184 kB
 VmSwap:	       0 kB
 CoreDumping:	1
 THP_enabled:	0
 Threads:	5
 SigQ:	0/14018
 ShdPnd:	0000000000000000
 SigBlk:	0000000000000000
 SigIgn:	0000000001001000
 SigCgt:	0000000180004000
 CapInh:	0000000000000000
 CapPrm:	0000000000000000
 CapEff:	0000000000000000
 CapBnd:	0000003fffffffff
 CapAmb:	0000000000000000
 NoNewPrivs:	0
 Seccomp:	0
 Speculation_Store_Bypass:	unknown
 Cpus_allowed:	f
 Cpus_allowed_list:	0-3
 Mems_allowed:	1
 Mems_allowed_list:	0
 voluntary_ctxt_switches:	2407
 nonvoluntary_ctxt_switches:	709
Signal: 11
Uname: Linux 5.4.0-1041-raspi aarch64
UserGroups: admin cdrom root sudo users
_LogindSession: c11
CoreDump: base64

theleftover · 16 August 2021 23:37

I also placed an unabridged crash file here: http://www.button.network/_usr_bin_marco.1000.crash.txt

Probably a different one.

I appreciate any and all help. Is there anything we can do to goose the priority? Whatever we do here will be baked into our product for years.

If this helps, it seems like our rig is pretty vanilla. I cannot think of anything esoteric about our setup.

Well, here is one thing: The Raspberry Pi, lacking bios, calls for putting some things into config.txt, which is loaded very early in the boot cycle. Ours looks like this:

# Place "config.txt" changes (dtparam, dtoverlay, disable_overscan, etc.) in
# this file. Please refer to the README file for a description of the various
# configuration files on the boot partition.
dtoverlay=dwc2,dr_mode=host
dtoverlay=vc4-fkms-v3d
disable_overscan=1

The last two lines were added recently to help xrandr work normally. If you do a search on 'dtoverlay=vc4-fkms-v3d', you will see that it sometimes has downstream implications.

gordon · 17 August 2021 21:56

This is Ubuntu 20.04 ARM64 on a Pi, or a different version?

theleftover · 18 August 2021 15:38

Yes. 20.04.2 Ubuntu on a Compute Module 4 (i.e. Pi4).

If it makes any difference, I installed the Ubunytu raspi image and then loaded MATE using Tasksel.

Today I will try to pin down the sequence that causes it more closely. See my issue posted here: Frequent crashes on Ubun

I mistook which utility was crashing. The morning Xorg is crashing like clockwork. Not Marco. Sorry for the confusion.

gordon · 19 August 2021 18:02

I really don't know much about the Raspberry Pi unfortunately, so I can't help you very much longer.

However, is the Pi perhaps overclocked? Does Xorg run stably if the Pi is not overclocked?

theleftover · 19 August 2021 18:24

Gordon, thank you. I appreciate your effort.

FWIW, I think the advent of the Pi4 has made new things possible. I am replacing an x86 system with a Pi at a 40% cost reduction and slightly better performance. That's pretty significant!

It is fresh terrain all around. I am a recent arrival to MATE off KDE because of MATE's support for the Pi. Hopefully, this path will get more trodden soon -- maybe even paved a little.

No overclocking going on here.

Ma_N0 · 7 July 2022 14:45

Greetings from Ubuntu Mate 22.04, I installed it just yesterday and the problem on "marco" occurred to me too, at the fourth or the fifth reboot.
Any news about the solution?
Thanks.
Regards.

BrujaBche · 26 August 2022 01:43

Exactly the same problem here, also on Ubuntu Mate 22.04
It happens to me on every reboot.
Regards!

ricmarques · 27 August 2022 22:31

Today (27th August 2022), I've upgraded my Ubuntu MATE 20.04.5 LTS ("Focal Fossa") to Ubuntu Mate 22.04.1 LTS ("Jammy Jellyfish") in my laptop.

As I've posted earlier in this thread / topic, when I was using Ubuntu 20.04, I had several "marco" crashes ("Sorry, Ubuntu 20.04 has experienced an internal error.") - "Title: marco crashed with SIGSEGV in cairo_region_num_rectangles()" - back then using the 1.24.0-1 version of "marco" (Package: marco 1.24.0-1ubuntu1).

Now that I've upgraded today to Ubuntu MATE 22.04.1 LTS ("Jammy Jellyfish"), I've also got a "marco" crash ("Sorry, Ubuntu 22.04 has experienced an internal error.") at maybe the third reboot after the Ubuntu upgrade. However, now with Ubuntu Mate 22.04, the version of marco is different (1.26.0-3) - "Package: marco 1.26.0-3ubuntu1" - and the title of the crash is also different: "Title: marco crashed with signal 5 in _XReadEvents()".

Here's the relevant info:

Screenshot:

Crash file :

The crash file "_usr_bin_marco.1000.crash" in the "/var/crash" directory (folder) has the following information (among other):

ProblemType: Crash
Architecture: amd64
CurrentDesktop: MATE
Date: Sat Aug 27 22:21:25 2022
DistroRelease: Ubuntu 22.04
ExecutablePath: /usr/bin/marco
ExecutableTimestamp: 1649755698
ProcCmdline: marco
(...)
Package: marco 1.26.0-3ubuntu1
PackageArchitecture: amd64
(...)
SourcePackage: marco
Stacktrace:
 #0  0x00007fa05026b157 in g_log_writer_default () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 No symbol table info available.
 #1  0x00007fa050266c93 in g_log_structured_array () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 No symbol table info available.
 #2  0x00007fa050266e93 in g_log_structured_standard () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 No symbol table info available.
 #3  0x00007fa04f511eb4 in ?? () from /lib/x86_64-linux-gnu/libgdk-3.so.0
 No symbol table info available.
 #4  0x00007fa04eedc8f4 in _XError () from /lib/x86_64-linux-gnu/libX11.so.6
 No symbol table info available.
 #5  0x00007fa04eedc9f7 in ?? () from /lib/x86_64-linux-gnu/libX11.so.6
 No symbol table info available.
 #6  0x00007fa04eedca95 in ?? () from /lib/x86_64-linux-gnu/libX11.so.6
 No symbol table info available.
 #7  0x00007fa04eedde02 in _XReadEvents () from /lib/x86_64-linux-gnu/libX11.so.6
 No symbol table info available.
 #8  0x00007fa04eede0d1 in XWindowEvent () from /lib/x86_64-linux-gnu/libX11.so.6
 No symbol table info available.
 #9  0x00007fa05019fa3e in meta_display_get_current_time_roundtrip () from /lib/x86_64-linux-gnu/libmarco-private.so.2
 No symbol table info available.
 #10 0x00007fa0501a1c86 in ?? () from /lib/x86_64-linux-gnu/libmarco-private.so.2
 No symbol table info available.
 #11 0x00007fa0501a1ce5 in meta_display_set_input_focus_window () from /lib/x86_64-linux-gnu/libmarco-private.so.2
 No symbol table info available.
 #12 0x00007fa0501b9f89 in meta_window_focus () from /lib/x86_64-linux-gnu/libmarco-private.so.2
 No symbol table info available.
 #13 0x00007fa0501c1e0d in ?? () from /lib/x86_64-linux-gnu/libmarco-private.so.2
 No symbol table info available.
 #14 0x00007fa0501b945e in meta_window_free () from /lib/x86_64-linux-gnu/libmarco-private.so.2
 No symbol table info available.
 #15 0x00007fa05019fd6a in meta_display_unmanage_windows_for_screen () from /lib/x86_64-linux-gnu/libmarco-private.so.2
 No symbol table info available.
 #16 0x00007fa0501ae6c4 in meta_screen_free () from /lib/x86_64-linux-gnu/libmarco-private.so.2
 No symbol table info available.
 #17 0x00007fa05019fe6b in meta_display_close () from /lib/x86_64-linux-gnu/libmarco-private.so.2
 No symbol table info available.
 #18 0x000055965544b1db in main ()
 No symbol table info available.
StacktraceAddressSignature: /usr/bin/marco:5:/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.7200.1+44157:/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.7200.1+3fc93:/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.7200.1+3fe93:/usr/lib/x86_64-linux-gnu/libgdk-3.so.0.2404.29+4beb4:/usr/lib/x86_64-linux-gnu/libX11.so.6.4.0+2b8f4:/usr/lib/x86_64-linux-gnu/libX11.so.6.4.0+2b9f7:/usr/lib/x86_64-linux-gnu/libX11.so.6.4.0+2ba95:/usr/lib/x86_64-linux-gnu/libX11.so.6.4.0+2ce02:/usr/lib/x86_64-linux-gnu/libX11.so.6.4.0+2d0d1:/usr/lib/x86_64-linux-gnu/libmarco-private.so.2.0.0+16a3e:/usr/lib/x86_64-linux-gnu/libmarco-private.so.2.0.0+18c86:/usr/lib/x86_64-linux-gnu/libmarco-private.so.2.0.0+18ce5:/usr/lib/x86_64-linux-gnu/libmarco-private.so.2.0.0+30f89:/usr/lib/x86_64-linux-gnu/libmarco-private.so.2.0.0+38e0d:/usr/lib/x86_64-linux-gnu/libmarco-private.so.2.0.0+3045e
StacktraceTop:
 ?? () from /lib/x86_64-linux-gnu/libX11.so.6
 ?? () from /lib/x86_64-linux-gnu/libX11.so.6
 _XReadEvents () from /lib/x86_64-linux-gnu/libX11.so.6
 XWindowEvent () from /lib/x86_64-linux-gnu/libX11.so.6
 meta_display_get_current_time_roundtrip () from /lib/x86_64-linux-gnu/libmarco-private.so.2
Tags:  jammy
(...)
Title: marco crashed with signal 5 in _XReadEvents()
UpgradeStatus: Upgraded to jammy on 2022-08-27 (0 days ago)
_MarkForUpload: True
separator:

I've also found the following related Confirmed bug in Launchpad (I've already marked that bug as also affecting me), reported by https://launchpad.net/~navycatt on 10 September 2021, and that has tags for both "impish" and "jammy" (I see in that bug that Martin Wimpress - @Wimpy - himself has set the Information in that Bug as "Public" on 6th April 2022):

https://bugs.launchpad.net/ubuntu/+source/marco/+bug/1943289

I've also found the bug / issue reported about a month ago (on 21 July 2022) in the "marco" git repository of "mate-desktop" in GitHub:

Finally, I see that there's a different topic here in the "Ubuntu MATE Community" discussion forums, started by @Trav_Bro (also on 21 July 2022) reporting this same issue:

Maybe @gordon has some ideas about this?

ricmarques · 28 August 2022 14:57

Following up to my own yesterday's post: today (28th August 2022), after I turned on my laptop and logged in to my Ubuntu MATE 22.04.1 ("Jammy Jellyfish"), I got another "marco" crash ("internal error"), but this time with a different error message ("title") than the one I got yesterday. Today, the "title" of the crash is "Title: marco crashed with signal 5 in _XReply()".

Here's the relevant info:

Screenshot:

Crash file :

The crash file "_usr_bin_marco.1000.crash" in the "/var/crash" directory (folder) has the following information (among other):

ProblemType: Crash
Architecture: amd64
CrashCounter: 1
CurrentDesktop: MATE
Date: Sun Aug 28 02:10:27 2022
DistroRelease: Ubuntu 22.04
ExecutablePath: /usr/bin/marco
ExecutableTimestamp: 1649755698
ProcCmdline: marco
(...)
Package: marco 1.26.0-3ubuntu1
PackageArchitecture: amd64
(...)
SourcePackage: marco
Stacktrace:
 #0  0x00007fcf7b3eb157 in g_log_writer_default () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 No symbol table info available.
 #1  0x00007fcf7b3e6c93 in g_log_structured_array () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 No symbol table info available.
 #2  0x00007fcf7b3e6e93 in g_log_structured_standard () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 No symbol table info available.
 #3  0x00007fcf7a691eb4 in ?? () from /lib/x86_64-linux-gnu/libgdk-3.so.0
 No symbol table info available.
 #4  0x00007fcf7a05c8f4 in _XError () from /lib/x86_64-linux-gnu/libX11.so.6
 No symbol table info available.
 #5  0x00007fcf7a05c9f7 in ?? () from /lib/x86_64-linux-gnu/libX11.so.6
 No symbol table info available.
 #6  0x00007fcf7a05ca95 in ?? () from /lib/x86_64-linux-gnu/libX11.so.6
 No symbol table info available.
 #7  0x00007fcf7a05e30d in _XReply () from /lib/x86_64-linux-gnu/libX11.so.6
 No symbol table info available.
 #8  0x00007fcf7a05134f in XSync () from /lib/x86_64-linux-gnu/libX11.so.6
 No symbol table info available.
 #9  0x00007fcf7a68273f in ?? () from /lib/x86_64-linux-gnu/libgdk-3.so.0
 No symbol table info available.
 #10 0x00007fcf7b32e75f in meta_screen_free () from /lib/x86_64-linux-gnu/libmarco-private.so.2
 No symbol table info available.
 #11 0x00007fcf7b31fe6b in meta_display_close () from /lib/x86_64-linux-gnu/libmarco-private.so.2
 No symbol table info available.
 #12 0x000056471bdd81db in main ()
 No symbol table info available.
StacktraceAddressSignature: /usr/bin/marco:5:/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.7200.1+44157:/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.7200.1+3fc93:/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.7200.1+3fe93:/usr/lib/x86_64-linux-gnu/libgdk-3.so.0.2404.29+4beb4:/usr/lib/x86_64-linux-gnu/libX11.so.6.4.0+2b8f4:/usr/lib/x86_64-linux-gnu/libX11.so.6.4.0+2b9f7:/usr/lib/x86_64-linux-gnu/libX11.so.6.4.0+2ba95:/usr/lib/x86_64-linux-gnu/libX11.so.6.4.0+2d30d:/usr/lib/x86_64-linux-gnu/libX11.so.6.4.0+2034f:/usr/lib/x86_64-linux-gnu/libgdk-3.so.0.2404.29+3c73f:/usr/lib/x86_64-linux-gnu/libmarco-private.so.2.0.0+2575f:/usr/lib/x86_64-linux-gnu/libmarco-private.so.2.0.0+16e6b:/usr/bin/marco+11db
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
Tags:  jammy
(...)
Title: marco crashed with signal 5 in _XReply()
UpgradeStatus: Upgraded to jammy on 2022-08-27 (0 days ago)
_MarkForUpload: True
separator:

I've also found the following related Confirmed bug in Launchpad (I've already marked that bug as also affecting me), reported by Phillip Dunstall on 2021-12-10, for "Ubuntu 22.04" (I presume that, back then on December 2021, Philip Dunstall was using some kind of daily build, given that Ubuntu 22.04 was obviously only released a few months later, on April 2022) and that has tags for "jammy":

jorgebarrero · 30 January 2023 11:47

I upgraded to Ubuntu-Mate 22.04. in var/crash this info is reported

ProblemType: Crash
Architecture: amd64
CurrentDesktop: MATE
Date: Mon Jan 30 00:27:42 2023
DistroRelease: Ubuntu 22.04
ExecutablePath: /usr/bin/marco
ExecutableTimestamp: 1649755698
ProcCmdline: marco
ProcCwd: /home/jorge
ProcEnviron:
LANGUAGE=en_US
LC_TIME=es_VE.UTF-8
LC_MONETARY=es_VE.UTF-8
PATH=(custom, no user)
LC_ADDRESS=es_VE.UTF-8
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
LC_TELEPHONE=es_VE.UTF-8
SHELL=/usr/bin/zsh
LC_NAME=es_VE.UTF-8
LC_MEASUREMENT=es_VE.UTF-8
LC_IDENTIFICATION=es_VE.UTF-8
LC_NUMERIC=es_VE.UTF-8
LC_PAPER=es_VE.UTF-8
.....