To reproduce this problem: In Writer do Insert->Object->Formula. Then type: q w e r t inside formula (with spaces), then click elsewere in document to exit formula editor. Then click Ctrl-Z. Nothing happans. Click Ctrl-Z several times until formula disappears. Then click Ctrl-Y. Formula appears. Then double click formula to enter editor. Press Ctrl-Z. Nothing happens. Undo unavailable. I have reproduced this problem on Linux 32 and 64 and Windows 32 and in OpenOffice.
Reproduced with LO 3.3.1 RC2 Ubuntu 10.04 x86.
[Reproducible] with "LibreOffice 3.3.2 – WIN7 Home Premium (64bit) German UI [OOO330m19 (Build:202 / tag 3.3.2.2)]" This is not a particular "Math in WRITER" effect! Every LibO-OLE object in every application (I additionally tested CALC in DRAW) will loose it's undo stack with deletion of the object. Undo of deletion restores the object, but not it's undo stack. It would be fine if undo stack also would be restored.
[This is an automated message.] This bug was filed before the changes to Bugzilla on 2011-10-16. Thus it started right out as NEW without ever being explicitly confirmed. The bug is changed to state NEEDINFO for this reason. To move this bug from NEEDINFO back to NEW please check if the bug still persists with the 3.5.0 beta1 or beta2 prereleases. Details on how to test the 3.5.0 beta1 can be found at: http://wiki.documentfoundation.org/QA/BugHunting_Session_3.5.0.-1 more detail on this bulk operation: http://nabble.documentfoundation.org/RFC-Operation-Spamzilla-tp3607474p3607474.html
reproduced on LibO 3.5.0 beta 1
<http://wiki.documentfoundation.org/BugReport_Details#Version> @Michal: Please feel free to reassign (or reset Assignee to default) if it’s not your area or if provided information is not sufficient. Please set Status to ASSIGNED if you accept this Bug.
Please read this message in its entirety before responding. Your bug was confirmed at least 1 year ago and has not had any activity on it for over a year. Your bug is still set to NEW which means that it is open and confirmed. It would be nice to have the bug confirmed on a newer version than the version reported in the original report to know that the bug is still present -- sometimes a bug is inadvertently fixed over time and just never closed. If you have time please do the following: 1) Test to see if the bug is still present on a currently supported version of LibreOffice (preferably 4.2 or newer). 2) If it is present please leave a comment telling us what version of LibreOffice and your operating system. 3) If it is NOT present please set the bug to RESOLVED-WORKSFORME and leave a short comment telling us your version and Operating System Please DO NOT 1) Update the version field 2) Reply via email (please reply directly on the bug tracker) 3) Set the bug to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + LibreOffice is powered by a team of volunteers, every bug is confirmed (triaged) by human beings who mostly give their time for free. We invite you to join our triaging by checking out this link: https://wiki.documentfoundation.org/QA/BugTriage There are also other ways to get involved including with marketing, UX, documentation, and of course developing - http://www.libreoffice.org/get-help/mailing-lists/. Lastly, good bug reports help tremendously in making the process go smoother, please always provide reproducible steps (even if it seems easy) and attach any and all relevant material
Setting Assignee back to default. Please assign it back to yourself if you're still working on this issue