Continuing installation after the warning leads to functional LO, however, presentation mode fails presenting a corrupted screen image. Reinstallation doesn't fix the bug. The screen is split between two images and overlaid by a white screen. Regards, Hermann.
Warning 1946 is only about creating shortcuts. Please copy and paste to a comment the contents of your Help - About. Set to NEEDINFO. Change back to UNCONFIRMED after you have provided the information.
Created attachment 133034 [details] Screen dump of corrupted presentation slide using impress The attached file contains the error using the presentation mode of LO impress. Meanwhile I found a workaround by deactivating "Hardware Beschleunigung" in "Ansicht" unter "Libre Office" "Optionen". Now the presentation mode works fine.
Try this: enable Hardware acceleration, but disable OpenGL. Then comment on the result here. (I am half-assuming you had OpenGL enabled)
I checked the different variations. The display of the presentation mode works fine when Hardware acceleration is disabled, regardless of having oppenGL active or not. Anyway, thanks for the advice. By the way, Open Office worked fine even if Hardware acceleration was swichted on. Hermann Gies.
(In reply to KHGies from comment #4) > I checked the different variations. The display of the presentation mode > works fine when Hardware acceleration is disabled, regardless of having > oppenGL active or not. > Anyway, thanks for the advice. By the way, Open Office worked fine even if > Hardware acceleration was swichted on. > > Hermann Gies. But does it work OK with Hardware acceleration enabled AND OpenGL Disabled?
If both, acceleration and OpenGL are enabled, LO restarts, yielding OpenGL disabled and the performance is corrupted (windows 10(64) and LO 5.3(64). In one installation of LO 5.2(64) on windows 7 pro(64) acceleration and openGL has been enabled, however, the performance is corrupted. Disabling acceleration and keeping open GL enabled, leads to stable performance.
Sounds like the classic DirectX driver brokenness: bug 54417 has a pointer on how to generate a blacklist entry, if you can generate that for us, happy to disable your hw/driver combo.
(In reply to Thorsten Behrens (CIB) from comment #7) > Sounds like the classic DirectX driver brokenness: bug 54417 has a pointer > on how to generate a blacklist entry, if you can generate that for us, happy > to disable your hw/driver combo. Hello KHGies, could you please provide the info requested by Thorsten? I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' once the requested information is provided.
Dear Bug Submitter, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping-20180502
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-20180530