Apache OpenOffice (AOO) Bugzilla – Issue 8802
crash on importing a linux-saved doc with jpg graphic into OO windows 2000
Last modified: 2003-09-08 16:56:16 UTC
I've got a 50 page doc written on a linux system with OO1.0.1. There's only one single jpg in it, not embedded but linked. When I copy the doc (without the image) to a windows2000 machine and open it there with windows version of OO1.0.1, then OO crashes. If I turn back onto my linux machine and remove the jpg, save it, open it with OO-windows, then OO can open it. I've found an issues that maybe related to it: 4761, 5649.
you must attach a sample document that causes the crash for us to be able to figure this out. As small as possible :-), attach with http://www.openoffice.org/issues/createattachment.cgi?id=8802 after logging in
Created attachment 3410 [details] writer doc with one link to a jpg (not embedded)
Hi, I couldn't make the file smaller than it is. I tried the same procedure as mentioned above after I removed all text around the image but then there was no crash. With this file however it crashes if the jpg is present, and doesn't crash if the jpg is removed. The image (link to it) is nearly at the end of the doc. Don't care for the strage kind of text I use in that document. This is done on purpose :-)
Hello Felix. I'm a bit confused at this point. Should the attached file, "test3.sxw", crash OOo or not? If we need the JPEG file to crash OOo, please attach the picture to this issue. Unable to duplicate on Win NT 4.0 SP6a, OOo 643. File loads, but loads a bit slow.
Created attachment 3426 [details] image (jpg) to which test3.sxw has a link
Hi PM, sorry if I confused you. * The file test3.sxw crashed my OpenOffice (win 2000 version) when the file contained a link to a jpg that was *NOT* present/accessable. * So, test3.sxw (as is) should crash (it did at least on my win machine). * Now I attached the jpg although it was NOT necessary to have for demonstrating the crash. * Additional comment: OpenOffice did NOT crash after (a) I had reopened the file test3.sxw on a linux system, (b) deleted the link to the image, (c) saved the file again, (d) opened it with OpenOffice-win version. I tested it twice. * Additinal comment: The win2000 system is a pentiumIII-500 Mhz, 30GB UDMA hard disc, but 64MB RAM only. So, "crash" meant the following: Start OO, click to Open File, the file loads (see blue progress bar), the progress bar stops in the middle. Instead of displaying text, there was a grey background only (never seen before), and then I waited for 10 minutes - no reaction of OpenOffice anymore to any user operation. Thank You.
Created attachment 3428 [details] another doc (part of test3.sxw)
Hi, I've noticed another strange behaviour with my doc (test3.sxw). Because I start to believe more and more that the whole issue is due to something inside of this special file I didn't want to file a NEW issue. In case that someone is analysing my doc then the following thing may be another hint: * The last new attachement I created is called test-italic.sxw * This is a small part of test3.sxw (just one line of text). * Open it and place the cursor at the very first/top position (as it appears automatically) * press ctrl-i to change from italic to normal mode. * this doesn't happen, though. Thank You
test3.sxw loads and opens fine for me in OOo 643. I don't have 1.0.1 on a Win 2K machine at this point, so I'll test that later. Felix, if possible you could try using the unstable developer build 643 to see if that fixes the issue. Developer builds are used for testing purposes only.
Hi fkater, thanks for using and supporting Openoffice... I opened your document test3.sxw and all worked without a crash on OOo1.1RC3... Please try again with newest version and send a new comment if your problem occurs again... If there's no new comment until 09/02/2003 this Issue will be closed... reassigned to mci@openoffice.org
set to WORKSFORME...
Hi, works here, too, now! (Win2000, OOo 1.1 rc3) btw: This issue is assigned to my old identity Felix Kater - so I've got no overview right now about my older issues. Because I had forgotten the password I created a new one some time ago (with the same name + email address).
Felix Kater wrote: "works here, too, now!" Closing Issue...