<html>
<head>
<base href="https://bugs.documentfoundation.org/">
</head>
<body><span class="vcard"><a class="email" href="mailto:freedesktop@nuclearsunshine.com" title="freedesktop@nuclearsunshine.com">freedesktop@nuclearsunshine.com</a>
</span> changed
<a class="bz_bug_link
bz_status_NEW "
title="NEW - Document recovery strips encryption"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=93389">bug 93389</a>
<br>
<table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>What</th>
<th>Removed</th>
<th>Added</th>
</tr>
<tr>
<td style="text-align:right;">Status</td>
<td>UNCONFIRMED
</td>
<td>NEW
</td>
</tr>
<tr>
<td style="text-align:right;">Ever confirmed</td>
<td>
</td>
<td>1
</td>
</tr></table>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - Document recovery strips encryption"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=93389#c6">Comment # 6</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - Document recovery strips encryption"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=93389">bug 93389</a>
from <span class="vcard"><a class="email" href="mailto:freedesktop@nuclearsunshine.com" title="freedesktop@nuclearsunshine.com">freedesktop@nuclearsunshine.com</a>
</span></b>
<pre>Sorry, that's ridiculous. This bug is not intermittent and its reproduction is
not difficult, time-consuming or lacking a full set of steps.
I provided clear, step-by-step instructions to reproduce this two years ago,
which take approximately *two* minutes for anyone to carry out to confirm this.
I have since *re-tested* it two years later using my *exact* instructions, on
an entirely different system, and re-confirmed it.
To further eliminate any doubt, I have now re-tested it a *third* time, and
re-confirmed it again, using a fresh VM and a Fedora 26 live ISO. This makes
the bug environment *exactly* reproduceable, and clearly not even slightly
custom.
I am changing the status back to new. Instead of changing it again, either take
the two minutes needed to actually confirm it, or leave the status as new.
Setting it to UNCONFIRMED is an abuse of that status on the technicality that
no-one has bothered to even *try* to confirm the easily and quickly
reproduceable bug, which would actually be the useful thing to do.</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>