Hi @ll, I hope, I have chosen the right (sub)component for this bug. If not, feel free to change it accordingly ... ;) I stumbled upon the following: 1. Open Calc 2. Enter "1" in cell A1 3. Press "Enter" 4. Press <Ctrl>+<Z> a couple of times 5. Press <Ctrl>+<W> The content of A1 will be removed, but the "Save" button stays active, although there are no changes any longer ins this file ... :( If you press <Ctrl>+<W>, the "Save document" window opens, which - I think - is a bug ... :( LO: Version: 4.1.2.3 Build ID: 40b2d7fde7e8d2d7bc5a449dc65df4d08a7dd38 OS: Debian Testing AMD64 Additional: I have not enabled "Tools – Options – General – Allow to save document even when the document is not modified" ... ;) If you need further information, feel free to ask :) Sorry for the inconvenience Thomas.
I can confirm this bug also under Windows XP x86 This also occurs if, on an existing spreadsheet, you type a value on any cell and then press Enter. It seems that pressing Enter on a non-empty cell triggers the Save action so even if you Undo all modifications since last save it will still ask the user to save the document. See discussion in QA http://nabble.documentfoundation.org/Libreoffice-qa-Ctrl-Z-seem-not-to-lead-to-an-unchanged-document-in-Calc-tp4075697.html
Hello Pedro, *, (In reply to comment #1) > I can confirm this bug also under Windows XP x86 thank you very much :) As you have confirmed it with Win XP, I changed "Platform" to "All" and "All" ... ;) Have a nice evening Thomas.
*** Bug 71053 has been marked as a duplicate of this bug. ***
Hello @ll, this bug is still valid with LO Version: 4.2.2.1 Build-ID: 3be8cda0bddd8e430d8cda1ebfd581265cca5a0f with installed Germanophone lang- as well as helppack on Debian Testing i386 ... :( It would be nice, if one of the devs / other QA guys and gals can have a look at it again ... ;) Sorry for the inconvenience Thomas.
*** Bug 84196 has been marked as a duplicate of this bug. ***
** 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
Hello QA Administrators, *, (In reply to QA Administrators from comment #6) <snip> > 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 thanks for reminding me about my bug :) I tested it with LO Version: 5.0.2.2 Build-ID: 00m0(Build:2) Gebietsschema: de-DE (de_DE.UTF-8) as well as with Version: 5.0.2.1 Build-ID: 9a18d52abbdfbdc2ac9acebec2b92e7859eb73b7 Gebietsschema: de-DE (de_DE.UTF-8) on Debian Testing AMD64. With both versions, this bug is still reproducible with both versions, sorry ... :( Have a nice evening Thomas.
** 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-20161108
Hello *, (In reply to QA Administrators from comment #8) <snip> > 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/ I can still confirm this bug with OS: Debian Testing AMD64 LO: Version: 5.1.6.1 Build-ID: f3e25ec0581f5012f54d8810dcddd5824f4ee374 CPU-Threads: 4; BS-Version: Linux 4.5; UI-Render: Standard; Gebietsschema: de-DE (de_DE.UTF-8); Calc: group , LO: Version: 5.1.7.0.0+ Build-ID: dea5ac15555ce2cbc8866f0511ed9d26156c9928 CPU-Threads: 4; BS-Version: Linux 4.5; UI-Render: Standard; TinderBox: Linux-rpm_deb-x86_64@70-TDF, Branch:libreoffice-5-1, Time: 2016-10-18_08:07:57 Gebietsschema: de-DE (de_DE.UTF-8); Calc: group , LO: Version: 5.2.3.3 Build-ID: d54a8868f08a7b39642414cf2c8ef2f228f780cf CPU-Threads: 4; BS-Version: Linux 4.5; UI-Render: Standard; Gebietsschema: de-DE (de_DE.UTF-8); Calc: group and LO: Version: 5.3.0.0.alpha1 Build-ID: f4ca1573fcf445164c068c1046ab5d084e1b005f CPU-Threads: 4; BS-Version: Linux 4.5; UI-Render: Standard; VCL: gtk2; Gebietsschema: de-DE (de_DE.UTF-8); Calc: group ... :( HTH Thomas.
** 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
Hello @ll, thanks for the reminder :) (In reply to QA Administrators from comment #10) <snip> > 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. Still reporoducible on OS: Debian Testing x86 LO: Version: 5.4.2.2.0+ Build-ID: 1:5.4.2-3 CPU-Threads: 2; Betriebssystem:Linux 4.13; UI-Render: Standard; VCL: x11; Gebietsschema: de-DE (de_DE.UTF-8); Calc: group (Debian's own version), LO: Version: 5.4.4.0.0+ Build-ID: 0958cd79545a21a37642f812937d57164117bffe CPU-Threads: 2; Betriebssystem:Linux 4.13; UI-Render: Standard; VCL: kde4; TinderBox: Linux-rpm_deb-x86@71-TDF, Branch:libreoffice-5-4, Time: 2017-11-11_02:06:59 Gebietsschema: de-DE (de_DE.UTF-8); Calc: group and LO: Version: 6.0.0.0.alpha1+ Build-ID: 7df058224a7cabb1cbfc8564ffe22a6844fb2a1f CPU-Threads: 2; Betriebssystem:Linux 4.13; UI-Render: Standard; VCL: kde4; TinderBox: Linux-rpm_deb-x86@71-TDF, Branch:master, Time: 2017-11-10_22:47:47 Gebietsschema: de-DE (de_DE.UTF-8); Calc: group (the last two parallel installed, following the instructions from https://wiki.documentfoundation.org/Installing_in_parallel/Linux), sorry ... :( Have a nice evening Thomas.
Dear Thomas Hackert, 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
Hello @ll, (In reply to QA Administrators from comment #12) <snip> > Test to see if the bug is still present with the latest version of > LibreOffice from https://www.libreoffice.org/download/ this bug is still reproducible with LO: Version: 6.2.7.1 Build-ID: 1:6.2.7-0ubuntu0.19.04.1 CPU-Threads: 4; BS: Linux 5.0; UI-Render: Standard; VCL: kde5; Gebietsschema: de-DE (de_DE.UTF-8); UI-Sprache: de-DE Calc: threaded and Version: 6.4.0.0.alpha0+ Build-ID: b2d8093b19642038631dfb8f1ab6745a380a652c CPU-Threads: 4; BS: Linux 5.0; UI-Render: Standard; VCL: kf5; TinderBox: Linux-rpm_deb-x86_64@86-TDF, Branch:master, Time: 2019-09-24_02:42:42 Gebietsschema: de-DE (de_DE.UTF-8); UI-Sprache: de-DE Calc: threaded on Kubuntu 19.04 with KDE/Plasma 5.15.4 ... :( Have a nice day Thomas.
*** Bug 132163 has been marked as a duplicate of this bug. ***
Dear Thomas Hackert, 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
Hello @ll, (In reply to QA Administrators from comment #15) > 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. this bug is still reproducible in Debian Testing AMD64 with: Version: 7.3.4.2 / LibreOffice Community Build ID: 30(Build:2) CPU threads: 4; OS: Linux 5.18; UI render: default; VCL: x11 Locale: de-DE (de_DE.UTF-8); UI: de-DE Debian package version: 1:7.3.4~rc2-1 Calc: threaded (Debian's installed version) Version: 7.3.4.2 / LibreOffice Community Build ID: 728fec16bd5f605073805c3c9e7c4212a0120dc5 CPU threads: 4; OS: Linux 5.18; UI render: default; VCL: kf5 (cairo+xcb) Locale: de-DE (de_DE.UTF-8); UI: de-DE Calc: threaded and Version: 7.5.0.0.alpha0+ / LibreOffice Community Build ID: 39ffe421047e69554e601cedf0fde931ccc18ca7 CPU threads: 4; OS: Linux 5.18; UI render: default; VCL: kf5 (cairo+xcb) Locale: de-DE (de_DE.UTF-8); UI: de-DE Calc: threaded Have a nice day Thomas.
*** Bug 86821 has been marked as a duplicate of this bug. ***
Reproduced in OOo 3.3, so inherited. Tested with both adding datat to a cell or formatting an existing cell. Writer not affected (except for comments, see bug 155292). Equivalent for Draw and Impress is bug 93519.