Bug 144426 - Background updates
Summary: Background updates
Status: RESOLVED DUPLICATE of bug 74934
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
7.1.6.2 release
Hardware: All All
: medium enhancement
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-09-10 08:34 UTC by Joselp
Modified: 2023-02-01 09:19 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 Joselp 2021-09-10 08:34:51 UTC
Description:
Hi all, I don't know if this upgrade has already been requested, I can't find in the bugs list.

I think that Libreoffice should implement the background updates, and that the user don't go to the web to download the next version of Libreoffice.

Actually, I find much installations of Libreoffice without update because the user see the warning but after don't go to download web.

This can lead to security problems, compatibility problems and new features don't see of the Libreoffice users.

Steps to Reproduce:
1. Install Libreoffice, for example, 7.0.4 version
2. Go to, "search updates" or wait to the update warning.
3. Libreoffice will go to the official web, and the user should download manually the new version.

Actual Results:
Actually, Libreoffice go to the official web, and the user should download manually the new version

Expected Results:
If the user see the warning, but don't go to the web to download the last version, Libreoffice will isn't updated.


Reproducible: Always


User Profile Reset: No



Additional Info:
Libreoffice should download the new version automatically and proceed to update the previous version installed on the computer.
Comment 1 Adolfo Jayme Barrientos 2021-09-12 23:27:55 UTC
Please read
https://blog.documentfoundation.org/blog/2021/08/03/tender-to-implement-autoupdater-202108-01/

*** This bug has been marked as a duplicate of bug 125451 ***
Comment 2 Thomas Bertels 2023-02-01 09:19:42 UTC

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