Bug 65696 - Visio drawing corrupted when opened in draw
Summary: Visio drawing corrupted when opened in draw
Status: RESOLVED INVALID
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Draw (show other bugs)
Version:
(earliest affected)
4.1.0.0.beta2
Hardware: Other Mac OS X (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard: infoprovider:steve_w@exemail.com.au
Keywords:
Depends on:
Blocks:
 
Reported: 2013-06-13 05:19 UTC by Stephen Wright
Modified: 2014-09-03 12:05 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments
screen shot of problem (605.58 KB, image/tiff)
2013-06-13 05:19 UTC, Stephen Wright
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Stephen Wright 2013-06-13 05:19:14 UTC
Created attachment 80751 [details]
screen shot of problem

I saved a visio drawing on a PC then emailed it home and opened it on my MAC.  The visio drawing was composed of some jpegs and when displayed some of the drawings were corrupted, the corruption was very specific, the left third of the jpeg (approx) was moved to the right side of the drawing.  see attachment for screen shot of the drawing.

can supply original visio file if required
Comment 1 Thomas Hackert 2013-06-20 12:51:58 UTC
Hello Stephen, *,
as I have neither Visio nor some adequate files, it would be nice, if you can attach it to this bug :)
TIA
Thomas.
Comment 2 QA Administrators 2014-08-04 16:17:57 UTC
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 INVALID due to lack of needed information.

For more information about our NEEDINFO policy please read the wiki located here: 
https://wiki.documentfoundation.org/QA/FDO/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
Comment 3 QA Administrators 2014-09-03 12:05:36 UTC
Dear Bug Submitter,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INVALID 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 FDO