Problem description: The check for updates menu entry is in the help menu. While on Mac this usually appears in the App menu. Being in the help menu it is also unavailable if you have no application open i.e. you just have the shell open with no Help menu. Steps to reproduce: 1. Open LibreOffice in shell 2. No Help menu can't check for new version 3. Open LibreOffice Write 4. Check in App menu - no Check for updates entry 5. Click on Help menu - Check for updates there Current behavior: Check for updates is in the Help menu Expected behavior: On Mac, Check for Update is available in the LibreOffice app menu. Operating System: Mac OS X Version: 4.0.1.2 release
(In reply to comment #0) > Problem description: > The check for updates menu entry is in the help menu. While on Mac this > usually appears in the App menu. I agree with that > Being in the help menu it is also unavailable if you have no application > open i.e. you just have the shell open with no Help menu. > Steps to reproduce: > 1. Open LibreOffice in shell > 2. No Help menu can't check for new version Mmmh, I can find the 'Check for updates' entry in menu Help in this step. > 3. Open LibreOffice Write > 4. Check in App menu - no Check for updates entry > 5. Click on Help menu - Check for updates there Because I agree with the fact most applications of Mac OSX can check for updates in the 'LibreOffice' menu entry, I mark this bug as NEW. Following [1] I mark this as 'trivial low'. Kind regards, Joren [1] https://wiki.documentfoundation.org/images/0/06/Prioritizing_Bugs_Flowchart.jpg
(In reply to comment #1) > (In reply to comment #0) > > Problem description: > > The check for updates menu entry is in the help menu. While on Mac this > > usually appears in the App menu. > > I agree with that > > > Being in the help menu it is also unavailable if you have no application > > open i.e. you just have the shell open with no Help menu. > > Steps to reproduce: > > 1. Open LibreOffice in shell > > 2. No Help menu can't check for new version > > Mmmh, I can find the 'Check for updates' entry in menu Help in this step. A misinterpretation of 'shell' here. 1) Start LO write 2) Ctrl-W to close any open docs 3) LO is still open but only has LibreOffice and File menu. 4) No help menu, so can't check version info.
Actgually, I think that most Mac apps will soon be distributed through the Mac App Store. And the App Store has its own update mechanism, so apps don't need any own update mechanism, and are not allowed to have any. Just saying. Whether TDF will see the writing on the wall or not I don't know.
Just wanting to add another perspective: 1) as long as LO is not in the MAS, this is a very valid enhancement request 2) coda, the award winning famous OSX editor app from panic inc. just shut down coda being available on the MAS since with their new version apple's restrictions where to annoying so that they instead went back to the good old sparkle updates for their stand-alone only app as update mechanism Don't get me wrong, if LO was on the MAS I'd instantly stop talking about integrating sparkle. But as long as we are not there yet, the debate should be open and there are several arguments pro and con MAS just as there are pro con sparkle update mechanism.
There is additional discussion on the Sparkle project. https://github.com/sparkle-project/Sparkle/issues/380 Some Sparkle developers and hackers want to help make this happen. Are there some experts here that can help explain build details for Mac?
(In reply to comment #5) > There is additional discussion on the Sparkle project. > https://github.com/sparkle-project/Sparkle/issues/380 > > Some Sparkle developers and hackers want to help make this happen. > > Are there some experts here that can help explain build details for Mac? I think you might receive the necessary help by using the developer-mailinglist: http://lists.freedesktop.org/mailman/listinfo/libreoffice and/or using the IRC-chat: irc://chat.freenode.net/libreoffice-dev How to build on Mac is documented over here: https://wiki.documentfoundation.org/Development/BuildingOnMac Kind regards, Joren
** Please read this message in its entirety before responding ** 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 on a currently supported version of LibreOffice (5.0.5 or 5.1.0) https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System 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) http://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: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for your help! -- The LibreOffice QA Team This NEW Message was generated on: 2016-02-21
Still valid. Version: 5.0.5.2 Build ID: 55b006a02d247b5f7215fc6ea0fde844b30035b3 Mac OS X 10.11.3
** Please read this message in its entirety before responding ** 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 on a currently supported version of LibreOffice (5.2.7 or 5.3.3 https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System 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) http://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: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug-20170522
(In reply to QA Administrators from comment #9) > Test to see if the bug is still present on a currently supported version of > LibreOffice > (5.2.7 or 5.3.3 https://www.libreoffice.org/download/ > > If the bug is present, please leave a comment that includes the version of > LibreOffice and > your operating system, and any changes you see in the bug behavior Still present in LibreOffice 5.3.3.2_de-DE, as well as in 5.4.0.0.beta1_de-DE on macOS Sierra 10.12.5.
*** Bug 111873 has been marked as a duplicate of this bug. ***
** Please read this message in its entirety before responding ** 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 http://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://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Is it a standard the "Check for updates" is in the App menu? All the apps that I use have it in the Help menu (sometimes the About or Tools menu). I use: Mozilla Firefox and Thunderbird, Adobe Acrobat Reader, LibreOffice, Microsoft Office, SourceTree, Eclipse, GnuCash. I don't mind it being in the App Menu, and probably do prefer it there, but it doesn't seem to be a common practice (based on the Apps I use).
"Bug" is still present. Version: 6.1.0.3 Build ID: efb621ed25068d70781dc026f7e9c5187a4decd1 CPU threads: 8; OS: Mac OS X 10.13.6; UI render: default; Locale: en-AU (en_AU.UTF-8); Calc: group threaded
Dear Dwayne Bailey, 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 http://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://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Alex: as MacOs user, any thoughts here? If you confirm, perhaps we may ping UI team?
Confirming Other FOSS software already does this on macOS, e.g. VLC, Firefox, etc Still valid IMO.
Code pointer: extensions/source/update/check/org/openoffice/Office/Addons.xcu this file contains: <node oor:name="OfficeHelp"> https://opengrok.libreoffice.org/xref/core/extensions/source/update/check/org/openoffice/Office/Addons.xcu?r=8dc38dd9#21 Taking a look at officecfg/registry/schema/org/openoffice/Office/Addons.xcs I noticed these: - https://opengrok.libreoffice.org/xref/core/officecfg/registry/schema/org/openoffice/Office/Addons.xcs?r=c31fa068#514 for help menu - https://opengrok.libreoffice.org/xref/core/officecfg/registry/schema/org/openoffice/Office/Addons.xcs?r=c31fa068#479 for app menu? I tried this patch: diff --git a/extensions/Configuration_updchk.mk b/extensions/Configuration_updchk.mk index 394a1ae6c76d..ad543ba584b6 100644 --- a/extensions/Configuration_updchk.mk +++ b/extensions/Configuration_updchk.mk @@ -24,8 +24,17 @@ $(eval $(call gb_Configuration_add_spool_modules,updchk,extensions/source/update # localized "Title" property values of # /org.openoffice.Office.Common/Menus/New/m0 (install:module="writer") end up in # registry_*.xcd instead of a, say, writer_*.xcd): +ifeq ($(OS),MACOSX) + +$(eval $(call gb_Configuration_add_localized_datas,updchk,extensions/source/update/check,\ + org/openoffice/Office/Addons_mac.xcu \ +)) + +else + $(eval $(call gb_Configuration_add_localized_datas,updchk,extensions/source/update/check,\ org/openoffice/Office/Addons.xcu \ )) +endif copy of extensions/source/update/check/org/openoffice/Office/Addons.xcu to extensions/source/update/check/org/openoffice/Office/Addons_mac.xcu changing just "OfficeHelp" to "AddonMenu" but got this: warning: failed to load external entity "schemaRoot" cannot parse schemaRoot I found schemaRoot in LO sources but don't understand how it works. Of course, I'm not sure too that using "AddonMenu" will add "Check for Updates" in App menu. Stephan: since it concerns Macos and noticed some commits from you about schemaRoot, thought you may be interested and have some ideas?
Still present in Version: 7.1.4.2 / LibreOffice Community Build ID: a529a4fab45b75fefc5b6226684193eb000654f6 CPU threads: 4; OS: Mac OS X 10.16; UI render: default; VCL: osx Locale: fr-FR (fr_FR.UTF-8); UI: fr-FR Calc: threaded