Description: Images copy and pasted in from Visio 2013 using Powerpoint 2013 and then when viewed in Impress show as "fuzzy". Almost as if there were two images (of the same data) slightly offset from each other. When viewed using Powerpoint 2013...images show OK. This happens over multiple .pptx files. Steps to Reproduce: 1. Use Visio to produce block diagrams. 2. Select all in Visio 3. Ctrl/C 4. Switch to Powerpoint and paste the clipboard 5. Save the .pptx file 6. Open in Impress Actual Results: "Fuzzy" images in IOmpress Expected Results: Sharp images! Reproducible: Always User Profile Reset: Yes Additional Info: Profile reset did NOT fix the problem. In fact, various parts of the diagrams vanished. User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:54.0) Gecko/20100101 Firefox/54.0
Please attach an example pptx. Set to NEEDINFO. Change back to UNCONFIRMED after you have provided the document.
Created attachment 134396 [details] Attached 2 dfiles, PPTX and a snip from LO IMpress I use Office on my desktop and LO on my laptop. The PPTX file shows perfectly in Powerpoint 2013. The other file I loaded into LO Impress on the laptop, clipped part of the image and pasted it into Wordpad.
You only attached an RTF file.
Created attachment 134413 [details] Single page PPTX file showing clear image
Reproduced, but only on Windows. Version: 5.4.0.1 (x64) Build ID: 962a9c4e2f56d1dbdd354b1becda28edd471f4f2 CPU threads: 4; OS: Windows 6.19; UI render: default; Locale: fi-FI (fi_FI); Calc: group Version: 6.0.0.0.alpha0+ (x64) Build ID: e0f67add2ec56706ce06a03572535266f21c0303 CPU threads: 4; OS: Windows 6.19; UI render: default; TinderBox: Win-x86_64@42, Branch:master, Time: 2017-06-27_23:04:56 Locale: fi-FI (fi_FI); Calc: group Arch Linux 64-bit, KDE Plasma 5 Version: 6.0.0.0.alpha0+ Build ID: 98befbb26217b0bf3f35354e418a355280c52cfc CPU threads: 8; OS: Linux 4.11; UI render: default; VCL: kde4; Locale: fi-FI (fi_FI.UTF-8); Calc: group Built on June 29th 2017
Any word on a possible fix for this issue? Thanks, Kevin
(In reply to Kevin Evans from comment #6) > Any word on a possible fix for this issue? That's not what the needinfo status is for: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO Yet, now I did more testing and noticed it is imported correctly in version 3.5, so this is a regression. Sadly, we don't have bibisect repositories for versions earlier than 4.3. Already bad in Version: 4.3.0.0.beta1 Build ID: b7cfa1eab1cb1e94f71d6df6612b73f231d0bf92
Apologies for using the NEEDINFO incorrectly. I installed V5.3.6.1 yesterday on my laptop and noticed that the bug was still there, hence the question. Regards, Kevin
So, will there ever be a fix for this issue? Kevin
So, will there ever be a fix for this issue. I have meetings in DC next week. Therefore, I will download Open Office and see if a similar problem exists with it. I may have to switch to OO. Regards, Kevin
(In reply to Kevin Evans from comment #10) > So, will there ever be a fix for this issue. I have meetings in DC next > week. Therefore, I will download Open Office and see if a similar problem > exists with it. I may have to switch to OO. You could also use Linux, where this problem does not exist.
You cannot be serious? Or maybe you can.....switching to Linux to avoid an application bug? Doesn't matter anymore I uninstalled LO and bought a copy of Office for the laptop...which does work. Kevin
(In reply to Kevin Evans from comment #12) > You cannot be serious? Or maybe you can.....switching to Linux to avoid an > application bug? You don't have to switch. Virtual machines work as well.
I am a retired software developer. I certainly don't want to get into VMs or other OS installations etc, etc. Just needed a piece of software that worked for me. Kevin
** 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 with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. 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) from 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: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Sorry, but this has been over 18 months since I reported this. As mentioned in an earlier comment...I uninstalled LO and purchased Office to use instead. It works fine. I could NOT keep going out to customers with graphics that were NOT readable. So, I don't have LO installed or the inclination to go and get it again just to test this bug that had zero action for a long time.
(In reply to Kevin Evans from comment #16) > Sorry, but this has been over 18 months since I reported this. As mentioned > in an earlier comment...I uninstalled LO and purchased Office to use > instead. It works fine. I could NOT keep going out to customers with > graphics that were NOT readable. > > So, I don't have LO installed or the inclination to go and get it again just > to test this bug that had zero action for a long time. I have good news for you: the bug is gone in LibreOffice 6.2.0 on Windows!