Created attachment 97246 [details] example of chart copying When copying a range of cells, objects within that range - such as charts - are copied as well. In Windows, this copies not just LibreOffice data but also bitmap data which can be pasted in most graphics programs. This is useful mostly when wanting to quickly copy/paste overlapping charts, as the standard 'Export as Image...' only applies to a single chart, and alternative means (screenshots, printing to a bitmap printer, etc.) are cumbersome as well and have their own issues (e.g. copying a selected chart directly copies it without any anti-aliasing). Unfortunately, something appears to have broken here recently. Repro steps: 1. Create a simple table, e.g. Thing | Amount A | 1 B | 2 C | 3 D | 4 2. Create a chart for that table. A pie chart will do. This should appear as a standard pie chart with green, yellow, orange and blue sections. 3. select the cells that contain the chart. 4. copy the selection to clipboard 5. paste into a graphics program The pie chart itself is not visible, while the legend shows completely different colors (irfanview) or the correct colors (mspaint - but still no actual chart), or fails to paste entirely (GIMP). Example image attached. Potentially related: Bug 60443, Bug 61405 - though those deal in part with pasting into LibreOffice documents.
I can not confirm with LO 4.3.2.2 (ID build: edfb5295ba211bd31ad47d0bad0118690f76407d), Windows 7. Copy paste chart to mspaint is correct.
Thanks for the reminder to check this. 4.3.2.2 (edfb5295ba211bd31ad47d0bad0118690f76407d), can still confirm actual chart is missing here - only the legend (minus text) pastes. But at least the odd color issue disappeared (not being able to paste in Gimp shifted to happening when copying the chart object itself - will open a different bug report if required). ----- I decided to check out the clipboard data, just in case Gimp et al were being silly, using: http://www.nirsoft.net/utils/inside_clipboard.html When copying cells with chart, I get output on several seemingly graphics-related clipboard streams: CF_DIB: Mostly FF values, coinciding with the white of the chart. PNG: Saved as binary, shows no chart. Windows Bitmap: Mostly FF values (saved as binary, shows no chart) GDIMetaFile: Unsure - apparently one of the few formats irfanview will not open or recognize. ----- Some additional info: O/S: Windows 8 - Other charts elements do appear to copy (title, subtitle, axes labels, axes, major/minor grid). - In most chart types, the legend's text does appear. - In the 'net' type of chart, the net title does not appear. - In a pie chart (any subtype), if I change the legend to appear at the top/bottom and make some of the label data longer, the legend's color squares get further apart to make room for the text. However, in the pasted version, they are all spaced closely together (i.e. as if the chart is re-generated for the clipboard specifically, and has the text (and pie slices) missing entirely). Any other things I could try / information I could provide?
I can not confirm with LO 4.3.2.2 (ID build: edfb5295ba211bd31ad47d0bad0118690f76407d), Windows 7 64bit. Copy paste chart to mspaint is correct. But I can confirm with LO 4.3.2.2 portable (portableapps.com), windows 7 32bit Copy paste chart to mspaint is incorrect - no chart. I can confirm with Version: 4.4.0.0.alpha0+ Build ID: ced24ffba2fa1754c466b7944b0ee06d21292706 TinderBox: Linux-rpm_deb-x86_64@46-TDF, Branch:master, Time: 2014-10-04_21:31:09 Copy paste chart to gimp is incorrect - no chart. I can not confirm with LO 4.2.6.3, Linux Copy paste chart to gimp is correct. Setting as NEW.
Glad you could confirm! I figured I should check if this issue also happens in AOO - it doesn't. That led me to checking out bug fix lists, and it looks like this bug from AOO is relevant: https://issues.apache.org/ooo/show_bug.cgi?id=118840 I can also confirm what is mentioned in there - renaming the sheet that the graph is on to anything other than "Sheet1" appears to cause the bug to be avoided. We never rename it, as the first sheet is designated our 'scratch pad' sheet. At least that's a work-around. If you feel that this new information should lower the Importance, you'd get no complaint out of me :)
** 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.1 or preferably 5.0.2.2 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 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 your help! -- The LibreOffice QA Team This NEW Message was generated on: 2015-10-14
LibreOffice Version: 5.0.3.2 Build ID: e5f16313668ac592c1bfb310f4390624e3dbfb75 Locale: en-US (en_US) OS: Windows Version: 8, 64-bit Bug still present. Renaming the sheet still a workaround.
** 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
LibreOffice Version: 5.2.4.2 Build ID: 3d5603e1122f0f102b62521720ab13a38a4e0eb0 CPU Threads: 8; OS Version: Windows 6.2; UI Render: default; Locale: en-US (en_US); Calc: group OS: Windows Version: 8, 64-bit Bug still present. Renaming the sheet still a workaround.
** 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
Dear panoworks, 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
I cannot confirm this ever worked (not marked regression anyway) but I reproduce in Lo 7.1+ with rename workaround.
Dear panoworks, 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
Tested on recent master build: Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 2ae9eb8be8d7eb9c3a72953a295d128b45639ea3 CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded When pasting a cell range that contains the chart into Gimp, I lose only the legend text. Using the linux-64-releases bibisect repo - OOo 3.3 to LO 3.6: worked as expected. - 4.0 to 7.4.0.0 alpha: chart missing, legend text missing (had to skip 4.0 betas 1 and 2, but 4.0.0.1 is bad) - 7.4.0.0 beta1 to 24.2: only legend text missing The partial fix in 7.4 is 964e2eaae9d32df201574e6f083acc630fed2f1d for bug 142635 (checked with linux-64-7.4 bibisect repo) - thanks Mike for that improvement! However, we're still missing some legend labels. I can also confirm the sheet-renaming workaround: the copy-paste works fine then!
Created attachment 189398 [details] test ODS Sample ODS I used for the bibisections above. Copy the pink range of cells.
*** This bug has been marked as a duplicate of bug 99969 ***
Verified that it indeed pastes the full chart with its labels into GIMP 2.10.36 and Inkscape 1.3.1 when copied from: Version: 24.8.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 709866a3b8e073fab4937dcf91dcd33ff1d2bc13 CPU threads: 8; OS: Linux 6.5; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: CL threaded Thanks Mike!