Description: A recovered document has "(Remote)" in the title Steps to Reproduce: 1. Open a new Writer document 2. Kill the proces tree in the ask manager 3. Restart LibreOffice & click restore/start 4. Notice "(Remote)" Actual Results: Shows remote Expected Results: Probably not.. not sure what it would mean Reproducible: Always User Profile Reset: No Additional Info: Version: 6.3.0.0.alpha0+ Build ID: bbf9b65f91e8136fa1a2e17960944b8720f5d58e CPU threads: 4; OS: Windows 6.3; UI render: default; VCL: win; TinderBox: Win-x86@42, Branch:master, Time: 2019-03-15_09:56:33 Locale: nl-NL (nl_NL); UI-Language: en-US Calc: threaded
Thank you for reporting the bug. I can confirm that the bug is present in Version: 6.3.0.0.alpha0+ (x64) Build ID: 91cdf22b88a4f7bec243c8fb187627e766d3294c CPU threads: 4; OS: Windows 6.3; UI render: default; VCL: win; TinderBox: Win-x86_64@42, Branch:master, Time: 2019-03-08_00:38:10 Locale: en-US (en_US); UI-Language: en-US Calc: CL In: Version: 6.2.1.2 (x64) Build ID: 7bcb35dc3024a62dea0caee87020152d1ee96e71 CPU threads: 4; OS: Windows 6.3; UI render: default; VCL: win; Locale: en-US (en_US); UI-Language: en-US Calc: CL After Killing the process in Task Manager when I am Restarting LibreOffice Its not showing restore window so I can not notice "(Remote)" in Title
Hello mulla.tasanim, thanks for checking. Then we can consider it a regression...
I don't get the recovery dialog with the bibisect repo. I wonder, how I might change this?
(In reply to Buovjaga from comment #3) > I don't get the recovery dialog with the bibisect repo. I wonder, how I > might change this? Recovery dialog shows up for me normally (also in bibisect mode (tested 6.2 only).. However also heaving trouble in the range required, with the portable builds at hand Good: Versie: 5.0.0.1 Build ID: 9a0b23dd0ab9652e0965484934309f2d49a7758e Locale: nl-NL (nl_NL) Bad LO5242
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
No repro with Version: 7.5.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: cfc8a8f5d841b3f84d207196153be67da7f60652 CPU threads: 4; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: cs-CZ (cs_CZ.UTF-8); UI: en-US Calc: threaded
Can't reproduce in LO 7.6 Dev build under Windows 10(x64). Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 1c638b7ac46d8077994c8483e6becc4a33efd12b CPU threads: 4; OS: Windows 10.0 Build 19044; UI render: Skia/Raster; VCL: win Locale: en-IN (en_IN); UI: en-US Calc: threaded
Telesto: per the recent test results, do you still see this?
1. It is repro using 7.6.0. 2. It is *not* reproducible using 24.2.0. In 7.6.0, it is *only* reproducible using steps from comment 0 *literally*, i.e. opening a new document, and killing it. If you open an existing document, the problem won't appear. If you edit the new document, and let it auto-save, the problem won't appear. Only a non-existing non-saved document would trigger this. The disappearance of the problem in 24.2+ is likely due to Justin's great improvements in the autorecovery area. However, that is only a guess. And I recall that some changes were reverted, at least temporarily - so maybe that would be still a problem. Regression *in version 5.1* after: 26c106a5aeca3e50d1e3c3d37e622b2743a23bca "append '(Remote)' in the titlebar when remote file is opened" (unsurprisingly, isn't it?). I believe that there is still a bug in the logic of "is this remote" check; simply we stopped to recover absent documents.
https://gerrit.libreoffice.org/c/core/+/171027
To reproduce in current versions, ass this line to registrymodifications.xcu: <item oor:path="/org.openoffice.Office.Recovery/RecoveryList"><node oor:name="recovery_item_1" oor:op="replace"><prop oor:name="Title" oor:op="fuse"><value>Untitled 1</value></prop><prop oor:name="Filter" oor:op="fuse"><value>writer8</value></prop><prop oor:name="Module" oor:op="fuse"><value>com.sun.star.text.TextDocument</value></prop><prop oor:name="TempURL" oor:op="fuse"><value></value></prop><prop oor:name="ViewNames" oor:op="fuse"><value></value></prop><prop oor:name="OriginalURL" oor:op="fuse"><value></value></prop><prop oor:name="TemplateURL" oor:op="fuse"><value></value></prop><prop oor:name="DocumentState" oor:op="fuse"><value>0</value></prop></node></item>
To reproduce in current versions, add this line to registrymodifications.xcu, after existing "SessionData" line (the placement is important here): <item oor:path="/org.openoffice.Office.Recovery/RecoveryList"><node oor:name="recovery_item_1" oor:op="replace"><prop oor:name="Title" oor:op="fuse"><value>Untitled 1</value></prop><prop oor:name="Filter" oor:op="fuse"><value>writer8</value></prop><prop oor:name="Module" oor:op="fuse"><value>com.sun.star.text.TextDocument</value></prop><prop oor:name="TempURL" oor:op="fuse"><value></value></prop><prop oor:name="ViewNames" oor:op="fuse"><value></value></prop><prop oor:name="OriginalURL" oor:op="fuse"><value></value></prop><prop oor:name="TemplateURL" oor:op="fuse"><value></value></prop><prop oor:name="DocumentState" oor:op="fuse"><value>0</value></prop></node></item>
(In reply to Mike Kaganski from comment #9) > I recall that some changes were reverted That doesn't affect this case. Unnamed, unmodified documents are still not recovered. Yes, the fact that there is now no file recovery happening at all for this unmodified document is due to commit 9e0f13b2c4d31537162434b5b932b265c62349e0 Author: Justin Luth on Thu Jul 20 16:29:41 2023 -0400 tdf#57414 autorecovery: don't always add every file to RecoveryList
Mike Kaganski committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/9b911aaa3d2c7258fd41a896b7d57ca8c2a476fb tdf#124213: handle private URLs as non-remote It will be available in 25.2.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
Mike Kaganski committed a patch related to this issue. It has been pushed to "libreoffice-24-8": https://git.libreoffice.org/core/commit/470295c39cea861558bc0db1a1d2074f9cf4504e tdf#124213: handle private URLs as non-remote It will be available in 24.8.0.2. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.