Bug 2150140

Summary: catdoc extracts no text from LibreOffice .doc files
Product: [Fedora] Fedora Reporter: skierpage <info>
Component: catdocAssignee: Adel Gadllah <adel.gadllah>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: 41CC: adel.gadllah, redhat-bugzilla
Target Milestone: ---Keywords: Patch, Reopened
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: ---
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2025-12-17 15:25:17 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:
Attachments:
Description Flags
simple LibreOffice Writer file saved as Word 97-2003 .doc file none

Description skierpage 2022-12-01 22:14:33 UTC
Description of problem:
KDE's baloo wasn't indexing many of my .doc files (I filed https://bugs.kde.org/show_bug.cgi?id=438455). Baloo uses KFileMetadata which for files with MIME type application/msword invokes `catdoc` to extract text, and `catdoc` produces no output for LibreOffice files saved as .doc.

This sounds like Debian bug https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874048 . Debian is carrying a simple patch that fixes this https://salsa.debian.org/debian/catdoc/-/blob/debian/sid/debian/patches/06-Fix_OLENAMELENGTH.patch which does not seem to be upstreamed, and in a comment on my KDE bug, @tagwerk19 reported that catdoc 0.95 in "KDE Neon Testing (rebased on Ubuntu 22.04)" does produce output.

Version-Release number of selected component (if applicable):
catdoc-0.95-13.fc37.src.rpm

How reproducible:
Happens every time.

Steps to Reproduce:
1. Create a LibreOffice Writer file with some words in it, save as Word 97-2003 .doc file.
2. Enter `catdoc path/to/test_LO_file.doc` in a terminal.
3. Enter `echo $?`

Actual results:
No output and exit code 69

Expected results:
Some output.

Additional info:
Debian has other useful patches to catdoc, https://salsa.debian.org/debian/catdoc/-/tree/debian/sid/debian/patches

I can't figure out how to access upstream's bug tracker, http://www.wagner.pp.ru/~vitus/software/catdoc/

Comment 1 skierpage 2022-12-01 22:19:38 UTC
Created attachment 1929170 [details]
simple LibreOffice Writer file saved as Word 97-2003 .doc file

Comment 2 skierpage 2023-10-28 21:14:56 UTC
(In reply to skierpage from comment #0)
> Debian has other useful patches to catdoc,
> https://salsa.debian.org/debian/catdoc/-/tree/debian/sid/debian/patches
I created the GitHub repo https://github.com/skierpage/catdoc to assemble this bug fix, the other Debian patches, and other fixes to catdoc floating around, although I'm barely proficient in C and don't understand Office formats. I let the Fedora maintainer "rsc" know about it, but they (understandably) aren't interested in taking on a bunch of undocumented unreproduceable fixes.

> I can't figure out how to access upstream's bug tracker,
> http://www.wagner.pp.ru/~vitus/software/catdoc/
The same git history of 0.95 is also on GitHub at https://github.com/vbwagner/catdoc , but has no commits for 7 years. So catdoc is a project with no upstream maintainer :-(

Comment 3 Aoife Moloney 2023-11-23 00:40:23 UTC
This message is a reminder that Fedora Linux 37 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 37 on 2023-12-05.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
'version' of '37'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version. Note that the version field may be hidden.
Click the "Show advanced fields" button if you do not see it.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 37 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Comment 4 skierpage 2023-11-23 09:21:27 UTC
Still fails in Fedora 39.

Comment 5 Aoife Moloney 2024-11-08 10:45:21 UTC
This message is a reminder that Fedora Linux 39 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 39 on 2024-11-26.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
'version' of '39'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version. Note that the version field may be hidden.
Click the "Show advanced fields" button if you do not see it.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 39 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Comment 6 skierpage 2024-11-09 07:50:30 UTC
Still fails in Fedora 41. Still no upstream, but Debian's version with multiple patches is much better than Fedora.

Comment 7 Adam Williamson 2025-12-02 01:12:09 UTC
This message is a reminder that Fedora Linux 41 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 41 on 2025-12-15.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
'version' of '41'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version. Note that the version field may be hidden.
Click the "Show advanced fields" button if you do not see it.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 41 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Comment 8 Samyak Jain (RedHat) 2025-12-16 17:05:30 UTC
Fedora Linux 41 entered end-of-life (EOL) status on 2025-12-15.

Fedora Linux 41 is no longer maintained, which means that it
will not receive any further security or bug fix updates. As a result we
are closing this bug.

If you can reproduce this bug against a currently maintained version of Fedora Linux
please feel free to reopen this bug against that version. Note that the version
field may be hidden. Click the "Show advanced fields" button if you do not see
the version field.

If you are unable to reopen this bug, please file a new report against an
active release.

Thank you for reporting this bug and we are sorry it could not be fixed.

Comment 9 skierpage 2025-12-17 11:09:12 UTC
Still fails in Fedora 43. vbwagner has shown signs of life at https://github.com/vbwagner/catdoc/ and I think fixed this bug, but hasn't made a new release. Still no interest from Fedora packagers in my updated repository that now has even more bugs fixed including important CVEs.

Comment 10 Samyak Jain (RedHat) 2025-12-17 15:25:17 UTC
Fedora Linux 41 entered end-of-life (EOL) status on 2025-12-15.

Fedora Linux 41 is no longer maintained, which means that it
will not receive any further security or bug fix updates. As a result we
are closing this bug.

If you can reproduce this bug against a currently maintained version of Fedora Linux
please feel free to reopen this bug against that version. Note that the version
field may be hidden. Click the "Show advanced fields" button if you do not see
the version field.

If you are unable to reopen this bug, please file a new report against an
active release.

Thank you for reporting this bug and we are sorry it could not be fixed.