Date: prev next · Thread: first prev next last
2011 Archives by date, by thread · List index


Hi :)
It's also not likely that a single app would crash the whole machine like that.  
One of the top 3 priorities of Gnu&Linux is that individual processes can fail 
without affecting the rest of the system.  Hence no Bsods.  Is your machine 
overheating severly?  Are you using a laptop or something with inadequate 
cooling?  Is your graphics card not pushed in properly or getting extremely 
hot?  Ram-sticks or cpu?  My money would be on the graphics chips over-heating 
or wobbly graphics card.  


If it is a desktop machine are you confident enough about opening the case and 
getting rid of some of the dust without touching any of the components or the 
mbord or anything?  Which country are you in?  In England the normal 3 pin mains 
earths the case so even though you would still need to turn off the machine at 
the back and at the wall you could remove static from your hands at that point 
by touching the case.  In the US it could be dangerous to touch the case even 
with the power off.  The static on your fingers and the oily grease even on 
carefully washed hands is enough to damage some components inside the machine so 
take care!  

Regards from
Tom :)





________________________________
From: JeepNut <JeepNut@zoho.com>
To: users@global.libreoffice.org
Sent: Fri, 22 July, 2011 17:42:36
Subject: [libreoffice-users] help recovering?

Hoping for some good news here.
Am using the openSuSE branded version of LibreOffice 3.3.3 OOO330m19
(Build:301) tag libreoffice-3.3.3.1 on openSuSE 11.3 and KDE 4.4.4-1.5.

Was editing a document that is pretty important (to me at least) and during
the process had tried to add a footnote.
I was editing the text in the footnote and almost immediately there was some
flashing of the screen and LibreOffice crashed, locking up the entire PC. 
No mouse control, no keyboard control, nothing.
So I had to "reset" the PC.
Now the document is fubar.  When I try to open it, LibreOffice attempts to
recover but fails.
Then it tries to repair the file but opens only a blank page.
I've tried to open it without an extension and get a list of a variety of
application types to attempt any modicum of recovery, but no matter what I
try to open it with it either fails, or opens in a file of unreadable
gibberish.
I'd be THRILLED if someone would be able to actually recover this document
for me.
Nothing secret in it, I'd be happy to email it to anyone who'd like to give
it a try.  Even just to get back the text out of it  so that I could rebuild
would be fabulous.

Any chance at all to recover?


--
View this message in context: 
http://nabble.documentfoundation.org/help-recovering-tp3191906p3191906.html
Sent from the Users mailing list archive at Nabble.com.

-- 
Unsubscribe instructions: E-mail to users+help@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/users/
All messages sent to this list will be publicly archived and cannot be deleted
-- 
Unsubscribe instructions: E-mail to users+help@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/users/
All messages sent to this list will be publicly archived and cannot be deleted

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.