Bug 74934 - 'Install' button in update dialog is never activated
Summary: 'Install' button in update dialog is never activated
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Libreoffice (show other bugs)
Version: 4.2.0.4 release
Hardware: Other All
: highest normal
Assignee: Not Assigned
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: mab4.3
  Show dependency treegraph
 
Reported: 2014-02-13 15:10 UTC by Jan Holesovsky
Modified: 2015-01-17 09:37 UTC (History)
5 users (show)

See Also:
i915 platform:
i915 features:


Attachments

Description Jan Holesovsky 2014-02-13 15:10:22 UTC
Currently the 'Install' button in the update dialog is never activated.  It is because we do not provide automatic download of new version.

In order to be able to have this functionality, we need to make sure that the download is safe - that the cannot get a binary from some malicious site instead.

The code needs review & update in case there are dangerous bits there; then we can enable this.
Comment 1 Jan Holesovsky 2014-02-13 15:10:46 UTC
MAB - as discussed at the ESC.
Comment 2 Jan Holesovsky 2014-02-13 15:11:49 UTC
Short term, we should at least update the help:

https://help.libreoffice.org/swriter/EXTENSIONS_HID_CHECK_FOR_UPD_DLG
Comment 3 Björn Michaelsen 2014-03-16 01:12:34 UTC
Fix priority for MABs.
Comment 4 tommy27 2014-11-29 17:47:54 UTC
@Jan
is this MAB still reproducible with 4.3.x releases?
Comment 5 Robinson Tryon (qubit) 2014-12-07 19:10:59 UTC
(In reply to Jan Holesovsky from comment #0)
> Currently the 'Install' button in the update dialog is never activated. 

CONFIRMED with 4.3.2.2 + Ubuntu 14.04

REPRO:
1) Open LibreOffice
2) Help -> Check for updates.

RESULT:
LO 4.3.4 is offered for download, but the 'Install' button stays grayed-out
Comment 6 Adolfo Jayme 2015-01-17 09:37:14 UTC
Can we consider using Sparkle/WinSparkle instead?


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.