file-roller crashed with SIGSEGV in g_cclosure_marshal_VOID__ENUMv()

[Kirill I.]

#

ProblemType: Crash
DistroRelease: Ubuntu 16.04
Package: file-roller 3.16.5-0ubuntu1.2
ProcVersionSignature: Ubuntu 4.8.0-58.63~16.04.1-lowlatency 4.8.17
Uname: Linux 4.8.0-58-lowlatency x86_64
ApportVersion: 2.20.1-0ubuntu2.16
Architecture: amd64
CurrentDesktop: LXDE
Date: Thu Apr 12 05:27:10 2018
ExecutablePath: /usr/bin/file-roller
InstallationDate: Installed on 2012-05-25 (2147 days ago)
InstallationMedia: Kubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120423)
ProcCmdline: file-roller --extract /home/username/data/kerya4/kerya4/distrib/android-sdk_r20.0.3-linux.tgz
ProcEnviron:
 LANGUAGE=ru_UA:ru
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=ru_UA.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x449228: mov 0x1e0(%rax),%rbp
 PC (0x00449228) 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_cclosure_marshal_VOID__ENUMv () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: file-roller crashed with SIGSEGV in g_cclosure_marshal_VOID__ENUMv()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom debian-tor dialout dip disk libvirtd lp lpadmin plugdev sambashare sudo vboxusers

[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 #1760257, 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.