Speaking of unsupported software...
I recently added a new Brother laser printer to my network as the default printer. Whether that had anything to do with it or not, suddenly OpenOffice can't open any of it's old documents. It started out by crashing when asked to print, cycling through it's "recovering document", but then it started crashing as soon as the document was opened. Strangely, this behavior happened on two different machines.
I joined the #openoffice.org channel on Freenode, hoping for some help in troubleshooting this problem, and followed it for a couple of days. Question after question was asked, and I saw very few answers. An actual dialog appears in the channel this morning, but it certainly seems to be a problem in search of a solution.
On 3/7/07, Jonathan Hutchins [email protected] wrote:
Speaking of unsupported software...
I recently added a new Brother laser printer to my network as the default printer. Whether that had anything to do with it or not, suddenly OpenOffice can't open any of it's old documents. It started out by crashing when asked to print, cycling through it's "recovering document", but then it started crashing as soon as the document was opened. Strangely, this behavior happened on two different machines.
I joined the #openoffice.org channel on Freenode, hoping for some help in troubleshooting this problem, and followed it for a couple of days. Question after question was asked, and I saw very few answers. An actual dialog appears in the channel this morning, but it certainly seems to be a problem in search of a solution. _______________________________________________ Kclug mailing list [email protected] http://kclug.org/mailman/listinfo/kclug
This probably isn't the best answer, but do you have a backup of any of the files? If so then I think the OpenOffice format is basically just a zip file. You could extract the documents and compare the 'innards' and see if there are any differences. Of course, if it's corrupted the OpenOffice install this won't do any good. Perhaps just a 'mv ~/.openoffice ~/.openoffice.backup' to blow away your configs and restarting (btw, those definitely aren't the right directory names :)).
PS - I will learn to reply to all eventually.
On Friday 09 March 2007 10:05:12 pm Kyle Sexton wrote:
This probably isn't the best answer, but do you have a backup of any of the files? If so then I think the OpenOffice format is basically just a zip file. You could extract the documents and compare the 'innards' and see if there are any differences.
I doubt it. The behavior seems to apply to any old (pre-Brother) documents, so it would presumably apply to backups as well. I feel like they're most likely being corrupted when being opened by OO, or when being re-formatted to the Brother configuration. (That's just a guess, it could have nothing to do with the Brother, but the problem started when I added it.)
Of course, if it's corrupted the OpenOffice install this won't do any good. Perhaps just a 'mv ~/.openoffice ~/.openoffice.backup' to blow away your configs and restarting (btw, those definitely aren't the right directory names :)).
What I did was completely remove OpenOffice and all related config files (including ~/.openoffice), then do a fresh install. No dice, same exact behavior.
PS - I will learn to reply to all eventually.
Um, yeah, my client defaults to replying to the list, and that way you don't get two copies of the reply. Using conventional usenet style quote marks (>) and trimming irrelevant portions such as signatures and advertisements is polite too.
Posting HTML format to a mailing list is generally considered bad form. It makes the messages harder to archive, takes up more than 2x as much space, and is often trapped as spam.
Kyle Sexton wrote:
This probably isn't the best answer, but do you have a backup of any of the files? If so then I think the OpenOffice format is basically just a zip file.
They are Java Archive files (jar files). You can use `jar -xf document.odt` to extract the innards, and from there everything is in XML. You would probably be interested in the settings.xml file, and you can find the printer settings by searching for "PrinterSetup". Unfortunately, the info in this particular tag is base64 encoded and I have absolutely no clue what the value means.
~Bradley
On Monday 12 March 2007 13:16, Bradley Hook wrote:
Kyle Sexton wrote:
This probably isn't the best answer, but do you have a backup of any of the files? If so then I think the OpenOffice format is basically just a zip file.
They are Java Archive files (jar files).
What exactly is the difference between ZIP and JAR?
On Wed, 2007-03-07 at 08:48 -0600, Jonathan Hutchins wrote:
An actual dialog appears in the channel this morning, but it certainly seems to be a problem in search of a solution.
I have seen this behavior when OpenOffice attempts to apply the discovered printer's page attributes to an open document. If you make the printer go away in CUPS does OpenOffice continue working?
Just a note that your messages to the list still come through as unreadable encapsulated messages, and your direct messages report that the signature is bad.
On Wednesday 14 March 2007 11:12, Jonathan Hutchins wrote:
Just a note that your messages to the list still come through as unreadable encapsulated messages, and your direct messages report that the signature is bad.
Works perfectly fine in KMail, and the signature is valid even on direct emails...
Message was signed by [email protected] (Key ID: 0xB52AA3938DB3BF09). The signature is valid, but the key's validity is unknown.
On Wednesday 14 March 2007 01:20:50 pm you wrote:
On Wednesday 14 March 2007 11:12, Jonathan Hutchins wrote:
Just a note that your messages to the list still come through as unreadable encapsulated messages, and your direct messages report that the signature is bad.
Works perfectly fine in KMail, and the signature is valid even on direct emails...
Funny you should say that Luke - KMail 1.9.6 on KDE 3.5.6 here, but it's been true for years.
Telling someone you don't have a particular problem is the equivalent of telling them you don't know anything. Doesn't really contribute much to the solution.
-
Bradley Hook -
Jason D. Clinton -
Jonathan Hutchins -
Kyle Sexton -
Luke -Jr