https://bugs.documentfoundation.org/show_bug.cgi?id=161048
--- Comment #4 from ady <[email protected]> --- (In reply to V Stuart Foote from comment #3) > If you want to install/test like that, what I'd suggest is to clear the per > user profile that links to you D:\LO\Alpha\program used in your custom > installs. Even though install is to your D: drive, your user profile is > going to be C:\Users\<yourusername>\AppData\Roaming\LibreOfficeDev. Delete > it to clear the profile (on next launch that will recreate with defaults. I have "reset" my LO Dev profile, but I have not manually deleted anything in C:\Users\<yourusername>\AppData\Roaming\LibreOfficeDev. I'd like to ask you, what should I manually delete, specifically, and what not? Additionally, should I delete anything using regedit.exe? FWIW, I have been installing and using LO Dev as I described, for more than a year, with several updates per month. The left-overs processes in Windows' Task Manager are new, and I cannot replicate the problem when going back to the build from 2024-04-30. So maybe the "/a" installation method overcomes or avoids the problem, whereas the "common" installation method allows the problem to be triggered. If this happens to be true, then at some point the "common" install method will arrive to the Stable branch (e.g. when 24.8 becomes Stable Fresh), and then users will report the same problem. My point is that perhaps the "common" installation should be tested now with LO Dev 24.8 in order to test whether the left-overs of soffice.exe can be replicated, after launching and closing the LO Dev Start Center several times. -- You are receiving this mail because: You are the assignee for the bug.
