Description: When writer is called from the launcher, a blank document opens; this should close when a 'recent document' is selected, but it stays open. Steps to Reproduce: 1.start writer from the launcher and a blank doc opens 2.select 'file-recent documents' and open a recent document 3.(or 'file-open' and specify a document) Actual Results: The selected document opens, but the blank document stays open. Expected Results: The blank doc should be replaced by the selected doc on the desktop. Reproducible: Always User Profile Reset: No Additional Info: In other components of LO, the blank file closes when another is opened.
Thank you for reporting the bug. I can't confirm it with Version: 6.5.0.0.alpha0+ (x64) Build ID: 350d25da375f221edfa37309324ce3c68cf297ef CPU threads: 4; OS: Windows 10.0 Build 18362; UI render: default; VCL: win; Locale: de-DE (de_DE); UI-Language: en-GB Calc: threaded To be certain the reported issue is not related to corruption in the user profile, could you please reset your Libreoffice profile (https://wiki.documentfoundation.org/UserProfile) and re-test? I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' if the issue is still present.
Likewise do not reproduce on Windows 10 Home 64-bit en-US with Version: 6.4.0.2 (x64) Build ID: 08d19fecdc7a2298d051e19cfdb7c35544855fc3 CPU threads: 4; OS: Windows 10.0 Build 18362; UI render: GL; VCL: win; Locale: en-US (en_US); UI-Language: en-US Calc: threaded Opening a new blank Document in Writer, selecting a Writer (ODT) entry from the File -> Recent Documents list will cleanly open that document replacing the blank empty Writer document. Verified from the main menu 'Windows' menu. Of course, when a Writer document is opened (i.e. it is not empty/unsaved) making the same selection from the File -> Recent Documents menu will launch that into a new Writer frame. Verifiable also from the main menu 'Windows' menu. That is the expected behavior and functions correctly. As Dieter suggests please test with a clean user profile.
Thanks Dieter Praas. Resetting the profile did indeed solve the problem. Particularly, I only need to remove registrymodifications.xcu, and the problem goes away. But I don't know how to interpret this file or whether I can track it down further.