Apache OpenOffice (AOO) Bugzilla – Issue 22739
Inserting text field under RH9 crashes OOo
Last modified: 2013-08-07 14:38:26 UTC
When I create the Input Field I go to Insert - Fields - Other - Functions - Input Field. I enter a suitable descriptor (which becomes the text in the tooltip) in the Reference text box and then click Insert and the Input Field dialogue box opens. As I am creating the blank form I leave the main text area empty and click OK. OOo returns to Input field page whereupon I click Close and OOo crashes. Fortunately crash reporting work and the crash dump is sent to Sun.
Retested and it works. Something funny going on ... Since the crash is in the pipe I will research some more.
Unable to reproduce (Mandrake 9.2/Redhat 9) 1.1.1a -- Do you have any further information? Can you attach the crash report to this issue? Thanks, Tam
Created attachment 12470 [details] Crash dump as requested
HI->ES: Please have a look.
First a little history: Path: main.gmane.org!not-for-mail From: "Artem B. Bityuckiy" <mail_lists@mail.ru> Newsgroups: gmane.comp.openoffice.questions Subject: Possible bug Date: Sun, 16 Nov 2003 18:22:38 +0300 Lines: 23 Approved: news@gmane.org Message-ID: <3FB7963E.6000107@mail.ru> Reply-To: users@openoffice.org NNTP-Posting-Host: deer.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Trace: sea.gmane.org 1068996191 3891 80.91.224.253 (16 Nov 2003 15:23:11 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Sun, 16 Nov 2003 15:23:11 +0000 (UTC) Original-X-From: users-return-50815-opof-users=m.gmane.org@openoffice.org Sun Nov 16 16:23:08 2003 Return-path: <users-return-50815-opof-users=m.gmane.org@openoffice.org> Original-Received: from s002.sfo.collab.net ([64.125.133.202] helo=openoffice.org) by deer.gmane.org with smtp (Exim 3.35 #1 (Debian)) id 1ALOk0-0003H1-00 by deer.gmane.org with smtp (Exim 3.35 #1 (Debian)) id 1ALOk0-0003H1-00 for <opof-users@gmane.org>; Sun, 16 Nov 2003 16:23:08 +0100 Original-Received: (qmail 22904 invoked by uid 5302); 16 Nov 2003 15:22:52 -0000Mailing-List: contact users-help@openoffice.org; run by ezmlm Precedence: bulk X-No-Archive: yes list-help: <mailto:users-help@openoffice.org> list-unsubscribe: <mailto:users-unsubscribe@openoffice.org> list-post: <mailto:users@openoffice.org> Delivered-To: mailing list users@openoffice.org Original-Received: (qmail 22887 invoked from network); 16 Nov 2003 15:22:51 -0000 Original-Reply-To: mail_lists@mail.ru User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.5) Gecko/20031011 X-Accept-Language: en, ru, en-us Original-To: users@openoffice.org X-Enigmail-Version: 0.76.7.0 X-Enigmail-Supports: pgp-inline, pgp-mime Xref: main.gmane.org gmane.comp.openoffice.questions:49664 X-Report-Spam: http://spam.gmane.org/gmane.comp.openoffice.questions:49664 It seems I've found a bug in OOO I'm using OOO 1.1 - rpm package from Fedora Core 1. How to reproduce: >soffice File->New->Text Document Insert->Indexes and Tables->Indexes and Tables... Entries In "Structure" field place cursor after "E#" Press Esc OOO should crash. P.S. I'm not in mailing list because I've dropped somehow and still can't subscribe. :-( Send personal e-mail if needed. Thanks. -- Best Regards Artem B. Bityckiy
Confirmed in Novemeber. I see that the meaning of Priority has been changed and nolonger specifies what eash level means. However, when I joined QA the criteria was that anything that crashes OOo is a P1. I will accept P2. It the crash dump is insufficient to resolve the problem please let me know.
JA: the attached call stack doesn't help. As it already has been sent I believe it will be processed soon. On the other hand I cannot reproduce this. Please post some information about your OpenOffice.org build and some more detailed information about your system. The attached mail needs to be ignored because it hasn't got anything related with this issue.
Nothing to do with the issue. How wrong you are. It was the start of the process. What is the problem? That the reporter did not create the issue? Please explain as the attached email has everything to do with the issue. Had it not been reported I would not have tested and would not have found that indeed the problem exists. You claim you cannot recreate the problem well then have the courtesy to report your environment. If it does not match those reported please find a system that does match and retry. If necessary, I will consider allowing you to setup and SSH2 tunnel to my system in order to reach a solution. As to the call stack, it and others like it have been sent to Sun on a regular basis since this problem reoccurs regularly. Perhaps you should find one of those.
Please explain why the crash when pressing <esc> in an index-edit dialog should be related to an issue related to a crash when using input fields. -> mail is to be ignored. P1 never has been the prio for crashes. For the description of priorities that has been used before the upgrade of SourceCast (and that hopefully be restored soon) see http://qa.openoffice.org/servlets/ReadMsg?list=dev&msgNo=541 This issue is P3 or maybe P2 The problem is not reproducible following the steps given, however I can crash OOo using a slightly different order of closing the dialog (first close the big Insert -fields dialog and then the small input-field dialog) this is issue 24755 and since that issue has a good explanation/step-by-step instructions and not so much fuzz, I close this one as duplicate. If you really can crash OOo using the order specified in this issue (close the small one first, then the big one) feel free to reopen the issue. *** This issue has been marked as a duplicate of 24755 ***
closing duplicate. reopen if appropriate.
Well you do what you must. Are you on piece work? I ask because you left a p1 bug open for more than 2 months before asking for more information. When you got you claim it was not satisfactory. After I updated the issue with all the pertinent info I have from my records you make a specious claim that this is a duplicate of a newer issue. Something is rotton in Denmark. And I do think that your responses are a bit arrogant considering the situation. I'm sorry that my memory is faulty but that comes with age and I do the best I can under the circustances. I wish you had done the same.
> Well you do what you must. Are you on piece work? I ask because you left a p1 > bug open for more than 2 months before asking for more information. Are you kidding? It is NOT P1, no matter how many times you tell. You couldn't even reproduce yourself - how can a non-reproducible crash be P1? There are many issues that haven't been touched for month, but this has nothing to do with piece work but with too many issues for too few developers. > When you got you claim it was not satisfactory. Have you reread the mail you posted to this issue? Do you still claim that it has anything to do with this issue? And what is wrong with telling the truth (trace won't help here)? > After I updated the issue with all the > pertinent info I have from my records you make a specious claim that this is a > duplicate of a newer issue. Something is rotton in Denmark. Have you compared this issue and the other one? Notice the difference? Why should I keep two issues open that describe the same issue? Why shouldn't I keep the one that is easier to read/contains the better reproducible description? > And I do think that your responses are a bit arrogant considering the > situation. Hello? Please relax, re-read the messages, trying not be be biased veforehand and judge again. (Exclude this comment) PS: Please don't forget that issueZilla is not about exchanging courtesies but technical information. If possible please use the mailing-lists (dev@qa.openoffice.org) to discuss this further.
Created attachment 12745 [details] Attemtping to insert fileld
So much for not being resproducible. It is easy to do. See techinical information is easy when you ask.
Is your crash other thatn the one described in issue 24755? If not, then you should be happy since it is already fixed for OOo 2.0 and has been targeted for OOo 1.1.2 - that means if the target gets accepted will be fixed in the 1.1.x-line as well. If this issue is different from issue 24755 please give a detailed step-by-step instruction on how to reproduce the crash.