Bug 141024 - Last position not saved in Writer document with 7.1 (portable)
Summary: Last position not saved in Writer document with 7.1 (portable)
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: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-03-14 16:01 UTC by Hagar Delest
Modified: 2023-02-05 09:04 UTC (History)
1 user (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 Hagar Delest 2021-03-14 16:01:15 UTC
Description:
From LO 7.1 (portable), the cursor last position is not saved. The documents open at first page.
User data is correctly filled in with first name last name and initials.
First experienced with 7.1.0.3 portable, still an issue with 7.1.1 portable.
No problem with 7.0.4.2 portable.

Additional information :
7.1.0.3 portable version tested from portableapps
7.1.1 portable version tested from winpenpack
Both on Windows 10.

Steps to Reproduce:
1. Create a new user profile
2. Fill in name in Tools > Options > LibreOffice > User Data
3. Create a document with several pages
4. Place the cursor in any place but first page and save, close LO
5. Open LO

Actual Results:
The document opens at first page.

Expected Results:
The last cursor position should have been saved.


Reproducible: Always


User Profile Reset: Yes



Additional Info:
The document should open at the last cursor position.
Comment 1 [REDACTED] 2021-03-15 16:20:35 UTC
Sounds like a duplicate of tdf#140147.
Comment 2 Hagar Delest 2021-03-16 20:18:04 UTC
Indeed. Could not find that report. I guess it was because I used "last" in keywords.
Comment 3 Hagar Delest 2021-03-16 20:19:35 UTC

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

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

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