Ask Your Question
0

LibreOffice 5.3.2.2 has corrupt CAB file

asked 2017-04-14 06:28:05 +0200

johnfarmer gravatar image

updated 2017-04-14 06:32:07 +0200

LibreOffice 5.3.2.2 failed to install due to corrupt CAB file. Had to re-install 5.2.6

edit retag flag offensive close merge delete

Comments

Where did you get your installer (msi) from?
My LibreOffice_5.3.2.2_Win_x64.msi downloaded from a tdf site installed flawlessly even on Win 10.

Lupp gravatar imageLupp ( 2017-04-14 09:32:48 +0200 )edit
johnfarmer gravatar imagejohnfarmer ( 2017-04-14 12:54:00 +0200 )edit

(Converted to an answer.)

Lupp gravatar imageLupp ( 2017-04-14 13:31:39 +0200 )edit

3 Answers

Sort by » oldest newest most voted
0

answered 2017-04-14 13:57:18 +0200

The MSI got corrupted at some point, possibly when you downloaded it, as now when I tried your link it worked perfectly (I needed to update anyway) although DL speed was low. You need to try other mirrors officially linked at www.libreoffice.org if one doesn't work.

edit flag offensive delete link more
0

answered 2017-04-22 18:18:31 +0200

cohiba gravatar image

Same problem even with the above download.
Still getting 1500 error code. Windows 10

edit flag offensive delete link more

Comments

I don't have your problem on Win10.
I had others, and I expect them to reoccur no later than the next Win-"update" is forced on me. It seems to me that Win10 has a poweful self-corruption feature.
It's a pity that I cannot simply throw away every junk adhering to my computer. It might be a full-time job for quite a while to get rid of it - and I depend on some special software only ....
Is it bribery? Is it a kind of cartel plot? Incompetence on my behalf? On someone else's?

Lupp gravatar imageLupp ( 2017-04-22 19:06:08 +0200 )edit

@Lupp You're definitely not the one to be blamed. Win10 was made with total surveillance in mind, and M$ never had the intention to make a good, working system, it's just to give 'fuck you' to the users every so often while getting more money. Some ppl I helped to set up their Win10 system say they've had no problems with updates, while a big part of the userland gets problems from destruction. If the system worked 1h ago, or yesterday, it's very possible another broken update is forced.

rautamiekka gravatar imagerautamiekka ( 2017-04-22 21:11:48 +0200 )edit

Addendum: in comparison, Win8.x is awesome system compared to Win10. An abomination the European Union has little trouble with, unlike with 8.0.

rautamiekka gravatar imagerautamiekka ( 2017-04-22 21:13:01 +0200 )edit
0

answered 2017-04-14 13:33:10 +0200

Lupp gravatar image

updated 2017-04-14 13:35:32 +0200

I fc-compared (binary: /B)
1) the 5.3.2.2_Win_x64.msi I actually installed from
2) the 5.3.2_Win_x64.msi currently provided by tdf (no longer treated as an RC but expected to be bitwise identical to the second RC)
with the 5.3.2_Win_x64.msi I just downloaded from the Australian mirror you linked to.
There were no differences found.
As I am neither a system nor a security specialist I cannot advise further on this issue.

edit flag offensive delete link more

Comments

At least on Ubuntu, the LO PPA's use the final RC release as the official non-RC release since they're always identical.

rautamiekka gravatar imagerautamiekka ( 2017-04-14 13:58:38 +0200 )edit

Yes. It's the same with the msi packages for Win. They only are renamed omitting the RC digit if no further RC is needed. I thought I expressed that (as a rule) by my remark "...no longer treated as RC but...".

Lupp gravatar imageLupp ( 2017-04-14 14:07:07 +0200 )edit

Right, but the PPA uses the naming the last RC had, which immediately made sense to me: no point in bothering with renaming when nothing's changed.

rautamiekka gravatar imagerautamiekka ( 2017-04-22 21:14:44 +0200 )edit
Login/Signup to Answer

Question Tools

1 follower

Stats

Asked: 2017-04-14 06:28:05 +0200

Seen: 292 times

Last updated: Apr 22 '17