RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1715109 - [fix available] Image with no extension can not be inserted but can be opened.
Summary: [fix available] Image with no extension can not be inserted but can be opened.
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: libreoffice
Version: 8.1
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: rc
: 8.0
Assignee: Caolan McNamara
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-05-29 15:17 UTC by Bill Sanford
Modified: 2020-11-14 12:49 UTC (History)
3 users (show)

Fixed In Version: libreoffice-6.0.6.1-16.el8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-11-05 20:54:23 UTC
Type: Bug
Target Upstream Version:
Embargoed:
pm-rhel: mirror+


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2019:3354 0 None None None 2019-11-05 20:54:28 UTC

Description Bill Sanford 2019-05-29 15:17:58 UTC
Description of problem:
I just installed RHEL-8.1.0-20190523.0 and libreoffice-6.0.6.1-13 and I try to insert and image File -> Insert -> Image to Writer (Or any LO app) with an image file (.jpg) that has no extension and I can't. If I do a File -> Open and select the file, without extension, it opens it within writer.

It seems like this was never tested and is default behavior.

Version-Release number of selected component (if applicable):
RHEL-8.1.0-20190523.0
libreoffice-6.0.6.1-13
libreoffice-filters-6.0.6.1-13

How reproducible:
100%

Steps to Reproduce:
1. Get or edit an image file, (JPG was used) and remove .jpg extension
2. File -> Insert -> Image to Writer and this file is not available.
3. Now try File -> Open and select the file.

Actual results:
Image is never shown to exist to add to Writer.

Expected results:
Image should be available to add.

Additional info:

I noticed that File -> Insert -> Image instead of having "All Files" in the dropdown of the Insert Image dialog, it has "All Images" or "All Formats," denoting that an extension is still hard coded to still require an extension.

Comment 1 Caolan McNamara 2019-05-31 14:35:36 UTC
My upstream patch for this https://gerrit.libreoffice.org/#/c/73276/

keep "<All formats>" to list everything that's known to be an image by its suffix, but add "All files" like file->open to list everything

Comment 3 Bill Sanford 2019-06-25 14:50:11 UTC
Verified with libreoffice-6.0.6.1-16.el8

Comment 5 errata-xmlrpc 2019-11-05 20:54:23 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, 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-2019:3354


Note You need to log in before you can comment on or make changes to this bug.