https://bugs.documentfoundation.org/show_bug.cgi?id=157458
Stéphane Guillou (stragu) <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEEDINFO Ever confirmed|0 |1 --- Comment #8 from Stéphane Guillou (stragu) <[email protected]> --- Thank you both. I also tried: 0. Make sure the "Save AutoRecovery information" setting is set to something small, like 1 minute 1. Create a new document, _don't save it_, add text 2. Wait for AutoRecovery to kick in by waiting more than one minute without touching LO 3. Kill the LO process 4. Reopen LO, recovery dialog shows, recover the document: unsaved changes are there 5. Change AutoRecovery setting again so LO asks to restart: I am prompted to save the file, which works as expected, then it restarts, and I can reopen the saved file, no data loss. (step 5 does not apply to 24.2, which does not need a restart when changing AutoRecovery settings) So it's actually all working as expected for me too, in all active branches: Version: 7.5.7.1 (X86_64) / LibreOffice Community Build ID: 47eb0cf7efbacdee9b19ae25d6752381ede23126 CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded Version: 7.6.2.1 (X86_64) / LibreOffice Community Build ID: 56f7684011345957bbf33a7ee678afaf4d2ba333 CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: ff9c8b62c1015972e9e89799832fa3690dcd46b4 CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded nador2, please see if you can provide precise steps that reproduce an issue consistently, testing with a recent daily build: https://dev-builds.libreoffice.org/daily/master/current.html But with 24.2 not needing a restart anymore, I'd say we can probably close this report as "works for me"? -- You are receiving this mail because: You are the assignee for the bug.
