Apache OpenOffice (AOO) Bugzilla – Issue 31065
crash when opening document
Last modified: 2013-08-07 14:38:26 UTC
OOo.org-1.1.2 crashes everytime when I open this document (I have to figure out how to attach it :-)).
Created attachment 16256 [details] the file that won't open and crashes OOo
no crash with OOo 1.1.2 german and 680m45Ë™ Are you using a localized version of OOo or a version that came with your distribution? Does the crash-reporter pop-up or does OOo fail silently?
I downloaded a binary from here. The error report tool opens when it crashes. I sent the bug report to Sun with the error report tool.
So you're using an english version? I tried with german and french version of OOo 1.1.2 and no crash occured. Would you mind trying again with the developer snapshot 680m45 from http://download.openoffice.org/680/index.html ? Could you name something special of your setup (distribution, kernel version, version of glibc, version of X-Server)?
I also do not get a crash when trying to open this document with OO 1.1.x (including 1.1.2) on Linux. Maybe there's a problem while building up the view when having a special default printer on the system. Please tell us, which printer your system uses. BTW: you should have recieved a confirmation mail for your crash report. Please post the ID you got there, so that we can have a quick view into the crash report database. thanks for supporting us!
Temporarily set to "worksforme". Should be reopened when further (requested) information can be provided.
This is what I got from Sun Microsystems Quality Feedback <quality_feedback_NOSPAM@sun.com>: >Dear User, > >Thank you for sending the error report generated by the OpenOffice.org error >report tool. Your error report has been received and will be evaluated. > >Please do not reply to this automatically generated response. > >Sincerely, >Your OpenOffice.org Team It is flaky, it crashed twice and now it opened the document. It also crashes on some other documents. The printer was the generic printer but I changed the default. I have KDE/CUPS but I do not currently have a printer hooked up so I may delete all system printer (Open Office should not crash though :-)).
In the return-Mail from the error report, hasn't there been a line like "The ID of the error report is xxxxxx" ? Without this, we won't be able to have a look at the correct error stack. Could you please have a look or send another error report? Thank you for supporting us.
You probably only get the ID when you report the crash from within sun. The only part that may be used to identiry the report could be the "references" line: (these are two reports created today, but since I'm not able to reproduce this bug, these are other crashers. I don't know whether you can evaluate these lines. <393325.1091220470421.JavaMail.root@report.stardiv.de> <626276.1091222972118.JavaMail.root@report.stardiv.de> I'll attach a response with full-header. Please check whether you can query the ID using this data.
Created attachment 16866 [details] response from crash-report tool
No crash here: OOo 1.1.2 english version on w2k
MRU->AMA: there seems to be a crash on some machines. A crash report has been sent and cloph has attached response data drom the crash report. Maybe you can find the stack belonging to this and assign this to the correct Developer. Thanks!
to make things clear: I'm unable to reproduce the crash. the attached report_answer.txt is not a crash report, but the automatic generated answer mail one gets when sending one. I attached it because I wanted to know whether it is possible to get the ID based on the msgID or other header-data. (OpenOffice.org users don't get the ID itself) As I wrote earlier, the crash was produced with some other steps, not while reproducing this one. So any reports from "cloph" are unrelated. You have to look for reports coming from bjlockie Anyway the problem seems related to the printersettings (see comment from bjlockie - Sun Jul 25)
Even I was able to identify the crash report (Id: 170861). We couldn't find a hint what's goes wrong there. So we will not ind a fix for OOo2.0. Maybe we'll find a solution later if we're able to reproduce the problem?!
This Issue requires more information ('needmoreinfo'), but has not been updated within the last year. Please re-test with one of the latest versions of OOo - the problem(s) may already be addressed. Either use the latest stable version: http://download.openoffice.org/index.html or consider trying the new OOo 3 BETA (still in testing): http://download.openoffice.org/3.0beta/ Please report back the outcome of your testing, so this Issue may be closed or progressed as necessary - otherwise the issue may be Resolved as Invalid in the future. You may also wish to search for (and note) any duplicates of this Issue that may have progressed further : http://www.openoffice.org/issues/query.cgi Regards, Andrew Cleaning-up and Closing old Issues as part of: ~ The Grand Bug Squash, pre v3 ~
Do we really expect to get more info for a crash that happened 4 years ago and that nobody except the submitter could reproduce?
closing
I found this bug by accident and I tried to open the attached file, it crashed. I can reproduce this bug. I use Ubuntu 9.04, OpenOffice 3.1.0 OOO310m11 build 9399, package openoffice.org-core 1:3.1.0-3ubuntu2jaunty1.