Bug 105619 - 5.3RC3 OSX: Icon shown in system bar showing app update is false
Summary: 5.3RC3 OSX: Icon shown in system bar showing app update is false
Status: RESOLVED DUPLICATE of bug 74934
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
5.3.0.2 rc
Hardware: x86-64 (AMD64) macOS (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-01-30 17:23 UTC by Martin Srebotnjak
Modified: 2017-01-31 11:20 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Martin Srebotnjak 2017-01-30 17:23:40 UTC 
Description:
Running 5.3.0.3 (RC3) on OSX and I get the icon announcing there is an update of software available.
There is currently no newer build than this.
Also, clicking on that icon does nothing (probably I should enter another bug report, but only after this is confirmed here as a bug).

Steps to Reproduce:
1. Install and open LO53RC3 on OSX.
2. Make sure that Online Updates are enabled (in LibreOffice > Settings > LibreOffice > Online Update
3. Wait for some time that LO checks for updates and shows the crane icon in the system OSX bar, usually on the top of your screen.

Actual Results:  
Icon for existing update shows.

Expected Results:
No icon for existing updates.


Reproducible: Always

User Profile Reset: No

Additional Info:


User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:51.0) Gecko/20100101 Firefox/51.0
Comment 1 steve 2017-01-30 17:48:35 UTC 
Updates have been broken for as long as I have taken a first look at LO. There are tickets addressing this.

https://bugs.documentfoundation.org/show_bug.cgi?id=68274
https://bugs.documentfoundation.org/show_bug.cgi?id=74934

Considering the above bugs, I decided it's not worth looking in more detail at teh current (broken) mechanism. What do you think? Should we keep your bug?
Comment 2 Alex Thurgood 2017-01-31 11:10:44 UTC 
I concur with Steve. At best this is a duplicate of known existing behaviour, O would opt for DUP of bug 74934.
Comment 3 steve 2017-01-31 11:20:34 UTC 

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