Created attachment 96048 [details] Sample odp file which prove the bug. Problem description: Steps to reproduce: 1. Start Impress 2. Open a file, for example, attached one. 3. Go to the slideshow mode. Current behavior: Existing figure is not displayed. Expected behavior: Figure should be displayed. Operating System: All Version: 4.1.0.4 release
This is a duplicate of bug 62038 - Sophie *** This bug has been marked as a duplicate of bug 62038 ***
The bug 62038 says "particular eps", while this bug says all eps cannot be shown. This bug is more serious than 62038 and critical. So, I reopen this.
On pc Debian x86-64 with master sources (future 4.3.0) updated 3 days ago, I could reproduce the problem. Testing with gv (ghostview), it indicated that fonts-japanese-mincho.ttf was missing. I installed fonts-hanazono package (which contains this font) and the image appeared. It worked too with 4.1.5.3 LO (package from Debian testing) On which env do you have this problem? Is fonts-japanese-mincho.ttf installed? Thorsten/Caolán: Would it be possible to use a fallback font or something to display the graphic?
Forget it, I had read too quickly and hadn't try the slideshow mode which indeed hasn't displayed the graphic :-(
On Windows 7 sp1, 64-bit with Version 3.6.5.2 (Build ID: 5b93205) Not sure if this is platform dependent, but on Windows this affects Writer, Draw and Impress at least as far back as 3.6.5, probably further. Inserting an EPS image is not rendered into a visible drawing. Only an image frame is laid out, but no visible drawing is rendered as bitmap or vector graphic. To me it looks like the import filter only converts the file metadata, which is what then shows when converted to bitmap in Impress or Draw, or when inserted into Writer.
Reverting version, and removing Windows related handling of EPS which is more completely described in bug 62051. This should probably be closed as duplicate of bug 62038. Sorry for the noise.
closing as duplicate to issues of bug 62038 which is already on MAB 4.2 *** This bug has been marked as a duplicate of bug 62038 ***