<html>
<head>
<base href="https://bugs.documentfoundation.org/">
</head>
<body><table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>Bug ID</th>
<td><a class="bz_bug_link
bz_status_UNCONFIRMED "
title="UNCONFIRMED - Upgrade can fail with running LO processes"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=123012">123012</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>Upgrade can fail with running LO processes
</td>
</tr>
<tr>
<th>Product</th>
<td>LibreOffice
</td>
</tr>
<tr>
<th>Version</th>
<td>6.3.0.0.alpha0+ Master
</td>
</tr>
<tr>
<th>Hardware</th>
<td>All
</td>
</tr>
<tr>
<th>OS</th>
<td>All
</td>
</tr>
<tr>
<th>Status</th>
<td>UNCONFIRMED
</td>
</tr>
<tr>
<th>Severity</th>
<td>normal
</td>
</tr>
<tr>
<th>Priority</th>
<td>medium
</td>
</tr>
<tr>
<th>Component</th>
<td>Installation
</td>
</tr>
<tr>
<th>Assignee</th>
<td>libreoffice-bugs@lists.freedesktop.org
</td>
</tr>
<tr>
<th>Reporter</th>
<td>kelemeng@ubuntu.com
</td>
</tr></table>
<p>
<div>
<pre>Created <span class=""><a href="http://bugs.documentfoundation.org/attachment.cgi?id=148704" name="attach_148704" title="Upgrade of types.rdb failed">attachment 148704</a> <a href="http://bugs.documentfoundation.org/attachment.cgi?id=148704&action=edit" title="Upgrade of types.rdb failed">[details]</a></span>
Upgrade of types.rdb failed
These are two somewhat rare situations that randomly plague our user base.
* When we centrally trigger the upgrade process on Windows 7 via SCCM, and
users are running LO at the same time, the upgrade sometimes - but not always;
we are yet unsure exactly how to trigger this behavior - fails and leaves an
inoperable installation behind.
The error message is on the types-rdb-54.png picture, sent by one of our users.
Some .rdb files fail to correctly upgrade and then LO no longer starts, only a
reinstall helps.
* Another issue is on the second picture (LO5-6.PNG), taken while testing a 5.4
-> 6.0 upgrade in the test environment while LO was running. Because the
default install directory changed to be versionless, the upgrade run smoothly,
but left the running process with removed libraries to a swift crash. This can
be called sort of a bad user experience.
We think these two issues have a common root, that is the lack of proper
detection of a running instance and subsequently marking every new file - not
only a select few (shown on LO607-install.PNG) - for delayed installation.</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>