Found while fixing bug 141887 (Writer IM crash). STR: 1. Start LO Calc, Impress, Draw or Math (not Writer! Didn't test Base) 2. Activate some IM and type a character, to be in IM pre-selection 3. Undo via shortcut (Ctrl+Z) Expected result: no crash Actual result: crash soffice.bin: svl/source/undo/undo.cxx:679: bool SfxUndoManager::ImplUndo(SfxUndoContext*): Assertion `!"SfxUndoManager::Undo: not possible when within a list action!"' failed. ----- All these modules create an undo entry while still in pre-selection (you can see the enabled undo toolbar button). Writer doesn't do that, so no crash happens. IMHO the other applications shouldn't create the Undo entry based on the pre-selection data, which would prevent the crash.
What's that IM, Jan-Marek?
(In reply to Roman Kuznetsov from comment #1) > What's that IM, Jan-Marek? IM = Input Method, mostly used for non-latin input, especially for complex symbolic languages, like Chinese, Japanese, etc. On Linux the most prominent ones are fcitx and ibus. Also often abbreviated as IME for Input Method Engine / Editor. You normally get an extra window when typing, so the user can prepare the final symbol / input, which is sometimes referred to as the "pre-selection" window. Because it normally uses auto-completion features with multiple suggestions, just like virtual keyboards on a phone (which might actually be a IM to) for faster input.
Jan-Marek, can you still reproduce in recent versions? I gave it a try with a Korean (Hangul) keyboard layout on Ubuntu 20.04 but I can't get a separate dialog for character entry. I could see an issue in Calc where a character was following me when changing cells, and wasn't undoable, but I don't know if it's related. Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: dd15364793401e41bae45cdeb410808c9f94fa93 CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded
Dear Jan-Marek Glogowski, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping
Dear Jan-Marek Glogowski, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-FollowUp