Problem description: Using LO3.5.0RC2 and RC3 the undo function make mistakes or doesn't work correctly. Steps to reproduce: 1. Start a new presentation 2. In the default first page click into the "Click to add text" (not the title) 3. enter the following: 123<press enter>abc 4. check the undo/redo icons in icon bar: undo is inactive 5. press Ctrl+Z: not the letter "c" but the <enter> is undoed. 6. press Ctrl+Z again: nothing happens, no more undo. Current behavior: It seems only some caracter pressing can be undoed. Undo icon is inactive sometimes, when Ctrl+Z does something. Expected behavior: Undo should work as ususal. Platform (if different from the browser): Browser: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:10.0) Gecko/20100101 Firefox/10.0
[Reproducible] with "LibreOffice 3.5.0 RC3 German UI/Locale [Build-ID: 7e68ba2-a744ebf-1f241b7-c506db1-7d53735] on German WIN7 Home Premium (64bit) Also [Reproducible] with - "LibreOffice 3.4.5 German UI [Build ID: OOO340m1 (Build:502)]" parallel Server installation on German WIN7 Home Premium (64bit) - 3.4.1 based RC Same problem with <control+z> and menu 'Edit -> Undo' Worked fine with 3.3.0 portable, so reporter's Version info might be erroneous? Related to "Bug 40165 - [EDITING] Undo retains overwriting text"? For the "Undo Icon inactive" problem we have "Bug 36138 - EDITING: UNDO button inactive also in DRAW" I see the same problem with simple DRAW Text Box, so DRQW might be a more appropriate Component
I intended to set the version to 3.5.0RC2, not 3.3.0RC2, sorry for the mistake. You are right, this bug is similar to Bug 40165 and Bug 36138.
Reproducible with LibreOffice 3.4.3 on Win XP Pro SP3
Some more interesting information: Reproducible with LibreOffice 3.5.1 on Win XP Pro SP3
Reproducible with Libre office 3.5.2.2 on Mac OS 10.7 .3. I got numerous instances of unexpected undo behavior - first noticed that the first key press afte window gains key status dies doesn't seem to get saved; further key presses were saved or lost in a seemingly random order..
*** This bug has been marked as a duplicate of bug 37405 ***