Created attachment 98383 [details] Microsoft Excel 2007 XLSX LO 4.2.x cannot open the attached xlsx spreadheet. LO 4.1.x opens the spreadsheet instantly. Tested with Windows and Linux versions: Doesn't open: 4.2.2.x 4.2.3.3 4.2.4.1 (Version: 4.2.4.1 Build ID: d4c441391e20647b3d2e8dde4d20aa868e77e515) Opens instantly: 4.1.5 4.1.6 (Version: 4.1.6.2 Build ID: 40ff705089295be5be0aae9b15123f687c05b0a) The file also opens with ApacheOO 4.0.x and 4.1.0.albeit slowly (around 4.5 min).
tested under Win7x64 bug already reproducibile in LibO 4.2.0.4 opens instantly with LibO 4.1.5.2 and 4.3.0.0.alpha1+ Build ID: 0b03f7ed575838f90e6b1ebec3538a3a214f81fb TinderBox: Win-x86@42, Branch:master, Time: 2014-04-30_02:30:23 so it's a regression of the 4.2.x branch which is fixed in 4.3.x branch so I mark this as RESOLVED WORKSFORME and let's hope a backport fix to 4.2.x will be possible in near future @NoOp please tell exactly which O/S you used.
OS tested: Windows 7 x64 Linux Ubuntu 12.04 x64
thanks, always remember to cite those info in any bug report description you write.
Also works for me with (linux): Version: 4.3.0.0.alpha1 Build ID: 46cfcd5a05aa1d13fecd73f5a25b64b8d8dd6781
Reopened and reset to the original reported version to ensure that the bug receives appropriate dev attention.While the yet to be released 4.3 version does 'fix' the issue, the problem still exists in the 4.2 release versions & reported the issue as 'fixed/resolved/worksforme/' indicates that the issue no longer needs dev attention - which it does.
@NoOp no this is not the correct procedure. 1- don't change the version number it should always indicate tghe first release where the bug has been reproduced.+ in this case: 4.2.0.4 2- once a bug is fixed in a codeline it should mark as RESOLVED, and not REOPENED, even if it's still present in the current codeline and fixed just in the development branch. and is labeled as FIXED if we know the committ that did it, or WORKSFORME if we don't know which one did. good or bad, these are the rules here :-) sometimes a fix which is in the 4.3.x line cannot always be easily backported to the 4.2.x (there are some fix that are the result of very drastical code change and cannot be applied to old branch) maybe if you are lucky the fix is already in a future 4.2.x release (you may try downloading a 4.2.4 RC1 or a 4.2.5 master from prerelease and daily builds page) to see if it's already there but in the worst case, you will have to wait for 4.3.0 final release which is end of july 2014. here some links in case you don't know have them at hand: http://www.libreoffice.org/download/pre-releases/ http://dev-builds.libreoffice.org/daily/libreoffice-4-2/ https://wiki.documentfoundation.org/ReleasePlan