Bug 161432 - LibreOffice 7.6.7.2 is repeatedly prompting to upgrade to v24.2.3 on MacOS 13.6.7 (on Intel)
Summary: LibreOffice 7.6.7.2 is repeatedly prompting to upgrade to v24.2.3 on MacOS 13...
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: IA64 (Itanium) macOS (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-06-05 19:20 UTC by Ken Selig
Modified: 2024-06-24 08:31 UTC (History)
2 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 Ken Selig 2024-06-05 19:20:22 UTC
Description:
LibreOffice 7.6.7.2 is repeatedly prompting to upgrade to v24.2.3 on MacOS 13.6.7 (on Intel)

Steps to Reproduce:
1. Open LibreOffice (and perhaps open or start a new file?)
2. Wait for the globe icon to appear in the MacOS system bar [if check for updates automatically is enabled, else use Help > Check for Updates for a manual check]
3. Click the globe icon [assuming check for updates automatically is enabled, else use Help > Check for Updates for a manual check] and be directed to the new version available pop-up, then click the button to go to https://www.libreoffice.org/download/download-libreoffice/ to download the newest version manually
4. Realize you're already at the current stable/LTS version release and do not wish to switch to the current release on the other channel
5. Close the new browser tab with the download page and ignore the globe icon in the system bar for a few days before repeating this process again to see if there is a newer version of the LTS channel available - perhaps with a fix for this bug

Actual Results:
The new version available alert is alerting for the wrong channel when on the LTSR version of the app suite

Expected Results:
A new version alert should only appear when a newer version of the same channel release is available.


Reproducible: Always


User Profile Reset: No

Additional Info:
Version: 7.6.7.2 (X86_64) / LibreOffice Community
Build ID: dd47e4b30cb7dab30588d6c79c651f218165e3c5
CPU threads: 4; OS: Mac OS X 13.6.7; UI render: Skia/Raster; VCL: osx
Locale: en-US (en_US.UTF-8); UI: en-US
Calc: threaded

--
Note: On MacOS the About LibreOffice selection is not under the Help menu - it's under the LibreOffice menu. Please consider updating the bug reporting form to reflect this navigation delta.
Comment 1 Stéphane Guillou (stragu) 2024-06-22 04:42:13 UTC
Thanks for the report.

Because the 7.6 branch has reached End of Life[1], it makes sense to point users to the branch that will receive updates and has become the de facto "mature" branch - especially since security update won't get to that branch.
Longer-term support exists from ecosystem companies[2].

So I would close as "not a bug", but I see it has been suggested before to allow turning this branch-hopping update suggestion off and I think it's a good candidate for duplicate.

[1]: https://wiki.documentfoundation.org/ReleasePlan/7.6
[2]: https://www.libreoffice.org/download/libreoffice-in-business/

*** This bug has been marked as a duplicate of bug 153101 ***
Comment 2 Ken Selig 2024-06-22 19:14:41 UTC
If the stable channel is now deprecated / EoL then that should be reflected on the downloads page - https://www.libreoffice.org/download/download-libreoffice/

Currently, there is no indication of this.
Comment 3 Stéphane Guillou (stragu) 2024-06-24 08:31:16 UTC
(In reply to Ken Selig from comment #2)
> If the stable channel is now deprecated / EoL then that should be reflected
> on the downloads page -
> https://www.libreoffice.org/download/download-libreoffice/
> 
> Currently, there is no indication of this.
That would be an issue for Redmine then, because it is about the website.
https://redmine.documentfoundation.org

I actually found a better ticket to mark duplicate of, which talks about this exact issue: bug 149838. If you want to add something, please do so there so the conversation happens in one place.
Having tickets marked as duplicates helps focus the conversation and have an idea of how many people are affected.
Thank you!

(Note that the status "reopened" is only for after a report was set to "resolved - fixed".)

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