Bug 140368 - LibreOffice Writer doesn't point to last changed line
Summary: LibreOffice Writer doesn't point to last changed line
Status: RESOLVED DUPLICATE of bug 140147
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
7.1.0.3 release
Hardware: x86-64 (AMD64) All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-02-12 09:55 UTC by Giovanni
Modified: 2023-02-05 09:05 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Giovanni 2021-02-12 09:55:41 UTC
Description:
Till when I saved ODT files with LibreOffice Writer 7.0.4.2 I had no problem.

I write a file, I change it, than save. Open again the changed file and Writer moves the cursor onto the last saved change I made the last time.

I do the same with Writer 7.1.0.3 and the cursor move somewhere but not onto my last changed line saved the previous time. So I save the file with this new version of Writer but the problem doesn't disappear. I had to move back to LibreOffice 7.0.4.2 and everything worked again.

This happens with Linux but also on Mac. In the same exactly way.

Steps to Reproduce:
1. Create an ODT file with Writer 7.0.4.2 and save it
2. Remember the last word you changed into the file and close it
3. Open it with Writer 7.1.0.3
4. The cursor doesn't points to the last changed word

Actual Results:
The cursor doesn't move onto the last changed line

Expected Results:
The cursor move onto the last changed line with the previous saved work


Reproducible: Always


User Profile Reset: No



Additional Info:
The software worked correctly till version 7.0.4.2
Comment 1 BogdanB 2021-02-12 10:15:35 UTC

*** This bug has been marked as a duplicate of bug 140147 ***
Comment 2 Aron Budea 2023-02-04 19:39:38 UTC

*** This bug has been marked as a duplicate of bug 141586 ***
Comment 3 Aron Budea 2023-02-05 09:05:07 UTC

*** This bug has been marked as a duplicate of bug 140147 ***