Bug 150266 - Program does not continue where it left off.
Summary: Program does not continue where it left off.
Status: RESOLVED INSUFFICIENTDATA
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
7.3.5.2 release
Hardware: x86-64 (AMD64) Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-08-04 15:19 UTC by holtecaydi
Modified: 2023-03-09 03:26 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 holtecaydi 2022-08-04 15:19:03 UTC
Description:
Despite completely filling out the user data as recommended, whenever I edit a document, close it, re-open it, the program opens the document on the first page. Upon first noticing the problem, I re-installed the program...this worked for about three weeks before the bug reappeared. Now, even if re-installed, the bug is constant. It happens when working with ODT and DOCX files. 

Steps to Reproduce:
1. Open a document
2. Edit the document
3. Save the changes
4. Close the document
5. Re-open the saved document


Actual Results:
The document opens on the first page.

Expected Results:
Supposedly, once User Data has been modified, the program is supposed to jump to the previous edited position.


Reproducible: Always


User Profile Reset: Yes


OpenGL enabled: Yes

Additional Info:
It should have jumped to the last edited position.
Comment 1 Mike Kaganski 2022-08-04 20:16:02 UTC
Please note that it never worked for DOCX: bug 112740 (recently WONTFIXed).

Wrt ODT, recently I fixed one possible cause of lost recent position [1], when the cursor was near the end of long documents which took long to layout on open. Will be in 7.5. But generally, bug 141586 explains multiple problems around restoring the position as it is implemented now.

[1] https://git.libreoffice.org/core/+/9426e90c2c339b16487c48cd885a3e4586e1e1f3
Comment 2 Ezinne 2022-08-07 20:19:03 UTC
With the User data set, the bug is Not reproducible in:


Version: 7.5.0.0.alpha0+ / LibreOffice Community
Build ID: a9d225df2f8772e21435523ca20df1ece37390e4
CPU threads: 4; OS: Linux 5.15; UI render: default; VCL: gtk3
Locale: pt-BR (en_NG); UI: en-US
Calc: threaded
Comment 3 Ezinne 2022-08-07 20:22:44 UTC
(In reply to Mike Kaganski from comment #1)

> ... But generally, bug 141586 explains multiple
> problems around restoring the position as it is implemented now.
> 
> [1]
> https://git.libreoffice.org/core/+/9426e90c2c339b16487c48cd885a3e4586e1e1f3

@Mike Kaganski, Please can this bug report be set as a duplicate of bug 141586?
Comment 4 Mike Kaganski 2022-08-08 04:35:01 UTC
(In reply to Ezinne from comment #3)
> @Mike Kaganski, Please can this bug report be set as a duplicate of bug
> 141586?

I don't think it's correct, because bug 141586 is generic, while this one isn't explained in a way that allows to reproduce (e.g., a sample document would be nice, with some specific steps to make it not restore position - like "put cursor at page X between words A and B, add text N, set book view, save, reload").
Comment 5 QA Administrators 2023-02-06 03:19:33 UTC Comment hidden (obsolete)
Comment 6 QA Administrators 2023-03-09 03:26:44 UTC
Dear holtecaydi,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INSUFFICIENTDATA due to inactivity and
a lack of information which is needed in order to accurately
reproduce and confirm the problem. We encourage you to retest
your bug against the latest release. If the issue is still
present in the latest stable release, we need the following
information (please ignore any that you've already provided):

a) Provide details of your system including your operating
   system and the latest version of LibreOffice that you have
   confirmed the bug to be present

b) Provide easy to reproduce steps – the simpler the better

c) Provide any test case(s) which will help us confirm the problem

d) Provide screenshots of the problem if you think it might help

e) Read all comments and provide any requested information

Once all of this is done, please set the bug back to UNCONFIRMED
and we will attempt to reproduce the issue. Please do not:

a) respond via email 

b) update the version field in the bug or any of the other details
   on the top section of our bug tracker

Warm Regards,
QA Team

MassPing-NeedInfo-FollowUp