file-roller crashed with SIGSEGV in syscall()

[Václav Haisman]

It crashed when I tried to open Factorio game save which is a ZIP file.

ProblemType: Crash
DistroRelease: Ubuntu 16.04
Package: file-roller 3.16.5-0ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-22.40-lowlatency 4.4.8
Uname: Linux 4.4.0-22-lowlatency x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
Date: Sun Jun 5 16:42:03 2016
Disassembly: $6 = 0x0
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/file-roller
InstallationDate: Installed on 2011-11-13 (1666 days ago)
InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
ProcCmdline: file-roller /home/username/.factorio/saves/wilxFP119.zip
SegvAnalysis: Failure: invalid literal for int() with base 16: '<gdk_window_is_destroyed+7>:'
Signal: 11
SourcePackage: file-roller
StacktraceTop:
 syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
 g_cond_wait_until (cond=cond@entry=0x7f9a5c013c78, mutex=mutex@entry=0x7f9a5c013c70, end_time=end_time@entry=1300129815184) at /build/glib2.0-t9oPgV/glib2.0-2.48.0/./glib/gthread-posix.c:1444
 g_async_queue_pop_intern_unlocked (queue=queue@entry=0x7f9a5c013c70, wait=wait@entry=1, end_time=end_time@entry=1300129815184) at /build/glib2.0-t9oPgV/glib2.0-2.48.0/./glib/gasyncqueue.c:422
 g_async_queue_timeout_pop (queue=0x7f9a5c013c70, timeout=timeout@entry=15000000) at /build/glib2.0-t9oPgV/glib2.0-2.48.0/./glib/gasyncqueue.c:543
 g_thread_pool_thread_proxy () at /build/glib2.0-t9oPgV/glib2.0-2.48.0/./glib/gthreadpool.c:167
Title: file-roller crashed with SIGSEGV in syscall()
UpgradeStatus: Upgraded to xenial on 2016-04-23 (43 days ago)
UserGroups: adm admin audio cdrom dialout dip fax floppy fuse lp lpadmin mythtv netdev plugdev sambashare scanner tape vboxusers video wireshark

[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.