Bug 133075

Summary: Pressing Enter with anchor to character with a shape at certain spot causes layout loop
Product: LibreOffice Reporter: Telesto <telesto>
Component: WriterAssignee: Not Assigned <libreoffice-bugs>
Status: NEW ---    
Severity: normal CC: buzea.bogdan, himajin100000
Priority: medium    
Version: Inherited From OOo   
Hardware: All   
OS: All   
See Also: https://bugs.documentfoundation.org/show_bug.cgi?id=133104
https://bugs.documentfoundation.org/show_bug.cgi?id=117925
https://bugs.documentfoundation.org/show_bug.cgi?id=133009
Whiteboard:
Crash report or crash signature: Regression By:
Bug Depends on:    
Bug Blocks: 87740, 136524, 113510    
Attachments: Example file

Description Telesto 2020-05-15 20:46:26 UTC 
Description:
Pressing Enter with anchor to character at certain spot causes layout loop

Likely similar to: bug 133009	

Steps to Reproduce:
1. Open the attached file
2. Cut the shape on 3 page 3
4. Select the text "dolor" on page 2 (bold)
5. Press CTRL+V
6. Text shifts, Empty space on page 1 
7. Place the cursor on page 1 after voluptua (green marking)
8. Press Enter
9. Result.. LibreOffice uses 24% CPU/ Shape is blinking LibreOffice uses 24% CPU/ Shape is blinking

Actual Results:
LibreOffice uses 24% CPU/ Shape is blinking

Expected Results:
This shouldn't happen


Reproducible: Always


User Profile Reset: No



Additional Info:
Version: 7.0.0.0.alpha1+ (x64)
Build ID: f9790da286f2d2fa47f1748f8cfa6172c6622ca3
CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: Skia/Raster; VCL: win; 
Locale: nl-NL (nl_NL); UI: en-US
Calc: CL
Comment 1 Telesto 2020-05-15 20:46:40 UTC 
Created attachment 160881 [details]
Example file
Comment 2 BogdanB 2020-05-17 09:35:51 UTC 
Confirm it. Exactly as is described.

Version: 7.0.0.0.alpha1
Build ID: 6a03b2a54143a9bc0c6d4c7f1...
CPU threads: 4; OS: Linux 5.4; UI render: default; VCL: gtk3; 
Locale: ro-RO (ro_RO.UTF-8); UI: en-US
Calc: threaded
Comment 3 Telesto 2020-05-17 18:46:20 UTC 
This is Shape specific (only tested Chart, Frame, Image & Shape)
Comment 4 QA Administrators 2022-08-03 03:30:45 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

MassPing-UntouchedBug