Created attachment 68252 [details] Screenshots of Different Scenario Values When creating "Scenarios" in CALC, some of the scenarios, hold the same values, despite the fact that they were created with different values. The enclosed screen shots demonstrate the problem. Regards KS
Checked with: LO 4.0.2.2 Build ID: own W7 debug build Windows 7 Professional SP1 64 bit In general I couldn't get this feature to work properly. Changed values in cells C8 and D5. 1st try: Two scenarios created - the cell scenario selector didn't work (neither in Navigator). With three scenarios it started to work but displayed wrong values - 1st one with values of 2nd, 2nd and 3rd with values of 2nd. The same happened when I changed scenarios in Navigator. More over when deleted 3rd scenario - the app crashed. 2nd try: Three scenarios created - displayed values were different. 1st scenario displayed values of 3rd, 2nd of 2nd, and 3rd of 3rd. If you deleted 3rd scenario - the app crashed again. This is reproducible. BT will follow.
Created attachment 78778 [details] Bug 55762 - WinDbg session Attached full WinDbg session.
NEW as bug confirmed and bt attached.
Hi there, The issue seems to disappear when you deselect the following option : □ Copy back when creating a new scenario. I'm using the following version of LO Writer : 4.3.5.2, in French. O/S : Windows 8.1. If you need anything else from me, please ask.
** 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.5 or 5.1.0) 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: 2016-02-21
** 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.2.5 or 5.3.0 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-20170306
Same error LibreOffice 5.3.1.2 Sama eraro, mismo error. English is discriminatory, better Esperanto.
** 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
I have tested this with Linux version 6.0.3.2 and confirm that the scenarios are changing correctly when selected. Thanks very much for fixing this.
English from Google Translate: The problem is a bad explanation in the help and a bad choice of the options activated by default. By default the option [v] Copy back is selected, in the help in Spanish this option is translated as "Copy back", "Copy again" and "Copy reverse", which complicates understanding what it does. If the option [v] Copy back or what is the same in English is selected [v] Copy back, then when you have selected a scenario and change the value, the scenario also changes and that is why you have repeated scenarios and not with the values originals What happens then? Well, after adding the first scenario, if you have selected it to test, when changing values to add a second scenario what you are doing is also changing the first scenario that was already active. Likewise, if before creating another scenario, try to choose one of the previously created ones, if it was created with the option [v] Copy back then you are also modifying that scenario, losing its original values and creating another one with repeated values. Solution: learn to deactivate the option [v] Copy back or Copy back first, and if you want to be able to change scenarios, you can change the active options from the navigation box (press F5 or the View menu - Navigator), select the icon with three red-green-blue rectangles and selecting the scenario you want to change you can activate the option [v] Copy back in their properties. So what is the use of the option [v] Prevent modifications? Well this option work with cell protection and sheet protection. Español: El problema es una mala explicación en la ayuda y una mala elección de las opciones activadas por defecto. Por defecto está seleccionada la opción [v] Copiar de vuelta, en la ayuda en español esta opción viene traducida como "Copiar de vuelta", "Copiar de nuevo" y "Copiar reverso", lo cual complica comprender lo que hace. Si está marcada la opción [v] Copiar de vuelta o lo que es igual en inglés [v] Copy back, entonces cuando tienes seleccionado un escenario y cambias el valor, el escenario también cambia y por eso tienes escenarios repetidos y no con los valores originales. ¿Qué ocurre entonces? Pues que tras añadir el primer escenario, si lo has seleccionado para probar, al cambiar valores para añadir un segundo escenario lo que se está haciendo también es cambiar el primer escenario que ya estaba activo. Igualmente si antes de crear otro escenario pruebas a elegir uno de los anteriormente creados, si fue creado con la opción [v] Copiar de vuelta entonces también estás modificando ese escenario, perdiendo sus valores originales y creando otro con valores repetidos. Solución: aprender a desactivar primero la opción [v] Copiar de vuelta o Copy back, y si quieres poder cambiar escenarios pues puedes cambiar las opciones activas desde el cuadro de navegación (pulsa F5 o el menú Ver - Navegador), selecciona el icono con tres rectángulos rojo-verde-azul y seleccionando el escenario que quiere cambiar puedes activar en sus propiedades la opción [v] Copiar de vuelta. ¿Entonces para qué sirve la opción [v] Impedir modificaciones? Pues esta opción trabajar con la protección de celda y la protección de hoja. Esperanto: La problemo estas malbona elekto de la ebloj aktivigitaj defaŭlte. Defaŭlta estas selektita [v] Kopiu reen en la hispana helpo opcio estas tradukita kiel "kopii reen", "kopii denove" kaj "Kopii inversigi", ke komplikas kompreni kion ĝi faras. Se la opcio estas markita [v] Kopiu reen aŭ en la angla [v] Copy back kiam vi elektas sceno kaj vi ŝanĝas valoron, la sceno ankaŭ ŝanĝas kaj tiel ripetas valorojn de la sceno kaj la unua sceno ne havas la originalajn valorojn. Solvo: Lernu kiel malŝalti unua la [v] Kopiu reen aŭ Copy back, kaj se vi volas ŝanĝi scenejoj ĉar vi povas ŝanĝi la aktiva ebloj de la navigado skatolo (klavo F5 aŭ la menuo Vidi - Foliumilo), elektu la piktogramon kun tri koloroj rektanguloj ruĝa-verda-blua kaj elektante la agordon kiun vi volas ŝanĝi. Ĉu kio faras la opcio [v] Malhelpi modifojn? Nu ĉi tiu opcio funkcias kun ĉelo-protekto kaj folia protekto.
Dear KSN, 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
I had tested this earlier also. Please refer my comment: https://bugs.documentfoundation.org/show_bug.cgi?id=55762#c9 I confirm that this is also working in Calc Version 6.3.0.4 Thanks KSN
Dear KSN, 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
Version: 7.2.0.4 / LibreOffice Community Build ID: 9a9c6381e3f7a62afc1329bd359cc48accb6435b CPU threads: 4; OS: Linux 5.4; UI render: default; VCL: gtk3 Locale: es-ES (es_ES.UTF-8); UI: es-ES Calc: threaded Continuing problem: Scenario option [] Copy back is enabled by default. Solution: disable the scenario option [] Copy back by default. Daŭra problemo: Scena opcio [] Kopii reen estas ŝaltita defaŭlte. Solvo: Defaŭlte malŝalti la scenaran opcion [] kopii reen. Problema que sigue: está activada por defecto la opción de escenario [ ] Copiar de vuelta. Solución: desactivar por defecto la opción de escenario [ ] Copiar de vuelta.
Dear KSN, 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