pdf arranger (pdfshuffler package) crashed when closing

[Christopher Kiraly]

I apt installed pdfshuffler, used the PDF Arranger program installed, and upon closing it, the screen flashed (crashing Marco) and reset. I had Firefox open with 16 pinned tabs open, as well as Chrome with 2 tabs open (running Youtube video), and 2 Caja windows open. Nothing else closed or crashed. Everything else worked fine.

ProblemType: Crash
DistroRelease: Ubuntu 20.04
Package: marco 1.24.0-1ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
Uname: Linux 5.4.0-21-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu26
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: MATE
Date: Sun Apr 12 08:35:29 2020
ExecutablePath: /usr/bin/marco
InstallationDate: Installed on 2020-04-03 (8 days ago)
InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
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: 0x7f74cd4119d4 <cairo_region_num_rectangles+4>: mov 0x4(%rdi),%eax
 PC (0x7f74cd4119d4) ok
 source "0x4(%rdi)" (0x06c00005) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading unknown 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 libvirt 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 #1871264, 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.