Bug 44229 - VIEWING Crash on serial letter with data navigator shown and switch to preview
Summary: VIEWING Crash on serial letter with data navigator shown and switch to preview
Status: RESOLVED DUPLICATE of bug 44040
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
3.5.0 Beta2
Hardware: x86 (IA32) Windows (All)
: medium major
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-12-28 10:19 UTC by libreoffice2
Modified: 2011-12-28 12:00 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments
Serial letter which cause the crash (8.79 KB, application/vnd.oasis.opendocument.text)
2011-12-28 10:19 UTC, libreoffice2
Details
Crash report (277.28 KB, text/plain)
2011-12-28 10:20 UTC, libreoffice2
Details

Note You need to log in before you can comment on or make changes to this bug.
Description libreoffice2 2011-12-28 10:19:24 UTC
Created attachment 54910 [details]
Serial letter which cause the crash

hello together,

the attached letter contains some parts of a serial letter. The data source is the biblio-database. If you now switch on the data explorer (Press F4) and then go to File -> Preview libreoffice crashed. It happens every time. I will attach the letter and also the crashreport from dr. watson.

cheers,
hitzi
Comment 1 libreoffice2 2011-12-28 10:20:21 UTC
Created attachment 54911 [details]
Crash report
Comment 2 libreoffice2 2011-12-28 11:05:27 UTC
same on LibreOffice 3.4.4 (OOO340m1 Build:402)
Comment 3 libreoffice2 2011-12-28 11:49:52 UTC
Ok I have done some further tests and the crash is indepedent on the serial letter. The crash occurs also when you follow the described steps:
Open a new document 
Press F4 (for data explorer)
Go on File --> Preview
--> Crash
Comment 4 Rainer Bielefeld Retired 2011-12-28 12:00:53 UTC
Known problem from "Bug 44040 - VIEWING: Crash when page preview after <f4> (data sources)"

@libreoffice@internetists.de
Thank you for your attention!

*** This bug has been marked as a duplicate of bug 44040 ***