Bug 1845169

Summary:	file command fails to recognize some DOCX files created with libreoffice
Product:	Red Hat Enterprise Linux 8	Reporter:	Andrew Mike <amike>
Component:	file	Assignee:	Vincent Mihalkovič <vmihalko>
Status:	CLOSED ERRATA	QA Contact:	Karel Volný <kvolny>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	8.2	CC:	alanm, brclark, fsumsal, jwright, kdudka, kvolny
Target Milestone:	rc
Target Release:	8.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	file-5.33-16.el8	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-11-04 01:57:38 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1857095

Description Andrew Mike 2020-06-08 15:05:09 UTC

Description of problem:
When "file" is run on certain DOCX documents created with LibreOffice (example attached), it is read as a zip file and not a DOCX document.

Version-Release number of selected component (if applicable):
5.33-13.el8

How reproducible: Consistently

Steps to Reproduce:
1. Run "file" on the test file (attached).

Actual results: File is read as "Zip archive data".

Expected results: File is read as "Microsoft Word 2007+"

Additional info:
- File was created with libreoffice-writer-6.3.6.2-3.fc31.x86_64 package.
- According to the customer filing a related support case, this may happen because LibreOffice "may save .docs without '[Content_Types].xml' being first (see attached docx) and instead _rels/.rels is first in the docx archive".
- Customer alleges this is not an issue in the file utility shipped with Fedora 31.

Comment 2 Vincent Mihalkovič 2020-06-15 14:11:16 UTC

Bug fixed in following upstream commit: https://github.com/file/file/commit/1ff074fc5

Comment 11 errata-xmlrpc 2020-11-04 01:57:38 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (file bug fix and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2020:4531