Problem description: Steps to reproduce: 1. make a graph 2. position some text around it 3. select a rectangle containing everything 4. copy 5. goto an odt-document Current behavior: 6. there is no way to paste everything correctly. Not even with paste special. Expected behavior: In Ubuntu 12.04 at least pasting a bitmap did work. Pasting a metafile did not work either. In still earlier version, however, it DID work. Operating System: Ubuntu Version: 4.2.3.3 release
Hi Erik, thanks for reporting. However, it simply works for me _if_ I have at least a full row/column of cells selected around the graph. (testing in 4.2.3.3 and 4.2.4.2 on Ubuntu) Can you pls heck if that is the same in your test? Cheers, Cor
Created attachment 99413 [details] test.odt Hi Cor, I've attached two files. In the file "test.odt" I've described what I have done. Would you please try to repeat it? Erik On 20-05-14 13:36, bugzilla-daemon@freedesktop.org wrote: > Cor Nouws <mailto:cno@nouenoff.nl> changed bug 78955 > <https://bugs.freedesktop.org/show_bug.cgi?id=78955> > What Removed Added > Status UNCONFIRMED NEEDINFO > CC cno@nouenoff.nl > Ever confirmed 1 > > *Comment # 1 <https://bugs.freedesktop.org/show_bug.cgi?id=78955#c1> on > bug 78955 <https://bugs.freedesktop.org/show_bug.cgi?id=78955> from Cor > Nouws <mailto:cno@nouenoff.nl> * > > Hi Erik, > > thanks for reporting. > However, it simply works for me _if_ I have at least a full row/column of cells > selected around the graph. > (testing in 4.2.3.3 and 4.2.4.2 on Ubuntu) > > Can you pls heck if that is the same in your test? > Cheers, > Cor > > ------------------------------------------------------------------------ > You are receiving this mail because: > > * You reported the bug. >
Created attachment 99414 [details] test.ods
(In reply to comment #2) > > Would you please try to repeat it? If you can be so kind to attach the spreadsheet that you mention: of course. By the way: describing a bug is fine here, as comment. Faster to read.
(In reply to comment #4) > If you can be so kind to attach the spreadsheet that you mention: of course. Ah you did. Sorry :) Pasting works neat in 4.3.0.1 and 4.2.5.2 for me. So probably fixed. Can you pls check too? thanks, Cor
So, I tried the same on 4.3.0.0. beta2. !! Select K7:R20 in the spreadsheet, and copy. Then "paste-special GDI metafile" in the write-doc. It does NOT give a nice result! Groetjes, Erik On 22-06-14 16:51, bugzilla-daemon@freedesktop.org wrote: > *Comment # 5 <https://bugs.freedesktop.org/show_bug.cgi?id=78955#c5> on > bug 78955 <https://bugs.freedesktop.org/show_bug.cgi?id=78955> from Cor > Nouws <mailto:cno@nouenoff.nl> * > > (In reply tocomment #4 <show_bug.cgi?id=78955#c4>) > >> If you can be so kind to attach the spreadsheet that you mention: of course. > > Ah you did. Sorry :) > > Pasting works neat in 4.3.0.1 and 4.2.5.2 for me. So probably fixed. Can you > pls check too? > thanks, > Cor > > ------------------------------------------------------------------------ > You are receiving this mail because: > > * You reported the bug. >
(In reply to ErikMAkkerman from comment #6) > So, I tried the same on 4.3.0.0. beta2. > !! Select K7:R20 in the spreadsheet, and copy. > Then "paste-special GDI metafile" in the write-doc. > It does NOT give a nice result! Reproduced. In the chart "lineair" the line gets smashed to the bottom. In "logaritmisch" there is no line. Win 7 64-bit Version: 4.5.0.0.alpha0+ Build ID: 772befa08f02b08da1ab493896a0744bc73781c7 TinderBox: Win-x86@51-TDF, Branch:MASTER, Time: 2014-11-23_22:39:02
clarify summary. Did not check how old the bug is (which version it shows for the first time)
** 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 on a currently supported version of LibreOffice (5.0.4 or later) https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System 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) 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: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for your help! -- The LibreOffice QA Team This NEW Message was generated on: 2015-12-20
** 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 on a currently supported version of LibreOffice (5.1.6 or 5.2.3 https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System 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) 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: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug-20170103
Dear ErikMAkkerman, 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 https://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
Dear ErikMAkkerman, 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 https://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://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug