Bug 141226

Summary:	When the installer is used to update an existing installation to a newer version, it should just update using the existing configuration.
Product:	LibreOffice	Reporter:	jopes79264
Component:	Installation	Assignee:	Not Assigned <libreoffice-bugs>
Status:	RESOLVED INSUFFICIENTDATA
Severity:	enhancement	CC:	vsfoote
Priority:	medium
Version:	7.0.5.2 release
Hardware:	x86-64 (AMD64)
OS:	Windows (All)
See Also:	https://bugs.documentfoundation.org/show_bug.cgi?id=54242 https://bugs.documentfoundation.org/show_bug.cgi?id=141280
Whiteboard:
Crash report or crash signature:		Regression By:

Description jopes79264 2021-03-24 12:34:29 UTC

Description:
Situation: LibreOffice notified me that an update was available and I downloaded it using the torrent.
Expectation: I open the .msi file, it asks me to close documents if necessary, a progress bar will fill up, and documents will be reopened in the new version if applicable. No further interaction necessary, no need to re-check configuration settings, everything is kept as is.
What actually happens: The installer window pops up as if I'm installing it for the first time. I have to check all the installation configuration settings; some were wrong. It doesn't ask me to close documents and then complains that certain files are still in use. A progress bar fills up and clears and fills up again multiple times, making the progress bar worthless.
Why this matters: It discourages users from updating.

Steps to Reproduce:
1. Wait until update icon appears on menubar.
2. Click the icon.
3. Click the torrent.
4. Wait until torrent is finished.
5. Open .msi file.

Actual Results:
Installer window with problems as described above.

Expected Results:
Simple update as described above.


Reproducible: Always


User Profile Reset: No



Additional Info:
Version: 7.0.5.2 (x64)
Build ID: 64390860c6cd0aca4beafafcfd84613dd9dfb63a
CPU threads: 8; OS: Windows 10.0 Build 19042; UI render: Skia/Raster; VCL: win
Locale: nl-NL (nl_NL); GI: nl-NL
Calc: threaded

Comment 1 V Stuart Foote 2021-03-24 20:16:24 UTC

There is only so much hand holding we can do. Simply put DO NOT UPDATE LibreOffice (or any Windows program for that matter) when it has components running (here the soffice.bin of the core LO program, a common gotcha with the Quick Start open).

We could add additional MS Installer MSI logic to check for running application--but beyond that NOT A BUG.

As to an enhancement, not much value in trying to make this facet of UI seamless--more to the point is solving incremental updates as for bug 54242

IMHO => WF

Comment 2 Mike Kaganski 2021-03-27 09:01:47 UTC

(In reply to jopes79264 from comment #0)
> I have to check all the installation configuration
> settings; some were wrong.

This is unexpected. And you need to not mix different things into one report - this specific issue is generally expected to be OK, and correctly migrate the state of installed components - so please file a specific bug related to this, mentioning the originally installed version and its component set; new installed version; and which components were automatically pre-selected.

Comment 3 V Stuart Foote 2021-03-27 14:43:24 UTC

@jopes79264, were you perhaps updating from a 6.4 installation to the 7.0.5 release indicated? Or was this fully between 7.0 releases?  

And you wouldn't happen to have captured an MSI verbose installation log (which required a command line launch). So probably not, right?

Comment 4 Buovjaga 2022-04-01 09:06:05 UTC

(In reply to V Stuart Foote from comment #3)
> @jopes79264, were you perhaps updating from a 6.4 installation to the 7.0.5
> release indicated? Or was this fully between 7.0 releases?  
> 
> And you wouldn't happen to have captured an MSI verbose installation log
> (which required a command line launch). So probably not, right?

NEEDINFO while we wait for jopes to reply

Comment 5 QA Administrators 2022-09-29 03:56:04 UTC Comment hidden (obsolete)

Dear jopes79264,

This bug has been in NEEDINFO status with no change for at least
6 months. Please provide the requested information as soon as
possible and mark the bug as UNCONFIRMED. Due to regular bug
tracker maintenance, if the bug is still in NEEDINFO status with
no change in 30 days the QA team will close the bug as INSUFFICIENTDATA
due to lack of needed information.

For more information about our NEEDINFO policy please read the
wiki located here:
https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO

If you have already provided the requested information, please
mark the bug as UNCONFIRMED so that the QA team knows that the
bug is ready to be confirmed.
 
Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team

MassPing-NeedInfo-Ping

Comment 6 QA Administrators 2022-10-30 03:49:55 UTC

Dear jopes79264,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INSUFFICIENTDATA due to inactivity and
a lack of information which is needed in order to accurately
reproduce and confirm the problem. We encourage you to retest
your bug against the latest release. If the issue is still
present in the latest stable release, we need the following
information (please ignore any that you've already provided):

a) Provide details of your system including your operating
   system and the latest version of LibreOffice that you have
   confirmed the bug to be present

b) Provide easy to reproduce steps – the simpler the better

c) Provide any test case(s) which will help us confirm the problem

d) Provide screenshots of the problem if you think it might help

e) Read all comments and provide any requested information

Once all of this is done, please set the bug back to UNCONFIRMED
and we will attempt to reproduce the issue. Please do not:

a) respond via email 

b) update the version field in the bug or any of the other details
   on the top section of our bug tracker

Warm Regards,
QA Team

MassPing-NeedInfo-FollowUp