file-roller crashed with SIGSEGV in g_action_map_lookup_action()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
file-roller (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
I don't have much to add really, I think I just opened and closed a "MS-DOS executable, COFF for MS-DOS, DJGPP go32 DOS extender" file archive with an .exe extension.
But it's not fully reproducible - openening and closing it again did not trigger this segmentation fault.
ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: file-roller 3.28.0-1ubuntu1
ProcVersionSign
Uname: Linux 4.18.0-15-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sun Feb 24 15:07:58 2019
ExecutablePath: /usr/bin/
ProcCmdline: file-roller CO112SFS.exe
SegvAnalysis:
Segfault happened at: 0x7f6a39d5b9ac <g_action_
PC (0x7f6a39d5b9ac) ok
source "0x10(%rax)" (0x00000010) not located in a known VMA region (needed readable region)!
destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: file-roller
StacktraceTop:
g_action_
()
g_closure_invoke () at /usr/lib/
() at /usr/lib/
g_signal_
Title: file-roller crashed with SIGSEGV in g_action_
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip fax libvirt libvirtd lpadmin lxd plugdev sambashare sudo users vboxusers
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 #1725017, 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.