Issue 16544 - Scanning into swriter causes the program to hang then crash
Summary: Scanning into swriter causes the program to hang then crash
Status: CLOSED DUPLICATE of issue 4487
Alias: None
Product: gsl
Classification: Code
Component: code (show other issues)
Version: OOo 1.1 Beta2
Hardware: PC Linux, all
: P3 Trivial (vote)
Target Milestone: OOo 2.0
Assignee: philipp.lohmann
QA Contact: issues@gsl
URL:
Keywords: oooqa
Depends on:
Blocks:
 
Reported: 2003-07-07 14:33 UTC by Unknown
Modified: 2003-10-09 13:54 UTC (History)
1 user (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this issue.
Description Unknown 2003-07-07 14:33:54 UTC
*Tried in Beta1 and Beta2 using same hardware and sequence of operations.

Using an HP USB scanner in RH Linux 9 (custom kernel) the following happens when
scanning in an image using Writer:

Going to Insert->Graphics->Scan->Select source works fine.  Scanner is detected,
preview works great, all advanced settings for the scanner are functional.

Once the source is selected and configured, going to
Insert->Graphics->Scan->Request causes the scanner to go through the scanning
routine then the app to hang indefinitely.  The app will stay frozen until the
mouse is clicked anywhere whithin its frame, it will then proceed to crash. 
Running the app (swriter) from a shell and crashing it returns the following:
[olivierv@I8200 program]$ ./swriter
Xlib: unexpected async reply (sequence 0x7204)!
sh: line 1: crash_report: command not found
X IO Error

CPU usage does not spike, memory usage does not spike either.  It just stops
responding.
Comment 1 christof.pintaske 2003-07-08 11:22:16 UTC
cp->pl: please take care of this one. Maybe it's sufficient to get a
stack trace from the user. If not please hand over to QA to reproduce.
Comment 2 christof.pintaske 2003-07-08 11:34:16 UTC
.
Comment 3 philipp.lohmann 2003-07-08 11:46:22 UTC
pl->cgu: can you reproduce this ?
Comment 4 Unknown 2003-07-08 14:56:33 UTC
I went ahead and downloaded and installed Mandrake 9.1 on a completely
different system.  The only thing in common between the sytem on which
I initially reported and this new system is Open Office B2 and the HP
scanner (Scanjet 62x0C).

The following still holds true- the preview scan and settings work as
before.

The request action still freezes the app but does not cause a crash on
a mouse click within the app.  It simply stops responding (no more
redraws within the application frame, ie "smearing" and ghosting of
other apps brought in front of swriter).

Upon the program freezing, the console from which the app was started
says:
[root@mandrake program]# ./swriter
Xlib: unexpteced async reply (sequence 0xb106)!


Let me know if I can be of any more help.  (and thanks for an
otherwise superb app)
Comment 5 christian.guenther 2003-07-21 10:29:27 UTC
I change the target
Comment 6 alex.thurgood 2003-09-12 15:14:18 UTC
THe target's been changed to 2.0 !!!


I can confirm this behaviour on my Linux MDK 9.1 with a HP G85
Officejet multifunction scanner. The scanner works fine in Gimp and
XSane. In OOo 1.1 RC1, and RC4 scanning into Writer hangs the app as
described.


This for me is a showstopper. How can we let a GA go with such a bad
bug in it, that has been around for so long. There are at least 10
other issues pending that relate similar behaviour.

I am confirming and setting oooqa tag. I feel we ought to change the
priority and the target.

Alex.
Comment 7 christian.guenther 2003-09-24 17:32:39 UTC
Hi Alex
I can't reproduce the bug.
Do you get a freez or a crash? 
If you get a crash please you send us a crash report with the crash
reporter.
Comment 8 christian.guenther 2003-10-09 12:51:55 UTC
Please have a look.
maybe duolicate to 4487
Comment 9 philipp.lohmann 2003-10-09 13:54:07 UTC
I agree, this is a duplicate to issue 4487; the X IO error is caused
by the crash report routines after the actual crash happened as far as
i can see. I also changed the target of 4487 to 1.1.2 because of the
crash.

*** This issue has been marked as a duplicate of 4487 ***
Comment 10 philipp.lohmann 2003-10-09 13:54:54 UTC
closing duplicate