Bug 141662 - Crash when trying to update
Summary: Crash when trying to update
Status: RESOLVED DUPLICATE of bug 132901
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: UI (show other bugs)
Version:
(earliest affected)
unspecified
Hardware: x86-64 (AMD64) Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-04-12 22:25 UTC by stehlampen
Modified: 2021-04-13 07:43 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description stehlampen 2021-04-12 22:25:57 UTC
LibO crashed when I wanted to check for updates by navigating "Extras --> Optionen... --> Online-Update". After many minutes of helplessness, it turned out that the update component was not checked during the installation process a long time ago.

I propose instead, if "Online update" is not chosen to be installed, to change the source code of the UI to show a message like "Online update not installed. Please download the installer and change your installation to have the component "Online update" checked."
Another solution would be to check during runtime if the component is installed every time a user clicks on "Online Update".

Besides, two minor issues occurred during installation:
-- The message "System start will be needed if we proceed with installation" (or something similar) was displayed multiple times. One time suffices.
-- Concerning selecting the installation components: In the tree, even for components with no children, the user can choose between 
  - "This component will not be installed locally",
  - "This component will be installed locally" or
  - "This component _and all its subcomponents_ will be installed locally".
Since there are no subcomponents for the considered items, the third option should not be displayed.

Please note that my LibreOffice is installed and used in German, therefore the cited strings (translated to English by myself) may not be entirely accurate.
Comment 1 Xisco Faulí 2021-04-13 07:43:21 UTC
Thanks for reporting this issue.
This looks like a duplicate of bug 132901

*** This bug has been marked as a duplicate of bug 132901 ***