Comment # 4 on bug 1022082 from
(In reply to Bernhard Wiedemann from comment #3)
> file-roller does not crash here.
> which version of file-roller is that? e.g. rpm -q file-roller

=============================================
k_mikhail@linux-mk500:~> rpm -q file-roller
file-roller-3.20.3-2.1.x86_64
=============================================

> does it always crash?

It's hard to say. Seems, no:
=============================================
k_mikhail@linux-mk500:~> coredumpctl | grep file-roller
������ 2017-01-26 15:56:59 EET  11561  1000   100  11   /usr/bin/file-roller
������ 2017-01-26 19:17:22 EET  16339  1000   100  11   /usr/bin/file-roller
������ 2017-02-02 15:35:56 EET  19920  1000   100  11   /usr/bin/file-roller
������ 2017-02-11 19:57:08 EET   5574  1000   100  11   /usr/bin/file-roller
������ 2017-02-15 16:42:54 EET  24315  1000   100  11 * /usr/bin/file-roller
=============================================

> can you provide an archive that triggers the crash?

Due to, for example, '������ 2017-02-15 16:42:54 EET  24315  1000   100  11 *
/usr/bin/file-roller', that was happened on 'suricata-3.2.1.tar.gz' file, which
can be downloaded from
https://www.openinfosecfoundation.org/download/suricata-3.2.1.tar.gz


You are receiving this mail because: