Bug 129204 - Impress File rendered only white
Summary: Impress File rendered only white
Status: RESOLVED INSUFFICIENTDATA
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Impress (show other bugs)
Version:
(earliest affected)
6.2.0.0.alpha1+
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: bibisected, bisected, regression
Depends on:
Blocks:
 
Reported: 2019-12-05 11:13 UTC by Jean-Sebastien Bevilacqua
Modified: 2022-02-14 03:29 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:


Attachments
Test file (629.34 KB, application/vnd.oasis.opendocument.presentation)
2019-12-05 11:14 UTC, Jean-Sebastien Bevilacqua
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Jean-Sebastien Bevilacqua 2019-12-05 11:13:24 UTC
Description:
Hello,
I found a bug in Impress since version 6.2. Some Impress file may open only white.

I join a test file you can open, and you will see it only white.

Bibisection:

6.1.6.3        -> Works well
6.2.0.0.alpha1 -> Not working
6.2.0.1        -> Not working
6.3.4.1        -> Not working

The problem starts with version 6.2.x, it works well with version 6.1.

Steps to Reproduce:
1. Open the joined file
2. It's just white

Actual Results:
It's white

Expected Results:
It should be renderd with images and texts


Reproducible: Always


User Profile Reset: No



Additional Info:
Comment 1 Jean-Sebastien Bevilacqua 2019-12-05 11:14:11 UTC
Created attachment 156326 [details]
Test file
Comment 2 Xisco Faulí 2019-12-05 11:48:41 UTC Comment hidden (obsolete)
Comment 3 Jean-Sebastien Bevilacqua 2019-12-05 12:13:30 UTC
Strange, it works with 6.1.x version of LibreOffice.
Comment 4 Xisco Faulí 2019-12-05 12:18:15 UTC
(In reply to Jean-Sebastien Bevilacqua from comment #3)
> Strange, it works with 6.1.x version of LibreOffice.

oh wait, my bad, I thought it was a pptx file, that's why I checked in MSO 2010
Comment 5 Xisco Faulí 2019-12-05 12:31:39 UTC
Regression introduced by:

https://cgit.freedesktop.org/libreoffice/core/commit/?id=9826a4e4a6aa9953d3f354fe645a23f9dae59d77

author	Regina Henschel <rb.henschel@t-online.de>	2018-08-17 19:02:55 +0200
committer	Tomaž Vajngerl <quikee@gmail.com>	2018-08-27 16:27:17 +0200
commit 9826a4e4a6aa9953d3f354fe645a23f9dae59d77 (patch)
tree 25a38cbe766a092b8df736ab5c75581d77944895
parent 3ed1bd19eb7fb7898bcca8e046e058799f836063 (diff)
tdf#101242 Support draw:display and draw:protect attributes of ODF

Bisected with: bibisect-linux64-6.2

Adding Cc: to Regina Henschel
Comment 6 Regina Henschel 2019-12-05 12:50:20 UTC
Bug 128730 has a macro to repair the document.

Jean-Sebastien Bevilacqua: Can you tell something about the history of the document? Was it involved in a crash or recovery? Which versions were used to save the document? Are third-party applications used to save the document?

I still know no scenario that produces such documents.
Comment 7 Aron Budea 2021-07-17 21:05:09 UTC
Let's wait for an answer from Jean-Sebastien.
Comment 8 QA Administrators 2022-01-14 03:41:52 UTC Comment hidden (obsolete)
Comment 9 QA Administrators 2022-02-14 03:29:13 UTC
Dear Jean-Sebastien Bevilacqua,

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-FollowUp