file-roller crashed with SIGSEGV in gtk_widget_get_screen()

Bug #2058120 reported by Roman
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
file-roller (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

I saw https://bugs.launchpad.net/bugs/1428619, created a new bug to not lose my bug info and because that bug was last updated 8 years ago.

ProblemType: Crash
DistroRelease: Ubuntu 24.04
Package: file-roller 43.1-1
ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4
Uname: Linux 6.8.0-11-generic x86_64
ApportVersion: 2.28.0-0ubuntu1
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Sat Mar 16 22:21:41 2024
ExecutablePath: /usr/bin/file-roller
InstallationDate: Installed on 2024-02-14 (32 days ago)
InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240212)
ProcAttrCurrent: firefox (unconfined)
ProcCmdline: /usr/bin/file-roller /home/username/Downloads/handout.tar.zst
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=<set>
SegvAnalysis:
 Segfault happened at: 0x75b8b4f5fcef: mov 0xd0(%rax),%rbx
 PC (0x75b8b4f5fcef) ok
 source "0xd0(%rax)" (0x75b8000000d1) not located in a known VMA region (needed readable region)!
 destination "%rbx" ok
SegvReason: reading unknown VMA
Signal: 11
SignalName: SIGSEGV
SourcePackage: file-roller
StacktraceTop:
 ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0
 gtk_widget_get_screen () from /lib/x86_64-linux-gnu/libgtk-3.so.0
 gtk_widget_get_settings () from /lib/x86_64-linux-gnu/libgtk-3.so.0
 ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0
 ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0
Title: file-roller crashed with SIGSEGV in gtk_widget_get_screen()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip docker libvirt lpadmin plugdev sudo users
separator:

Revision history for this message
Roman (vient1) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Crash report cannot be processed

Thank you for your report!

However, processing it in order to get sufficient information for the
developers failed as the report has a core dump which is invalid. The
corruption may have happened on the system which the crash occurred or during
transit.

Thank you for your understanding, and sorry for the inconvenience!

Changed in file-roller (Ubuntu):
status: New → Invalid
tags: removed: need-amd64-retrace
Revision history for this message
Roman (vient1) wrote :

looks like the same bug

information type: Private → Public
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.