Bug 135118 - Invisible image on wrong page after deleting an image and hiding changes
Summary: Invisible image on wrong page after deleting an image and hiding changes
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
6.2.0.3 release
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: bibisected, bisected, regression
Depends on:
Blocks: Track-Changes-TextFormatting
  Show dependency treegraph
 
Reported: 2020-07-24 20:49 UTC by Telesto
Modified: 2023-05-13 19:12 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:


Attachments
Example file (3.03 MB, application/vnd.oasis.opendocument.text)
2020-07-24 20:49 UTC, Telesto
Details
Screencast (3.24 MB, video/mp4)
2020-07-24 20:50 UTC, Telesto
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Telesto 2020-07-24 20:49:14 UTC
Description:
Invisible image on wrong page after deleting an image and hiding changes

Steps to Reproduce:
1. Open the attached file
2. Go to page 45
3. Delete image 16 (not the frame/image)
4. Edit -> Track Changes -> Show -> Disable
5. Scroll down to image 17 and try to click it (Another image will be selected)

Actual Results:
Image at wrong positon

Expected Results:
Not so


Reproducible: Always


User Profile Reset: No



Additional Info:
Version: 7.1.0.0.alpha0+ (x64)
Build ID: <buildversion>
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-07-24 20:49:34 UTC
Created attachment 163494 [details]
Example file
Comment 2 Telesto 2020-07-24 20:50:21 UTC
Created attachment 163495 [details]
Screencast
Comment 3 Telesto 2020-07-24 20:54:09 UTC
Found in
Version: 6.2.4.0.0+
Build ID: 915ec0b5f5ce9a2da6a51f5278ea4faaffa19839
CPU threads: 4; OS: Windows 6.3; UI render: default; VCL: win; 
Locale: nl-NL (nl_NL); UI-Language: en-US
Calc: CL

not in
Version: 6.1.0.0.alpha0+
Build ID: 77ef84ef7251004e0c581174929a1eb551112ec3
CPU threads: 4; OS: Windows 6.3; UI render: default; 
Locale: nl-NL (nl_NL); Calc: CL
Comment 4 Attila Baraksó (NISZ) 2020-10-25 10:07:56 UTC Comment hidden (obsolete)
Comment 5 Attila Baraksó (NISZ) 2020-10-25 10:16:46 UTC
After I tried to click top of the image 17, I reproduced in:

Version: 7.1.0.0.alpha0+
Build ID: f1d798151048dde3f48b124ef406416668d1e9c5
CPU threads: 6; OS: Linux 5.4; UI render: default; VCL: gtk3
Locale: hu-HU (hu_HU.UTF-8); UI: en-US
Calc: threaded
Comment 6 Attila Baraksó (NISZ) 2020-11-08 09:13:07 UTC
Bibisected using linux-64-6.3 to:
URL: https://cgit.freedesktop.org/libreoffice/core/commit/?id=b3265d6e11200a55a068902e2d78c2de374e973b
author: László Németh <nemeth@numbertext.org>
committer: László Németh <nemeth@numbertext.org>
summary: tdf#123054 track changes: fix paragraph style regression
Comment 7 Attila Baraksó (NISZ) 2020-11-08 09:14:08 UTC
Adding Cc: László Németh
Comment 8 QA Administrators 2022-11-09 04:03:08 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