Apache OpenOffice (AOO) Bugzilla – Full Text Issue Listing |
Summary: | Testing Base with dba qa test cases causes crash | ||||||
---|---|---|---|---|---|---|---|
Product: | Base | Reporter: | alex.thurgood | ||||
Component: | code | Assignee: | maho.nakata | ||||
Status: | CLOSED NOT_AN_OOO_ISSUE | QA Contact: | issues@dba <issues> | ||||
Severity: | Trivial | ||||||
Priority: | P2 | CC: | issues | ||||
Version: | 680m180 | Keywords: | crash, oooqa | ||||
Target Milestone: | --- | ||||||
Hardware: | All | ||||||
OS: | FreeBSD | ||||||
Issue Type: | DEFECT | Latest Confirmation in: | --- | ||||
Developer Difficulty: | --- | ||||||
Attachments: |
|
Description
alex.thurgood
2006-09-03 14:53:37 UTC
setting oooqa and crash keywords since chris said he would be takers for any reported incidents, this one's coming his way ;-) Alex Created attachment 38912 [details]
problematic Base document
works for me in a src680m180multi clu->wurzel: 1. please add the step by step description to the issue (because the current position and design of the linked document is provisional) 2. please add what you choose in those steps where you can choose betwwen more than one option (field, table, condition etc.) 3. i guess that the issue is repro by repeating step 12-24 (the query part) only? 4. have you the possibility to try this out on a n other os and/or another version (if office/java is corrupted)? do you use the oo native java (wizard is java based) thx @clu : I have Java version : java version "1.5.0-p2" Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0-p2-alex_12_feb_2006_10_56) Java HotSpot(TM) Client VM (build 1.5.0-p2-alex_12_feb_2006_10_56, mixed mode) I have tried this out on a MDV 2006 Linux, with Java 1.5 and the problem doesn't occur there, so I would say this is FreeBSD specific (unless others can confirm on other platforms). I'll try and write down exactly what I did so that you can compare. One thing I did notice was that a lock file was created that persisted even after the ODB file was recovered by the auto-recovery mechanism. This lock file may be what causes further manipulation in OOo to kill the Office. Alex @clu : I was just thinking that it might not be a good idea to set to resolved unless you tested on FreeBSD ? Just to further answer your previous question : yes, the crash is only reproducible when going through the Query wizard steps. The table creation wizard doesn't cause any problems as such. Another point that may be important : the table was empty, it didn't actually contain any data, when I started building the query. Alex as it looks like a freebsd only bug (and seems to work in general) => i reopen this bug to send it further sned further to freebsd developer @maho : more testing on 2.0.4m1 leads to same crash. The point at which the wizard crashes the first time around is as indicated below, when carrying out the dba qa tests : 23. insert any 'grouping condition' and 'next' Alex wurzel: sorry for long delay. 1. could you please tell me smaller subset of testcase so that I can reproduce very easily. 2. could you please use newer version of OOo? I hope this problem has been solved with newer version ;) Hello wurzel, *, as maho has asked you on March 26th, could you please answer his questions and give us a short feedback? TIA. Thomas. P.S.: This is only meant as reminder ... ;) Closing as invalid, coz a portupgrade hosed my FreeBSD system and I'm not going to reinstall...sorry people. Alex => close |