Issue 7360 - Scan Crash
Summary: Scan Crash
Status: CLOSED NOT_AN_OOO_ISSUE
Alias: None
Product: Writer
Classification: Application
Component: code (show other issues)
Version: OOo 1.0.1
Hardware: PC Windows ME
: P3 Trivial (vote)
Target Milestone: ---
Assignee: timcastle
QA Contact: issues@sw
URL:
Keywords: oooqa
Depends on:
Blocks:
 
Reported: 2002-08-30 16:58 UTC by timcastle
Modified: 2003-09-08 16:56 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description timcastle 2002-08-30 16:58:10 UTC 
When I try to insert a scanned image the program crashes and I get the 
following message:

Soffice has caused an error in SCN641M.DLL
Soffice will now close
Comment 1 prgmgr 2002-09-24 00:34:16 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.
Comment 2 stefan.baltzer 2003-01-10 11:48:00 UTC 
Tim, please comment.
Comment 3 eric.savary 2003-01-31 17:03:16 UTC 
Tim,

Reassign to SBA when you have more info.
--

Reassigned to submitter.
Comment 4 michael.bemmer 2003-03-24 11:57:32 UTC 
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.
Comment 5 michael.bemmer 2003-03-24 12:04:05 UTC 
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.
Comment 6 michael.bemmer 2003-03-24 12:11:42 UTC 
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.