Bug 162780 - LibreOffice Maintenance Service is installed unnecessarily
Summary: LibreOffice Maintenance Service is installed unnecessarily
Status: CLOSED FIXED
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Installation (show other bugs)
Version:
(earliest affected)
24.8.0.3 release
Hardware: x86-64 (AMD64) Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard: target:25.8.0 inReleaseNotes:25.8
Keywords:
Depends on:
Blocks: Automatic-Updater MAR_update_framework
  Show dependency treegraph
 
Reported: 2024-09-04 03:18 UTC by robbage
Modified: 2026-05-07 11:15 UTC (History)
7 users (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 robbage 2024-09-04 03:18:56 UTC
Description:
LibreOffice Maintenance Service is installed despite the optional component "Online Update" not being selected during installation process

Steps to Reproduce:
1.Start the installer
2.Make sure "Online Update" is unselected
3.Install application


Actual Results:
Maintenance Service appears anyway

Expected Results:
No maintenance service installed


Reproducible: Always


User Profile Reset: No

Additional Info:
Version: 24.8.0.3 (X86_64) / LibreOffice Community
Build ID: 0bdf1299c94fe897b119f97f3c613e9dca6be583
CPU threads: 12; OS: Windows 10 X86_64 (10.0 build 19045); UI render: default; VCL: win
Locale: en-AU (en_AU); UI: en-GB
Calc: threaded
Comment 1 V Stuart Foote 2024-10-04 18:48:25 UTC
IIUC the legacy Check for Update is distinct from the MAR incremental online-updates, and the "maintenance service" is the new piece as needed for MAR.

Enabled by default in master, 24.8 and 24.8.1 as with
https://gerrit.libreoffice.org/c/core/+/172406
Comment 2 V Stuart Foote 2024-12-18 13:28:45 UTC
resolved in master against a 25.8 release with
https://gerrit.libreoffice.org/c/core/+/178679

follow for any backport to 25.2 or 24.8 branches.
Comment 3 Ruby Turner 2026-05-07 11:06:20 UTC
I came across this discussion while researching similar technical issues and the details shared here were genuinely useful. I’ve noticed that keeping organized references like https://osceolacountycourt.org can really help when tracking updates and documentation efficiently. The way this bug was explained makes troubleshooting much easier for others facing the same situation. Thanks for taking the time to post such a clear report and follow-up information.