Bug 164043 - [MAR] After MAR-update, Windows keep old release number in Settings and registry
Summary: [MAR] After MAR-update, Windows keep old release number in Settings and registry
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Installation (show other bugs)
Version:
(earliest affected)
24.2.0.3 release
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
: 160585 (view as bug list)
Depends on:
Blocks: Automatic-Updater
  Show dependency treegraph
 
Reported: 2024-11-25 13:57 UTC by Olivier Hallot
Modified: 2024-11-26 15:53 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:


Attachments
Image shows old release after MAR update. (108.71 KB, image/png)
2024-11-25 13:57 UTC, Olivier Hallot
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Olivier Hallot 2024-11-25 13:57:12 UTC
Created attachment 197778 [details]
Image shows old release after MAR update.

I was able to update LO 24.8.2 to 24.8.3 with the MAR update.

After the update, Windows 10 settings still shows LO 24.8.2 ( see image attached)


Note: The update was in 2 steps, no indication why, which I gess it is for the main software and the Help. A more verbose text is welcome.


Additional info: 

Version: 24.8.3.2 (X86_64) / LibreOffice Community
Build ID: 48a6bac9e7e268aeb4c3483fcf825c94556d9f92
CPU threads: 8; OS: Windows 10 X86_64 (10.0 build 19045); UI render: Skia/Raster; VCL: win
Locale: pt-BR (pt_BR); UI: pt-BR
Calc: threaded
Comment 1 Dennis Roczek 2024-11-25 14:23:29 UTC
Can confirm. Found that out today also by accident.
Comment 2 V Stuart Foote 2024-11-25 18:07:47 UTC
(In reply to Olivier Hallot from comment #0)

See Mike's comment on see also/dupe bug 160585 and bug 68274

> 
> Note: The update was in 2 steps, no indication why, which I gess it is for
> the main software and the Help. A more verbose text is welcome.
> 

Believe that is expected, the MAR packaging is specific to signature, i.e. from 24.8.2.1 --> 24.8.3.1 --> 24.8.3.2
Comment 3 Rafael Lima 2024-11-25 20:36:14 UTC
I can confirm as well. As a user, I would expect the version to be the current one after the update.
Comment 4 Tulio Macedo 2024-11-25 20:42:32 UTC
I can confirm in Windows 11 as well.
Comment 5 V Stuart Foote 2024-11-26 15:08:29 UTC
*** Bug 160585 has been marked as a duplicate of this bug. ***