<html>
<head>
<base href="https://bugs.documentfoundation.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_UNCONFIRMED "
title="UNCONFIRMED - Calc Zoom -> 'Synchronise sheets' user preference boolean changes in user profile settings unexpectedly during upgrade installation"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=142666#c6">Comment # 6</a>
on <a class="bz_bug_link
bz_status_UNCONFIRMED "
title="UNCONFIRMED - Calc Zoom -> 'Synchronise sheets' user preference boolean changes in user profile settings unexpectedly during upgrade installation"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=142666">bug 142666</a>
from <span class="vcard"><a class="email" href="mailto:mikekaganski@hotmail.com" title="Mike Kaganski <mikekaganski@hotmail.com>"> <span class="fn">Mike Kaganski</span></a>
</span></b>
<pre>(In reply to Colin from <a href="show_bug.cgi?id=142666#c5">comment #5</a>)
<span class="quote">> Is there a procedure I can run periodically to detect any potential
> corruption in my user profile - I assume when you refer to "file corruption"
> you are referring to something potentially identifiable by a chkdsk command
> as it's probably impossible to identify that something has changed a binary
> "true" to "false" without physical damage to the structure?</span >
No, I refer not to a physical disk corruption (and so not to something
identifiable by chkdsk), although such disc corruptions indeed could cause this
(but such things would be not possible to fix in LibreOffice code, even in
theory). What I am thinking about is some problem in LibreOffice (either in
older version generating an invalid profile, or in newer version considering
valid profiles as invalid). And this could only be identified by backing up the
profile [1] from time to time, and especially before upgrading, so that if the
problem appears, one could then try again with the profile restored from
backup, check if restored backup also gets the setting "reset"; maybe check if
older version still has the setting correct (downgrading the version);
inspecting the setting in the profile before and after running the new version
(to see if it changes) ... and finally filing the bug with the "good" profile
attached, to allow devs to try and see what in the profile causes the problem
(in the hope that it would also happen on others' system).
[1] <a href="https://wiki.documentfoundation.org/UserProfile">https://wiki.documentfoundation.org/UserProfile</a></pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>