https://issues.apache.org/ooo/show_bug.cgi?id=122475

Arto Suominen <[email protected]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[email protected]
                   |                            |e

--- Comment #7 from Arto Suominen <[email protected]> ---
I was able to reproduce this. The cause may be different from the original
report, but the error message is indeed the same. 

Looking at the screenshot attached to the original report, I saw that there
were already several slides and images in the presentation. That led me to the
conclusion that a particular image might be causing the error. I may be wrong
in this assumption, but I believe it is worth considering to be the cause.

It would help immensely if the original reporter would attached the .jpg he
used.
If that file indeed is corrupt, this issue should be considered a lower
priority.

I Tested on Windows 8 Pro, OpenOffice 3.4.1 (AOO341m1(Build:9593) – Rev.
1372282).

I used a corrupted .jpg file which I had made by editing a .jpg in Wordpad. I
have attached the file I used, and listed here are the steps to replicate the
issue:

1.    Download the attachment, “corrupted_image.jpg”.
2.    Create a new presentation, either by using the wizard or
[File]->[New]->[Presentation].
3.    From the top menu, click [Insert]->[Picture]->[From File…].
4.    Select the file mentioned in step 1, and click “Open”.
    -Alternatively, you can copy-paste the image into the presentation, or use
other ways of inserting.

I believe all corrupted image files will get the same result. I verified this
by also corrupting other images, large and small.
To create a corrupted image, you can follow these steps:

1.    Download a .jpg file, or use an existing one on your computer.
2.    Open the file in Wordpad or another text editor.
3.    Remove a few lines of text from the contents.
4.    Save the file.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.

Reply via email to