Bug 1473749

Summary: libreoffice apps are unable to show license
Product: Red Hat Enterprise Linux 7 Reporter: Martin Krajnak <mkrajnak>
Component: libreofficeAssignee: David Tardon <dtardon>
Status: CLOSED ERRATA QA Contact: Desktop QE <desktop-qa-list>
Severity: low Docs Contact:
Priority: medium    
Version: 7.5CC: dtardon, tpelka
Target Milestone: rcKeywords: Regression, Reopened
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-04-10 12:03:00 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Description Martin Krajnak 2017-07-21 14:33:15 UTC
Description of problem:
Clicking the license button in License Information dialog cause dialog to disappear but does not show the license information.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1.Open any libreoffice app (Impress in my case)
2.Navigate to "Help -> License Information..."
3.Click "Show License"

Actual results:
nothing is shown

Expected results:
Should show license information (I think that in previous version license file was displayed using LibreOffice Writer)

Additional info:
I am using the updated libreoffice version (libreoffice-impress- on RHEL 7.4

Comment 1 Caolan McNamara 2017-07-21 14:48:24 UTC
looks to me that the packaging moved the LICENSE.html file to /usr/share/doc/libreoffice-data so the attempt to find it in showDocument in sfx2/source/appl/appserv.cxx fails

Comment 2 David Tardon 2017-10-02 10:52:21 UTC
This has never appeared in any official RHEL version, just in the CSB one, so let's just close the bug silently...

Comment 3 Martin Krajnak 2017-11-16 08:50:51 UTC
I can reproduce this bug with the most current version of LO:

Comment 6 Martin Krajnak 2017-12-20 13:27:55 UTC
Fixed in version:

Comment 10 errata-xmlrpc 2018-04-10 12:03:00 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.