file-roller crashed with SIGSEGV in ???()

[Eric Carvalho]

File-roller crashes while browsing the contents of big archives. I'm actually trying to select and extract some folders from https://download.qt.io/official_releases/qt/6.6/6.6.2/single/qt-everywhere-src-6.6.2.tar.xz

$ lsb_release -rd
No LSB modules are available.
Description: Ubuntu Noble Numbat (development branch)
Release: 24.04

$ apt-cache policy file-roller
file-roller:
  Installed: 43.1-1
  Candidate: 43.1-1
  Version table:
 *** 43.1-1 500
        500 http://archive.ubuntu.com/ubuntu noble/main amd64 Packages
        100 /var/lib/dpkg/status

ProblemType: Crash
DistroRelease: Ubuntu 24.04
Package: file-roller 43.1-1
ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3
Uname: Linux 6.6.0-14-generic x86_64
ApportVersion: 2.27.0-0ubuntu6
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Fri Feb 16 14:37:59 2024
ExecutablePath: /usr/bin/file-roller
InstallationDate: Installed on 2023-05-16 (276 days ago)
InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230516)
ProcCmdline: /usr/bin/file-roller /home/username/Downloads/qt-everywhere-src-6.6.2.tar.xz
SegvAnalysis:
 Segfault happened at: 0x55c7652e82d0: mov (%rbx),%rsi
 PC (0x55c7652e82d0) ok
 source "(%rbx)" (0x200000006) not located in a known VMA region (needed readable region)!
 destination "%rsi" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: file-roller
StacktraceTop:
 ??? ()
 ??? () at /lib/x86_64-linux-gnu/libgtk-3.so.0
 g_closure_invoke () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ??? () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ??? () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: file-roller crashed with SIGSEGV in ???()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dialout dip lpadmin plugdev sudo users vboxusers wireshark
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 #2037767, 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.