Created attachment 59187 [details] PPT file can be opened but when slide show is executed only blue screen is displayed Using LibreOffice v3.5.1 Impress on Windows XP. I opened attached ppt file and file opens successfully. In the right site I can clearly see slides. But when running a presentation slide show with <F5> then only blue screen is displayed. No slides are visible. So this file can't be seen in LibreOffice. I also tried pressing a mouse or <Enter> key and nothing really happens - but it looks like slides are trying to be displayed, because if I press <Esc> key to abort presentation I see non-first slide is currently marked as active slide - so Enter key is working properly to go to Next slide - but no content displayed.
I have tried to open and run PPT file in LibreOffice v3.5.4.2 on Windows XP and file can be normally opened and run. So it looks problem fixed.
Thanks for bugreport in 3.5.4 on Fedora 64 bit pictures seen on press F5. But depending on: Tools->Options->LibreOffice->View-> "Use hardware acceleration" if enabled, then no transition effect if disabled, then effect present in both cases seen one blink before something appears in 3.3.4 on Fedora 64 bit all works correctly in both cases, not blinking therefore regression after 3.3.4 in 3.6.b1 on Fedora 64 bit the same problem as in 3.5.4 on Windows not tested
I tested again in LibreOffice 3.5.4.2 with or without hardware acceleration. So it looks like this was fixed for Windows.
Thanks for additional testing. Then it becomes Linux-only problem
Now I have also tested on LibreOffice 3.5.3.2 on Ubuntu 12.04 and LibreOffice 3.5.4.2 on Ubuntu 12.04. I can confirm document can also be opened on Ubuntu, so major problem solved. Just reading sasha's respond more carefully. I also do not see any transitions effect on Windows/Ubuntu. There is just a blink. But major problem is solved, I can at least open a file and see slide-show (which I was unable at bug report time).
Bibisected with 3.5 on Ubuntu 11.10. ----- 32da975c44003573f7346a9a4a783742a3e974b9 is the first bad commit commit 32da975c44003573f7346a9a4a783742a3e974b9 Author: Bjoern Michaelsen <bjoern.michaelsen@canonical.com> Date: Thu Dec 8 01:07:57 2011 +0100 source-hash-62f4128d74179c6211fc961845182bf2956e3323 commit 62f4128d74179c6211fc961845182bf2956e3323 Author: Tor Lillqvist <tml@iki.fi> AuthorDate: Thu Oct 20 08:32:16 2011 +0300 Commit: Tor Lillqvist <tml@iki.fi> CommitDate: Thu Oct 20 08:41:36 2011 +0300 char can be unsigned, use sal_Int8 :100644 100644 26adf8f909ccd514d5c1205a328c0636813bc197 8315f3c6a0ac1a6a80c508ab93173aeb62077bb1 M ccache.log :100644 100644 0eaea8500fd118ddb2e7b81c99c91208f8b0d6b8 1912db4a3e9a32351a9537d67160a24d598b7ee8 M commitmsg :100644 100644 23abcebefdb55ef132cbe42ddb3f406327c3a158 480212515e08b6fe4708f4142dc2ffb4f2cf76d1 M dev-install.log :100644 100644 81490d34db5ec1e2b2d82880c47a6b7bb1cf0f6f 0b0c8eff2e8deb9db196bdf9df2440106655284c M make.log :040000 040000 5f049a7edc27e0db9531c966605247de72a87a0b 5da2e578b27bd55137ddd931bd7c3bd1ad2bf414 M opt $ git bisect log # bad: [4c30602f43475389f81b1d981ce8ee9a3410b9d9] source-hash-85c6244b85b29c1d2bb9d89b62e9512dd65378b5 # good: [65fd30f5cb4cdd37995a33420ed8273c0a29bf00] source-hash-d6cde02dbce8c28c6af836e2dc1120f8a6ef9932 git bisect start 'latest' 'oldest' # bad: [2faf4bc12ab490370d2196dedbc8091f9b09d0a5] source-hash-418a35f4861e863feb39eec73f4a39a87fbcb1f3 git bisect bad 2faf4bc12ab490370d2196dedbc8091f9b09d0a5 # bad: [2faf4bc12ab490370d2196dedbc8091f9b09d0a5] source-hash-418a35f4861e863feb39eec73f4a39a87fbcb1f3 git bisect bad 2faf4bc12ab490370d2196dedbc8091f9b09d0a5 # good: [4bae211a2589ecaec48c1409cf7cd1580d3e14c5] source-hash-31e7820f03badc3c6fe8fdaffb74f2125e05ea96 git bisect good 4bae211a2589ecaec48c1409cf7cd1580d3e14c5 # good: [eca91b9203dad6a608086451c6ad119f856782e4] source-hash-003973f5d461b981737946456eb08b2b7d60f150 git bisect good eca91b9203dad6a608086451c6ad119f856782e4 # bad: [b7e3f39afb62647252f6e649962e94eb967a3cce] source-hash-3e5eece31d93ed378613991c8a8bbe451aa5c081 git bisect bad b7e3f39afb62647252f6e649962e94eb967a3cce # bad: [32da975c44003573f7346a9a4a783742a3e974b9] source-hash-62f4128d74179c6211fc961845182bf2956e3323 git bisect bad 32da975c44003573f7346a9a4a783742a3e974b9 # good: [8cf17558c98d06aa33880dafcd22adf710d40f40] source-hash-d6f2418d0828ec4275355502ae3f87c80e16e8f5 git bisect good 8cf17558c98d06aa33880dafcd22adf710d40f40
I tested this bug in LibreOffice 3.6.4.3 on Windows XP and I see no problem anymore. I am marking a bug fixed.
Thanks for additional testing. On RFR 17 64 bit still reproducible. Please, do not close this bugreport for we do not forget to fix it. Or tell me to open separate bugreport for Linux.
Sasha, sorry I have missed your "Comment 4" referring that this is not working on Linu. "Mea culpa". I installed LibreOffice 3.6 on Ubuntu 12.04 32-bit using the following commands (adding PPA): sudo add-apt-repository ppa:libreoffice/ppa sudo apt-get update sudo apt-get install libreoffice libreoffice-gnome After install completed I started LibreOffice and checked Help | About and there is 3.6.0.2 (so looks like build without fixes). I opened Impress file attached to this bug report and file opened successfully and slide show works fine. Sasha, can you please specify what is the LibreOffice version and Linux distribution/version you are using. I am using 32-bit Ubuntu and LibreOffice, you refer to 64-bit.
My OS is Russian Fedora Remix 17 "Beefy miracle" 64 bit LO is 3.6.4 installed from libreoffice.org from rpm
I tried to bisect the bi-bisected range, but unfortunately it did not lead anywhere. Also, I did not spot a commit in the bi-bisected range that would do anything related to slideshow or impress :-( - so I am afraid something Sasha: Any chance you could try with LO 4.0 if your problem is still there? And can you try with distro-provided 3.6 if that contains the problem? Thank you!
in 4.0.0 on RFR 17 64 bit transitions working correctly also with hardware acceleration enabled. So, we may close it as WFM > And can you try with distro-provided 3.6 Most fresh version of LO in Fedora 17 repository is 3.5.7.2. So can not test 3.6. IMHO 3.6 will never appear there.