Bug 108462 - FILEOPEN Using a custom font in a presentation makes opening it extremely slow
Summary: FILEOPEN Using a custom font in a presentation makes opening it extremely slow
Status: RESOLVED INSUFFICIENTDATA
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Impress (show other bugs)
Version:
(earliest affected)
5.2.2.2 release
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-06-11 12:19 UTC by Ophir LOJKINE
Modified: 2018-01-29 10:35 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments
Presentation that takes a very long time to open. (6.65 MB, application/vnd.oasis.opendocument.presentation)
2017-06-11 12:19 UTC, Ophir LOJKINE
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Ophir LOJKINE 2017-06-11 12:19:06 UTC
Created attachment 133954 [details]
Presentation that takes a very long time to open.

The attached file is a presentation with only 3 slides, one low-quality image, and a custom font.

However, it takes several minutes to open on a windows laptop, making it unusable. Once opened, it works normally.
Comment 1 Xisco Faulí 2017-06-11 13:33:24 UTC Comment hidden (obsolete)
Comment 2 QA Administrators 2018-01-02 10:14:30 UTC Comment hidden (obsolete)
Comment 3 QA Administrators 2018-01-29 10:35:24 UTC
Dear Bug Submitter,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INSUFFICIENTDATA due to inactivity and
a lack of information which is needed in order to accurately
reproduce and confirm the problem. We encourage you to retest
your bug against the latest release. If the issue is still
present in the latest stable release, we need the following
information (please ignore any that you've already provided):

a) Provide details of your system including your operating
   system and the latest version of LibreOffice that you have
   confirmed the bug to be present

b) Provide easy to reproduce steps – the simpler the better

c) Provide any test case(s) which will help us confirm the problem

d) Provide screenshots of the problem if you think it might help

e) Read all comments and provide any requested information

Once all of this is done, please set the bug back to UNCONFIRMED
and we will attempt to reproduce the issue. Please do not:

a) respond via email 

b) update the version field in the bug or any of the other details
   on the top section of our bug tracker

Warm Regards,
QA Team

MassPing-NeedInfo-20180129