file-roller crashed with SIGSEGV in syscall()

[Dustyn Gibson]

Opened a tar.gz, double clicked a python file which should have been opened in my editor but instead crashed file-roller

ProblemType: Crash
DistroRelease: Ubuntu 16.04
Package: file-roller 3.16.4-1ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-17.33-generic 4.4.6
Uname: Linux 4.4.0-17-generic x86_64
ApportVersion: 2.20.1-0ubuntu1
Architecture: amd64
CurrentDesktop: GNOME
Date: Mon Apr 4 02:48:17 2016
ExecutablePath: /usr/bin/file-roller
InstallationDate: Installed on 2015-08-20 (228 days ago)
InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 (20150422)
ProcCmdline: file-roller /home/username/Downloads/httplib2.ca_certs_locater-0.2.0.tar.gz
ProcEnviron:
 LD_LIBRARY_PATH=<set>
 PATH=(custom, user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Registers: $8 = 0x4 <error: Cannot access memory at address 0x4>
SegvAnalysis: Failure: invalid literal for int() with base 16: '='
Signal: 11
SourcePackage: file-roller
StacktraceTop:
 syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
 g_cond_wait_until (cond=cond@entry=0xa0dd68, mutex=mutex@entry=0xa0dd60, end_time=end_time@entry=151328114408) at /build/glib2.0-VLj5wM/glib2.0-2.48.0/./glib/gthread-posix.c:1444
 g_async_queue_pop_intern_unlocked (queue=queue@entry=0xa0dd60, wait=wait@entry=1, end_time=end_time@entry=151328114408) at /build/glib2.0-VLj5wM/glib2.0-2.48.0/./glib/gasyncqueue.c:422
 g_async_queue_timeout_pop (queue=0xa0dd60, timeout=timeout@entry=15000000) at /build/glib2.0-VLj5wM/glib2.0-2.48.0/./glib/gasyncqueue.c:543
 g_thread_pool_thread_proxy () at /build/glib2.0-VLj5wM/glib2.0-2.48.0/./glib/gthreadpool.c:167
ThreadStacktrace: $4 = 0x0
Title: file-roller crashed with SIGSEGV in syscall()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip libvirtd 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 #1428619, 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.