file-roller crashed with SIGSEGV
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
file-roller (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Happened when extracting multiple archives at once
ProblemType: Crash
DistroRelease: Ubuntu 18.10
Package: file-roller 3.30.0-1
ProcVersionSign
Uname: Linux 4.15.0-
NonfreeKernelMo
ApportVersion: 2.20.10-0ubuntu11
Architecture: amd64
CurrentDesktop: GNOME
Date: Tue Oct 9 07:51:28 2018
ExecutablePath: /usr/bin/
InstallationDate: Installed on 2018-07-28 (72 days ago)
InstallationMedia: Ubuntu-Studio 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
ProcCmdline: file-roller --extract-here --notify file://
SegvAnalysis:
Segfault happened at: 0x55b09fa76702: mov 0x1e0(%rax),%rbp
PC (0x55b09fa76702) ok
source "0x1e0(%rax)" (0x000001e0) not located in a known VMA region (needed readable region)!
destination "%rbp" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: file-roller
StacktraceTop:
()
g_closure_invoke () at /usr/lib/
() at /usr/lib/
g_signal_
g_signal_emit () at /usr/lib/
Title: file-roller crashed with SIGSEGV
UpgradeStatus: Upgraded to cosmic on 2018-09-30 (8 days ago)
UserGroups: adm audio cdrom dip docker lpadmin plugdev sambashare sudo
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.