Windows/MSI builds only (x64, but I'm sure x86 as well).
Upon a MAJOR version upgrade (i.e. 6.1.4 to 6.2.0), the QuickStarter shortcut in the user's Start Menu/Startup folder (%APPDATA%\Roaming\Microsoft\Windows\Start Menu\ Programs\Startup) does NOT get renamed or updated from "LibreOffice 6.1" to "LibreOffice 6.2".
The link still correctly points to the existing %PROGRAMFILES%\LibreOffice\program\quickstart.exe, so this is obviously cosmetic.
However, if one were to go to the running Quickstarter in the Taskbar and enable "Load LibreOffice during System Startup" (which is unchecked even though installed/upgraded with the QUICKSTART=1 flag), then this will create a 2nd LibreOffice entry (6.2 in addition to 6.1) in the Startup program group.
It probably doesn't matter, but I believe that this has been existing behavior and not 6.2 specific.
Can not confirm.
On Windows 10 Ent 64-ti en-US with 220.127.116.11 installed, and a per user LibreOffice setting of Tools -> Options -> General: "Load LibreOffice during system start-up" showing the LibreOffice 6.1 shortcut object in %APPDATA%\Microsoft\Windows\Start Menu\Programs\Startup...
the "LibreOffice 6.1" shortcut is removed during the MSI install/cleanup.
During installation, the checkbox for "Load LibreOffice during system start-up" was not checked--just the checkbox for Quickstarter in the options.
Launching LibreOffice, and then checking it active Tools -> Options -> General writes the "LibreOffice 6.2" shortcut per user into their %APPDATA% Startup folder.
This seems the desired behavior since we're keeping Quickstarter around.
Well - I can easily see that this must be reproducible, if not using interactive installation, then using some centrally configured deployment scenario. I don't know if uninstall includes removal of the shortcut (comment 2 implies it does), but such a removal can only handle *currently logged in* user, not any user of the system; and if e.g. the installation is performed using GPO at system startup, before user logged in, then it must be as described in comment 0.
Actually, I don't know a way to fix this, other than making the shortcut name to have no version information, or using the proposal from bug 116694.
I should have been more specific. Mike hit it on the head -- generally deployed when user is offline, but even still, installed by a user other than the logged-in-user.
I deploy via WPKG, and the install command is _generally_ as follows -- I have a bunch of variable substitution here as I remove most DICT, LANGPACK, and HELPPACK (and a few default extensions).
msiexec /i "%SOFTWARE%\Libreoffice\LibreOffice_%PKG_VERSION%_Win_x64.msi" /q ISCHECKFORPRODUCTUPDATES=0 SELECT_WORD=1 ADDLOCAL=ALL SELECT_EXCEL=0 SELECT_POWERPOINT=1 SELECT_VISIO=1 CREATEDESKTOPLINK=0 REGISTER_XLS=0 REGISTER_XLSX=0 REGISTER_DOC=1 REGISTER_DOCX=1 REGISTER_DOCM=1 REGISTER_DOT=1 REGISTER_DOTX=1 REGISTER_DOTM=1 REGISTER_RTF=1 REGISTER_PPT=1 REGISTER_PPS=1 REGISTER_PPSX=1 REGISTER_PPTX=1 REGISTER_PPTM=1 REGISTER_POT=1 REGISTER_POTX=1 REGISTER_POTM=1 REGISTER_ALL_MSO_TYPES=0 QUICKSTART=1 VC_REDIST=1 UI_LANGS=en_US RebootYesNo=No PRODUCTALLLANGUAGES=en-US REMOVE=%DICT%,%LANGPACK%,%HELPPACK%,%MISCEXT% /norestart
My understanding is that QUICKSTART=1 corresponds to a registry entry, which in turn creates or ensures that the Quickstarter link is created at every user session. Is it possible to change the behavior to remove previous link(s) and create new ones with the current version?
Lastly, again, this is cosmetic, so not crucial by any means.
Dear Kris Lou,
To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year.
There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present.
If you have time, please do the following:
Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/
If the bug is present, please leave a comment that includes the information from Help - About LibreOffice.
If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice.
Please DO NOT
Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not
appropriate in this case)
If you want to do more to help you can test to see if your issue is a REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/
2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword
Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa
Thank you for helping us make LibreOffice even better for everyone!
Isn't this the same issue as described in bug 35568? Can we mark as a duplicate?
(In reply to Stéphane Guillou (stragu) from comment #6)
No. It is indeed related to the awkward way we implement the (de)activation of the feature at OS level, but it's very different.