Apache OpenOffice (AOO) Bugzilla – Full Text Issue Listing |
Summary: | Scanning into swriter causes the program to hang then crash | ||
---|---|---|---|
Product: | gsl | Reporter: | Unknown <non-migrated> |
Component: | code | Assignee: | philipp.lohmann |
Status: | CLOSED DUPLICATE | QA Contact: | issues@gsl <issues> |
Severity: | Trivial | ||
Priority: | P3 | CC: | issues |
Version: | OOo 1.1 Beta2 | Keywords: | oooqa |
Target Milestone: | OOo 2.0 | ||
Hardware: | PC | ||
OS: | Linux, all | ||
Issue Type: | DEFECT | Latest Confirmation in: | --- |
Developer Difficulty: | --- |
Description
Unknown
2003-07-07 14:33:54 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. . pl->cgu: can you reproduce this ? 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) I change the target 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. 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. Please have a look. maybe duolicate to 4487 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 *** closing duplicate |