https://bugs.documentfoundation.org/show_bug.cgi?id=164862
--- Comment #5 from Mike Kaganski <[email protected]> --- (In reply to librelibre from comment #4) > You conclusion is completely incorrect. I mentioned that I *can* manually > fix the problem by manually editing the registry, not that I did. I'm not > sure why you chose to ignore that critical word and omit it when quoting me. > Please do not misquote me, it is disingenuous and scientifically > inappropriate. An apology is warranted. > > Your error led you to a completely false conclusion. Given that I haven't > touched the registry (nor did I state that I did), your conclusion is > patently false and nonsensical. 1. You are wrong when requiring me to do the quoting differently - you only would be correct if the context wasn't readily available right here. It is a single thread, not a different scientific paper, where finding the source of the quote would require a separate research. 2. I specifically designed my phrase to make it clear what I strongly suspect to be the real cause. It worked as intended, you understood it correctly. In practice, people who tend to edit registry, use different registry cleaners, etc., often break the registry structure; and the problem may not be immediate edit of the *keys in question* - sometimes a previous such edit / cleanup somewhere else could break enough to disallow correct setting of the data here. I still am not convinced that it wasn't your (previous) registry edits that caused this. 3. Given how boldly you claimed your idea of the "actual cause" of the problem ("The reason is because soffice.exe is specified in the Windows registry for each action for the file type" in comment 2 - I admit that in comment 0, you used the "perhaps", but not later), why do you require others to state their assumptions less firmly? Now that "apology" is over, I hope that you will abstain from emotions, and focus on finding the facts. That's my goal, even when I have some reasons to suspect something, I still like to learn the problem, and you could notice that I didn't close the bug, which I would definitely do, if I was 100% sure. > That registry value is *not* set, and thus the LibreOffice installer is not > functioning correctly. Please do uninstall LibreOffice, then install it again, but this time, enable logging [1]. Attach the log here. [1] https://wiki.documentfoundation.org/Faq/General/General_Installation_Issues_(Windows)#Create_an_installation_log -- You are receiving this mail because: You are the assignee for the bug.
