Issue 124913 - Disable 4.1.0 Update Info
Summary: Disable 4.1.0 Update Info
Status: CLOSED WONT_FIX
Alias: None
Product: Infrastructure
Classification: Infrastructure
Component: Downloads (show other issues)
Version: current
Hardware: All Windows, all
: P3 Critical (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-05-16 04:25 UTC by Rainer Bielefeld
Modified: 2015-11-05 22:12 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---

Attachments
Screenshot showing "Update Available" info (21.77 KB, image/png)
2014-05-16 04:25 UTC, Rainer Bielefeld 		no flags Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description Rainer Bielefeld 2014-05-16 04:25:46 UTC 
Created attachment 83400 [details]
Screenshot showing "Update Available" info

Steps how to reproduce with "AOO 4.0.1 – German UI / German locale [AOO401m3(Build:9712) - Rev. 1520285 2013-09-05 13:52:01]" on German WIN7 Home Premium (64bit)", Common 4.0 User Profile:

Simply launch AOO 4.0.1, open an arbitrary document and wait a while: Update info (see screenshot) will appear.

It's a very bad idea to recommend an update for WIN users as long as the recommendation is for an AOO version with "Issue 124717 - Embedded GDI Metafiles replaced by "Read Error" box" in it.

Currently it's difficult to calculate how many users might be affected, but we already have DUPs and due to my preliminary research results every user with documents with pictures copied from other software or other AOO application might be affected. 

At least on my PC I after I have used 4.1.0 for a while I see lots of lots of damaged documents showing symptoms of the bug (.svm pictures with .bmp file name extension in unzipped document)
Comment 1 Marcus 2015-11-05 22:12:03 UTC 
The update feeds were changed in the meantime and for the new version 4.1.2 they are starting and get still improved (see issue 126612). Therefore I'm closing this issue. New problems should be reported with a new issue.