Bug 73425 - Printing a mail merge document crashes Libreoffice
Summary: Printing a mail merge document crashes Libreoffice
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
4.1.3.2 release
Hardware: Other All
: medium major
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-01-09 08:45 UTC by Sebastian@SSpaeth.de
Modified: 2015-01-24 12:15 UTC (History)
0 users

See Also:
Crash report or crash signature:


Attachments
Mail Merge document which crashes Libreoffice (16.75 KB, application/vnd.oasis.opendocument.text)
2014-01-09 08:45 UTC, Sebastian@SSpaeth.de
Details
Underlying data for the mail merge (11.90 KB, application/vnd.oasis.opendocument.spreadsheet)
2014-01-09 08:45 UTC, Sebastian@SSpaeth.de
Details
Database providing the mail merge query.... (1.73 KB, application/vnd.oasis.opendocument.database)
2014-01-09 08:46 UTC, Sebastian@SSpaeth.de
Details
Mail Merge document which crashes Libreoffice (15.32 KB, application/vnd.oasis.opendocument.text)
2014-01-09 08:54 UTC, Sebastian@SSpaeth.de
Details
added backtrace of the crash (48.43 KB, text/x-log)
2014-01-09 09:18 UTC, Sebastian@SSpaeth.de
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Sebastian@SSpaeth.de 2014-01-09 08:45:14 UTC
Created attachment 91739 [details]
Mail Merge document which crashes Libreoffice

Attaching 3 files, one Sheet with data, one .odb providing the database source, and one MailMerge.odt. Opening MailMerge.odt and selecting "print" leads to the dialogue: "This document contains form fields, do you want to print a mail merge letter" (or similar wording). Select yes, and hit print in the resulting dialogue. Instant crash. It does not matter if you print "to file" or only print a subset of rows, it will always crash. There is no console output at all.

The same document used to print fine in earlier versions of Libreoffice (not sure which was the last working one though).
Comment 1 Sebastian@SSpaeth.de 2014-01-09 08:45:50 UTC
Created attachment 91740 [details]
Underlying data for the mail merge
Comment 2 Sebastian@SSpaeth.de 2014-01-09 08:46:21 UTC
Created attachment 91741 [details]
Database providing the mail merge query....
Comment 3 Sebastian@SSpaeth.de 2014-01-09 08:54:31 UTC
Created attachment 91742 [details]
Mail Merge document which crashes Libreoffice

Updated document, removing address data which should not have been made public
Comment 4 Sebastian@SSpaeth.de 2014-01-09 09:18:27 UTC
Created attachment 91743 [details]
added backtrace of the crash
Comment 5 retired 2014-01-10 11:36:00 UTC
Hi Sebastian,

Is this bug still valid / reproducible with the latest pre-release 4.2.0.1: http://www.libreoffice.org/download/pre-releases/

Please also try resetting your user profile and let us know if that helps: https://wiki.documentfoundation.org/UserProfile

Should this be still reproducible for you with the latest LO release please set this bug back to UNCONFIRMED. Should this issue be solved set it to WORKSFORME.

Setting to NEEDINFO until more detail is provided.
Comment 6 QA Administrators 2014-08-04 16:17:40 UTC
Dear Bug Submitter,

This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INVALID due to lack of needed information.

For more information about our NEEDINFO policy please read the wiki located here: 
https://wiki.documentfoundation.org/QA/FDO/NEEDINFO

If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed.


Thank you for helping us make LibreOffice even better for everyone!


Warm Regards,
QA Team
Comment 7 Sebastian@SSpaeth.de 2014-08-05 15:59:26 UTC
Just tried this in 4.3 (on Windows, as I don`t have the Linux box where I experienced the issue is not available right now), and it worked. So closing. I will reopen when I re-experience this on Linux.