Hi! Presentation demonstration hangs only with enabled hardware acceleration option. Noticed on x86 and amd64 systems (Intel and NVIDIA graphics) (slackware-current with KDE SC 4.10.2) It happen with any presentations. It's confirmed by Eric "AlienBOB" Hameleers.
Hi galym, Thanks for reporting. Is it possible for "AlienBOB" to leave a message over here he can reproduce this behavior, and add a bit more system information? In that way we can mark this bug as NEW. Kind regards, Joren
The bug was mentioned in this blog post: http://slackblogs.blogspot.nl/2013/02/libreoffice-transparent-slide-show.html I have experienced this myself as well. It started with LibreOffice 4.0.0 and as mentioned in the blog, Slackware updated its X.Org around the same time in the development release we (the reporters of this bug) are all using. See the "Fri Feb 22 01:09:25 UTC 2013" update in http://slackware.osuosl.org/slackware-current/ChangeLog.txt where xorg-server was updated to 1.13.2, libdrm to 2.4.42, cairo to 1.12.14, mesa to 9.0.2 among others. My system has NVIDIA proprietary graaphics drivers installed. Cheers, Eric
Could be NOTOURBUG - proprietary drivers + an update to xorg around the same time makes me wonder - requesting additional input Also - was this a problem with 3.6 or before?
Sounds like Eric Hameleers confirms this bug, so Status -> NEW Whiteboard: Remove 'Need_Advice' The devs will be in a better position to determine if this bug is ours or not.
** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: *Test to see if the bug is still present on a currently supported version of LibreOffice (4.4.1 or later) https://www.libreoffice.org/download/ *If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior *If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System Please DO NOT *Update the version field *Reply via email (please reply directly on the bug tracker) *Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to "inherited from OOo"; 4b. If the bug was not present in 3.3 - add "regression" to keyword Feel free to come ask questions or to say hello in our QA chat: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for your help! -- The LibreOffice QA Team This NEW Message was generated on: 2015-04-18
Created attachment 123190 [details] example.odp
The document attached reproduces the near behavior described in the Debian report. The acceleration is also involved. I ask more to the user on its hardware configuration. He uses LO 4.3.3.
Now, the Debian user use LO 5.0.5.2 and can reproduce this bug. He has a graphics card (lspci output): 00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09)
** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present on a currently supported version of LibreOffice (5.2.5 or 5.3.0 https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to "inherited from OOo"; 4b. If the bug was not present in 3.3 - add "regression" to keyword Feel free to come ask questions or to say hello in our QA chat: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug-20170306
This is rather old bug last tested with LO 5.0. Looks reasonable to set back to Needinfo. Please test with newer LO and daily master if possible, easiest from https://www.libreoffice.org/download/appimage/
Dear galym, 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
Dear galym, 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
(In reply to Timur from comment #10) > This is rather old bug last tested with LO 5.0. > Looks reasonable to set back to Needinfo. > Please test with newer LO and daily master if possible, easiest from > https://www.libreoffice.org/download/appimage/ Ce bogue a été reproduit par le rapporteur original dans LO 7.0.4 et 7.4.3 sur Debian.
This bug was reproduced by the original reporter in LO 7.0.4 and 7.4.3 on Debian.