file-roller crashed with SIGSEGV in g_closure_invoke()

[Jurgen Schellaert]

Selecting multiple rar files to "extract here" produces multiple pop-ups informing that extraction has been completed; dismissing the second one causes file-roller to crash.

ProblemType: Crash
DistroRelease: Ubuntu 20.04
Package: file-roller 3.36.1-1
ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
Uname: Linux 5.4.0-21-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu26
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sun Apr 12 13:40:35 2020
ExecutablePath: /usr/bin/file-roller
InstallationDate: Installed on 2020-04-05 (6 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
ProcCmdline: file-roller --extract-here --notify file:///home/username/Downloads/bx/IT/R%20Data%20Analysis%20Cookbook%202nd%20Edition%20(2017).rar file:///home/username/Downloads/bx/IT/R%20Data%20Visualization%20Recipes%20(2017).rar file:///home/username/Downloads/bx/IT/Security%20Tokens%20and%20Stablecoins%20Quick%20Start%20Guide%20-%20Learn%20how%20to%20build%20STO%20and%20stablecoin%20decentralized%20applications%20(2019).rar
SegvAnalysis:
 Segfault happened at: 0x565215c7a647: mov 0x1e0(%rax),%r12
 PC (0x565215c7a647) ok
 source "0x1e0(%rax)" (0x000001e0) not located in a known VMA region (needed readable region)!
 destination "%r12" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: file-roller
StacktraceTop:
 ?? ()
 g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_signal_emit_valist () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_signal_emit () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: file-roller crashed with SIGSEGV in g_closure_invoke()
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 #1603324, 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.