Nothing obvious causes me to see the error.

[donwood]

I am just notified that it occurred without context. It then asks me if I want to send the error to you, It happens when I first log in so I am not "doing anything" yet. The only problem I have is when first checking for uploads, which I do first thing, it usually fails. Normally upon retry it then succeeds with download and update installs normally.

This was on the summary line when this page came up:
marco crashed with SIGSEGV in cairo_region_num_rectangles()

ProblemType: Crash
DistroRelease: Ubuntu 20.04
Package: marco 1.24.0-1
ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
Uname: Linux 5.4.0-14-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu16
Architecture: amd64
CurrentDesktop: MATE
Date: Thu Feb 20 12:59:07 2020
ExecutablePath: /usr/bin/marco
InstallationDate: Installed on 2019-12-07 (74 days ago)
InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Alpha amd64 (20191207)
ProcCmdline: marco
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f3b08a869d4 <cairo_region_num_rectangles+4>: mov 0x4(%rdi),%eax
 PC (0x7f3b08a869d4) ok
 source "0x4(%rdi)" (0x000000f5) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: marco
StacktraceTop:
 cairo_region_num_rectangles () from /lib/x86_64-linux-gnu/libcairo.so.2
 ?? () from /lib/x86_64-linux-gnu/libmarco-private.so.2
 ?? () from /lib/x86_64-linux-gnu/libmarco-private.so.2
 ?? () from /lib/x86_64-linux-gnu/libmarco-private.so.2
 ?? () from /lib/x86_64-linux-gnu/libmarco-private.so.2
Title: marco crashed with SIGSEGV in cairo_region_num_rectangles()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
separator:

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1863392, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.