2ND TRY: Can't open LO DMG file. How contact tech support?

asked 2016-10-22 17:50:58 +0200

mkraft gravatar image

I posted about this previously on Oct. 18: i.e., not being able to open the downloaded DMG file . . . https://ask.libreoffice.org/en/questi...

I've now downloaded the DMG file a second time, with the same result.

If no one here can tell me how to solve this obvious dilemma ('can't open' means 'can't use'), is there a way to directly contact LibreOffice tech support?


edit retag flag offensive close merge delete


Before you try an earlier version (http://www.libreoffice.org/download/l...), try downloading that file from http://rautamiekka.org/public/LibreOf...

rautamiekka gravatar imagerautamiekka ( 2016-10-22 19:03:24 +0200 )edit

Thanks but what's the difference between your DMG and the official one at LO's website?

Also, are you LO tech staff or a user? (Isn't there a way to get in direct communication with LO's 'tech support' -- or does it not even have any?)

mkraft gravatar imagemkraft ( 2016-10-22 20:08:55 +0200 )edit

It's the same file. If the result doesn't change whether you get it from LO site or from mine, then the file most likely is fucked to begin with. I'm just an user, and not even a good one with LO. Dunno if they even have a tech staff except for one keeping the site up; I seem to recall The Document Foundation saying they don't have anyone to help ppl, leaving the job for others. Lemme check the hash of the file just in case.

rautamiekka gravatar imagerautamiekka ( 2016-10-22 20:15:17 +0200 )edit

The hashes match, so my site, and my computer, has the identical file. You really should verify the hash, it's the only surefire way to know if the file made it to your computer without getting changed some way.

rautamiekka gravatar imagerautamiekka ( 2016-10-22 20:30:26 +0200 )edit

Actually, I did. Or at least I did the best I could with trying to verify the hash. I didn't understand what to do with the result, though. I eventually found what appeared to be the hash I was supposed to compare my result to and there was nothing similar about them.

That's when I decided to just forget about it and download the file again. But then I got the same result with that again, too -- i.e., the .DMG wouldn't open, returned same error message.

mkraft gravatar imagemkraft ( 2016-10-22 22:14:50 +0200 )edit

If the file was 'fucked' wouldn't others be reporting the problem, too? Doesn't seem likely I'm the only Mac user who d/l'd 5.2.2 in the past 5 days.

mkraft gravatar imagemkraft ( 2016-10-22 22:16:04 +0200 )edit

Dunno if there are reports of that. So you ran the DMG through a sha256 hasher and that didn't match the website ? I'm pretty sure OS X has sha256sumprogram in the standard app library. Once you've received the hash, copy it, open http://download.documentfoundation.or... and paste the hash into the search.

rautamiekka gravatar imagerautamiekka ( 2016-10-22 22:18:50 +0200 )edit

It didn't match this:

SHA-256 Hash: 73b501e710a51016f80c38f4104021114a35c578b68ad48ac7e237a36bd015a4

I don't know whether that's what I was supposed to compare my result to or not, but it was nothing like the above.

I have no experience doing this kind of stuff. I just relied on my reasonable knowledge of the command line and ran the command with the name of the file. (I think I used one of your flags, not the other.) It returned a hash string so I assumed the command went off okay.

mkraft gravatar imagemkraft ( 2016-10-22 22:49:58 +0200 )edit

I think this was it:

shasum -a 256 -c LibreOffice_5.2.2_MacOS_x86-64.dmg.sha256

I used -a but not -c.

String returned was:


mkraft gravatar imagemkraft ( 2016-10-22 22:51:35 +0200 )edit

If you didn't add -c before that .sha256, making the line shasum -a 256 LibreOffice_5.2.2_MacOS_x86-64.dmg.sha256 instead of shasum -a 256 -c LibreOffice_5.2.2_MacOS_x86-64.dmg.sha256, you hashed the hash file instead of the installation file. To hash the installation file, run shasum -a 256 LibreOffice_5.2.2_MacOS_x86-64.dmg.

rautamiekka gravatar imagerautamiekka ( 2016-10-23 12:00:20 +0200 )edit