Bug 156472 - Explicitly naming programs that interfere with the installation
Summary: Explicitly naming programs that interfere with the installation
Status: UNCONFIRMED
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Installation (show other bugs)
Version:
(earliest affected)
7.5.5.2 release
Hardware: All Windows (All)
: medium normal
Assignee: Not Assigned
URL: https://ask.libreoffice.org/t/why-do-...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-07-26 04:12 UTC by Franklin Schiftan
Modified: 2024-11-01 14:02 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Franklin Schiftan 2023-07-26 04:12:39 UTC 
I know from other programme installers that they explicitly name programmes that are currently using components required for the installation, so that from the many running programmes only the really annoying ones can be terminated before a new installation attempt.

From my point of view, it would be desirable if LibO also explicitly named the programmes here and did not just "talk" globally about (any) programmes that use required components.
Comment 1 Stéphane Guillou (stragu) 2023-07-26 06:48:43 UTC 
Thanks Franklin.
Which message exactly are you referring to?
And which version of LO are you testing this with?
Comment 2 Franklin Schiftan 2023-07-26 07:41:55 UTC 
On installing LibO V 7.5.5.2 on Win10-64 I was informed that there are components in use of other programmes so a reboot was neccesary if the other (which?) programmes are not closed.
Comment 3 Buovjaga 2023-09-07 15:36:29 UTC 
(In reply to Franklin Schiftan from comment #2)
> On installing LibO V 7.5.5.2 on Win10-64 I was informed that there are
> components in use of other programmes so a reboot was neccesary if the other
> (which?) programmes are not closed.

Was this about fonts?
Comment 4 Franklin Schiftan 2023-09-07 17:41:07 UTC 
I have no idea, but the installer should actually know what's bothering it.
Comment 5 Mike Kaganski 2024-11-01 14:02:41 UTC 
In 2016, I implemented the support for Windows RestartManager in bug 69066. And when the restart manager gets activated, you get the list of the processes. If it doesn't, the list is not shown. Why it sometimes can't get activated, I don't know.