Issue 62255 - Crash with Sig 11 on exporting one specific document to tagged pdf
Summary: Crash with Sig 11 on exporting one specific document to tagged pdf
Status: CLOSED FIXED
Alias: None
Product: Writer
Classification: Application
Component: save-export (show other issues)
Version: OOo 2.0.2
Hardware: PC Linux, all
: P3 Trivial (vote)
Target Milestone: ---
Assignee: h.ilter
QA Contact: issues@sw
URL:
Keywords: crash, needmoreinfo, oooqa
: 63193 (view as issue list)
Depends on:
Blocks:
 
Reported: 2006-02-18 21:15 UTC by hes
Modified: 2013-08-07 14:40 UTC (History)
2 users (show)

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


Attachments
this document generates on my machine a sig 11 on exporting to pdf (9.79 KB, application/vnd.oasis.opendocument.text)
2006-02-18 21:17 UTC, hes
no flags Details
stack trace on FC4---No, I didn't get an ID. (12.92 KB, text/xml)
2006-02-20 14:33 UTC, aziem
no flags Details
Crash report from OOo 2.0.1 Windows 2000--also sent via crash tool (10.08 KB, text/xml)
2006-02-22 16:09 UTC, aziem
no flags Details

Note You need to log in before you can comment on or make changes to this issue.
Description hes 2006-02-18 21:15:34 UTC
Exporting one specific one page document to pdf generates reproducable a sig 
11. This document was generated by mixing imports of eMail (kmail) per Drag & 
Drop and some typing.
Sorry, I can't provide a URL but I can send this doc file by eMail.
Please send me an eMail address to hes@hesconsult.de
Comment 1 hes 2006-02-18 21:17:51 UTC
Created attachment 34270 [details]
this document generates on my machine a sig 11 on exporting to pdf
Comment 2 aziem 2006-02-19 03:02:01 UTC
Confirm crash with OOo 2.0.2rc1 Linux RPMs Fedora Core 4 x86-32.  I sent a crash
report with my OOo e-mail address.
Comment 3 michael.ruess 2006-02-20 07:58:36 UTC
Reassigned to HI.
Comment 4 h.ilter 2006-02-20 09:55:34 UTC
HI->Aziem: Did you get an report id for your report? 
I can export the attachment on redhat and fedora without any problem.
Comment 5 aziem 2006-02-20 14:33:40 UTC
Created attachment 34324 [details]
stack trace on FC4---No, I didn't get an ID.
Comment 6 h.ilter 2006-02-20 15:22:16 UTC
HI->PL: Please take a look whether you can start to do something with the stack
from aziem
Comment 7 philipp.lohmann 2006-02-20 15:39:12 UTC
pl->hi: the stack trace ends somewhere in writer. If you find a way to reproduce
this, the fme will probably want to have a look at this. However i could not
reproduce the crash on my machine; then again i don't have FC4.
Comment 8 h.ilter 2006-02-22 09:30:43 UTC
HI->aziem: I've found many report of you but none for this issue. Can you
reproduce the crash to send us the crash report? Thanks. The attached stack
doesn't help.
Comment 9 aziem 2006-02-22 14:33:15 UTC
aziem->HI: I sent a new report with the fake address aziem62255@openoffice.org
Comment 10 aziem 2006-02-22 16:09:34 UTC
Created attachment 34382 [details]
Crash report from OOo 2.0.1 Windows 2000--also sent via crash tool
Comment 11 h.ilter 2006-02-23 15:13:47 UTC
HI->FME: Please have a look for the report-id: 1299041
Comment 12 frank.meies 2006-02-27 08:33:19 UTC
FME: Crashes when exporting as tagged pdf. Duplicate of internal 130940, fixed
in cws swqbf57.
Comment 13 frank.meies 2006-03-10 09:25:46 UTC
FME: Ready for QA.

re-open issue and reassign to mru@openoffice.org
Comment 14 frank.meies 2006-03-10 09:25:49 UTC
reassign to mru@openoffice.org
Comment 15 frank.meies 2006-03-10 09:25:54 UTC
reset resolution to FIXED
Comment 16 frank.meies 2006-03-10 09:26:44 UTC
.

re-open issue and reassign to hi@openoffice.org
Comment 17 frank.meies 2006-03-10 09:26:47 UTC
reassign to hi@openoffice.org
Comment 18 frank.meies 2006-03-10 09:26:51 UTC
reset resolution to FIXED
Comment 19 h.ilter 2006-03-15 11:11:53 UTC
Verified with cws swqbf57 = ok
Comment 20 h.ilter 2006-03-15 12:22:17 UTC
*** Issue 63193 has been marked as a duplicate of this issue. ***
Comment 21 h.ilter 2006-05-11 13:26:43 UTC
Verified with 680m168 = ok