Bug 142273 - MAILMERGE: Printing to Letter stops at second letter, if letter contains a pagebreak
Summary: MAILMERGE: Printing to Letter stops at second letter, if letter contains a pa...
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
7.1.3.2 release
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-05-14 06:42 UTC by Robert Großkopf
Modified: 2021-05-18 06:42 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments
Extract the *.zip-file. Contains a Calcfile, a Basefile and two Writerfiles for testing. (39.27 KB, application/zip)
2021-05-14 06:42 UTC, Robert Großkopf
Details
FormLetter with internal Bibliography database. (8.49 KB, application/vnd.oasis.opendocument.text)
2021-05-17 11:21 UTC, Robert Großkopf
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Robert Großkopf 2021-05-14 06:42:28 UTC
Created attachment 171988 [details]
Extract the *.zip-file. Contains a Calcfile, a Basefile and two Writerfiles for testing.

This buggy behavior could be seen under OpenSUSE 15.2 64bit rpm Linux with LO 7.1.3.2. It doesn't appear with LO 7.0.5.2 on the same machine with the same userprofile.

Download the attached package.
Extract the *.zip-file.
Set "Mailmerge.odb" as database (Tools → Options → LibreOffice Base → Databases)
Open the document "Mailmerge_with_pagebreak.odt".
Hope it gets the database contact …
Start printing a form letter.
Choose File → Save as individual documents.
Press "OK".
Printing stops here while creating the second form letter.

Stop the printing.
Open the document "Mailmerge_without_pagebreak.odt".
Print it the same way. Will run without any problem.

Only difference between the two documents is the pagebreak.
Comment 1 Timur 2021-05-17 10:44:07 UTC
When reporting mail merge bugs, it's more convenient to use built-in database Bibliography. Please prepare such example.
Comment 2 Robert Großkopf 2021-05-17 11:21:52 UTC
Created attachment 172083 [details]
FormLetter with internal Bibliography database.

Removed example with external database and added a new example with the database bibliography, which is part of the LO-package.
Comment 3 Timur 2021-05-17 13:09:11 UTC
No repro with 7.1 and 7.2+ master, prints OK to files for example 3 records.
Please try to rename profile and test with AppImages.
I don't see how you have multiple LO on the same machine.
Comment 4 Robert Großkopf 2021-05-17 14:01:14 UTC
(In reply to Timur from comment #3)
> No repro with 7.1 and 7.2+ master, prints OK to files for example 3 records.
> Please try to rename profile and test with AppImages.

Don't know what AppImage should be. I resetted the profile, which works well with every installed LO here and started the attached file.
Pressed print and choose 3 rows of the data. Let write them down as separate letters.
The procedure stopped at the second letter.

In German mailinglist it seems to be a special bug with rpm-based Linux systems.

> I don't see how you have multiple LO on the same machine.

Download the packages from LO.
Extract to get all the *.rpms.
Move *.rpm into a folder.
Create a folder inside this folder ("install" for example).
Start
for i in ../*.rpm; do rpm2cpio $i | cpio -id; done
in this folder.
You get a special installation for one user.

There are 44 different versions at this moment in my home directory. I need this for testing all the bugs of Base see, since which version the bug appears first.
Comment 5 Timur 2021-05-17 14:29:23 UTC
AppImage is simple way to test multiple LO versions, from stable to master: https://libreoffice.soluzioniopen.com/daily-version/

I didn't reproduce with master on Mint. So maybe it's limited problem.
Comment 6 Robert Großkopf 2021-05-17 14:59:01 UTC
I also can't reproduce it with LO 7.2.0.0 Alpa from 2021-05-14. So it seems to be a special bug of the version LO 7.1.
Comment 7 QA Administrators 2021-05-18 04:16:58 UTC Comment hidden (obsolete)
Comment 8 Timur 2021-05-18 06:42:31 UTC
If you reproduce with AppImage 7.1 and not with 7.2+, then it's fixed bug, but we don't know where, so I mark WFM.
If you don't repro with AppImage 7.1, than it's more complicated, some local problem at yours, which doesn't justify a bug, until discovered.