Bug 161807 - Update note
Summary: Update note
Status: RESOLVED DUPLICATE of bug 149838
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
7.6.7.2 release
Hardware: x86-64 (AMD64) Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-06-27 09:57 UTC by Rook
Modified: 2024-07-22 13:40 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 Rook 2024-06-27 09:57:28 UTC
Description:
I have installed the latest version of LO (7.6.7). As soon as I did this, I get a message every day that there is a newer version. This is version 24.2.4, which has not yet been sufficiently tested and is intended for so-called power users. Please make sure that I am not notified of this update every day. It is annoying

Steps to Reproduce:
1.Start Office
2.Wait...
3.Ignore update info...

Actual Results:
The notice about this update appears every time the program is started

Expected Results:
The hint should stop if you constantly ignore it


Reproducible: Always


User Profile Reset: No

Additional Info:
This problem has occurred from time to time in the history of LO. Why it doesn't occur after some updates and is so annoying with other updates puzzles me
Comment 1 Rafael Lima 2024-06-27 12:14:00 UTC
This can be disabled. See:

https://ask.libreoffice.org/t/update-notice/61186

Simply go to Tools - Options - LibreOffice - Online Update. Remove the tick mark in Check for updates. Click OK to close.
Comment 2 Stéphane Guillou (stragu) 2024-07-22 13:40:30 UTC
Thanks for the report.

Apart from the workaround Rafael offered: it makes sense to offer an update to the next branch because 7.6.7 is the last version of the 7.6 branch, which had already reached end of life when you opened this report.
See: https://wiki.documentfoundation.org/ReleasePlan/7.6

Marking as duplicate of bug 149838, but see also bug 109098 and bug 97302.

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