Apache OpenOffice (AOO) Bugzilla – Full Text Issue Listing |
Summary: | Scan Crash | ||
---|---|---|---|
Product: | Writer | Reporter: | timcastle <mail4castle> |
Component: | code | Assignee: | timcastle <mail4castle> |
Status: | CLOSED NOT_AN_OOO_ISSUE | QA Contact: | issues@sw <issues> |
Severity: | Trivial | ||
Priority: | P3 | CC: | issues, oooqa |
Version: | OOo 1.0.1 | Keywords: | oooqa |
Target Milestone: | --- | ||
Hardware: | PC | ||
OS: | Windows ME | ||
Issue Type: | DEFECT | Latest Confirmation in: | --- |
Developer Difficulty: | --- |
Description
timcastle
2002-08-30 16:58:10 UTC
Tim, thanks for posting this issue. Please list step by step instructions that consistently reproduces this problem. Please attach all the files we need to reproduce this issue. Thank you for using and supporting OOo. Tim, please comment. Tim, Reassign to SBA when you have more info. -- Reassigned to submitter. Despite some reminders there is still no target milestone asigned. From the fact that reporter and owner are identical we conclude information is missing that doesn't allow working on this issue. That's why we've decided to close such issues. This is done without invidually taking care of each issue. If you feel this decision has been wrong regarding this specific issue, please re-open it. Despite some reminders there is still no target milestone asigned. From the fact that reporter and owner are identical we conclude information is missing that doesn't allow working on this issue. That's why we've decided to close such issues. This is done without invidually taking care of each issue. If you feel this decision has been wrong regarding this specific issue, please re-open it. Despite some reminders there is still no target milestone asigned. From the fact that reporter and owner are identical we conclude information is missing that doesn't allow working on this issue. That's why we've decided to close such issues. This is done without invidually taking care of each issue. If you feel this decision has been wrong regarding this specific issue, please re-open it. |