Bug 132907 - Formatting lost when pressing redo in a specific setup
Summary: Formatting lost when pressing redo in a specific setup
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
(earliest affected) release
Hardware: All All
: low minor
Assignee: Not Assigned
Keywords: bibisected, bisected, regression
: 137324 (view as bug list)
Depends on:
Blocks: Undo-Redo Formatting-Text-Diverse
  Show dependency treegraph
Reported: 2020-05-10 09:41 UTC by Telesto
Modified: 2024-02-09 03:13 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Note You need to log in before you can comment on or make changes to this bug.
Description Telesto 2020-05-10 09:41:04 UTC
Formatting lost after redo

Steps to Reproduce:
1. Open Writer
2. Type: AAA
4. Type: BBB
5. undo the BBB
6. Redo BBB -> BBB has no bold

Actual Results:
No bold

Expected Results:

Reproducible: Always

User Profile Reset: No

Additional Info:
Found in
Version: (x64)
Build ID: 97a2c1fc5e376c0c00968f17a0392c6d3a5ed565
CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: Skia/Raster; VCL: win; 
Locale: nl-NL (nl_NL); UI-Language: en-US
Calc: threaded

and in

and in

but not in
Build ID: 3215f89-f603614-ab984f2-7348103-1225a5b
Comment 1 Xisco Faulí 2020-05-11 10:09:13 UTC
Reproduced in

Build ID: 86bc13248c1d9f63b10aac304bdf0361d1dcc47f
CPU threads: 4; OS: Linux 4.19; UI render: default; VCL: gtk3; 
Locale: en-US (en_US.UTF-8); UI: en-US
Calc: threaded
Comment 2 Buovjaga 2020-06-10 11:18:32 UTC
Bibisected with Linux 42max repo to https://git.libreoffice.org/core/+/e012f326c1c32c053304998a6826cb322f2c7728%5E!/
sw: implement proper Undo for SwDoc::UpdateRsid

Adding Cc: to Michael Stahl
Comment 3 Telesto 2020-08-04 14:58:14 UTC
It's working properly when pressing CTRL+Z twice. So with following steps
1. Open Writer
2. Type: AAA
4. Type: BBB
Comment 4 Telesto 2020-10-08 15:48:17 UTC
*** Bug 137324 has been marked as a duplicate of this bug. ***
Comment 5 QA Administrators 2024-02-09 03:13:31 UTC
Dear Telesto,

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