Created attachment 123921 [details] test file with basic conditional format Description: conditional formatting lost after paste special as bitmap Steps: 1) Create a sheet with conditional format (or open the attached file) 2) Copy the formatted area 3) Paste special as bitmap (using the paste special dropdown list on the toolbar) Expected: The area is pasted as bitmap with all the styles Current: The area is pasted as bitmap but the conditional format is lost Verified on: Version: 5.0.5.2 Build ID: 55b006a02d247b5f7215fc6ea0fde844b30035b3 Locale: it-IT (it_IT.UTF-8) OS: openSUSE Tumbleweed (20160117) (x86_64) Version: 5.1.0.3 Build ID: 10m0(Build:3) CPU Threads: 4; OS Version: Linux 4.4; UI Render: default; Locale: it-IT (it_IT.UTF-8) OS: openSUSE Tumbleweed (20160117) (x86_64)
Verified on: Version: 4.4.7.2 Build ID: f3153a8b245191196a4b6b9abd1d0da16eead600 locale: it_IT.UTF-8 OS: openSUSE Tumbleweed (20160117) (x86_64) --> changed Version to 4.4.7.2
Verified on: Version 3.6.7.2 (Build ID: e183d5b) Locale: it-IT (it_IT.UTF-8) OS: openSUSE Tumbleweed (20160117) (x86_64) Version 3.5.7.2 Build ID: 3215f89-f603614-ab984f2-7348103-1225a5b Locale: it-IT (it_IT.UTF-8) OS: openSUSE Tumbleweed (20160117) (x86_64)
Reproducible: Win10x64 Version: 5.1.2.1 (x64) Build ID: 2603b69c5ec5981bb5f053f8ebfd1f3de00a4c29 CPU Threads: 1; OS Version: Windows 6.19; UI Render: GL;
Seems to work in master. Please close as WORKSFORME if that is the case for you as well. Otherwise we need more information.
Sorry @Markus, not for me with (clean profile): Version: 5.4.0.0.alpha0+ Build ID: cfd5f4158bd7bfc5714e9bf23b7a71b2d769a644 CPU threads: 4; OS: Windows 6.2; UI render: GL; TinderBox: Win-x86@62-TDF, Branch:MASTER, Time: 2017-04-11_20:19:26 Locale: es-ES (es_ES); Calc: CL Could be some option producing the issue?
Repro on: Versione: 5.4.0.0.beta2 Build ID: 3cc1cdd8ee50f144e5514da51800a08119754d8f CPU threads: 4; OS: Windows 6.1; UI render: predefinito; Versione locale: it-IT (it_IT); Calc: group OS: Win 7 Home Premium SP1 Version: 6.0.0.0.alpha0+ Build ID: c50ae538a6656889c68c43bd9fe0347c61c82aa5 CPU threads: 4; OS: Windows 6.1; UI render: default; TinderBox: Win-x86@42, Branch:master, Time: 2017-06-18_23:58:50 Locale: it-IT (it_IT); Calc: group OS: Win 7 Home Premium SP1 New useful infos. I notice that the issue occurrs with some conditional formatting with formulas as conditions. try to reproduce directly with the attachment 123921 [details]. The formulas are applied on range A2:B6 Condition 1: MOD(ROW(A2);2)=1 Condition 2: MOD(ROW(A2);2)=0
Confirmed in - Version: 6.0.0.0.alpha0+ Build ID: 9e4502f0e393d2bc2810488b3ebb0a5c23038436 CPU threads: 1; OS: Windows 6.1; UI render: default; TinderBox: Win-x86@42, Branch:master, Time: 2017-06-16_08:52:00 Locale: es-ES (es_ES); Calc: group - Version: 6.0.0.0.alpha0+ Build ID: 08f6f9dded1b142b858c455da03319abac691655 CPU Threads: 4; OS Version: Linux 4.8; UI Render: default; VCL: gtk2; Locale: ca-ES (ca_ES.UTF-8); Calc: group - Version: 4.3.0.0.alpha1+ Build ID: c15927f20d4727c3b8de68497b6949e72f9e6e9e - Version 4.1.0.0.alpha0+ (Build ID: efca6f15609322f62a35619619a6d5fe5c9bd5a) - LibreOffice 3.3.0 OOO330m19 (Build:6) tag libreoffice-3.3.0.4
** 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
Repro with: Versione: 6.2.0.1 (x64) Build ID: 0412ee99e862f384c1106d0841a950c4cfaa9df1 Thread CPU: 4; SO: Windows 10.0; Resa interfaccia: GL; VCL: win; Versione locale: de-DE (en_US); UI-Language: it-IT Calc: threaded
Dear Marina Latini (CIB), 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
*** Bug 143069 has been marked as a duplicate of this bug. ***
Dear Marina Latini (SUSE), 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