Bug 83853 - Other: Printing from File>Labels fails without error message
Summary: Other: Printing from File>Labels fails without error message
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version: 4.2.6.2 release
Hardware: Other All
: medium normal
Assignee: Not Assigned
QA Contact:
URL:
Whiteboard: BSA
Keywords:
Depends on:
Blocks:
 
Reported: 2014-09-14 17:12 UTC by Martin Thomas
Modified: 2015-01-03 17:39 UTC (History)
3 users (show)

See Also:
i915 platform:
i915 features:


Attachments

Description Martin Thomas 2014-09-14 17:12:53 UTC
Problem description: Printing from File>Labels produces no output. This is equally true if the option to print output to file is selected (i.e. it's isn't a printer problem with us).

There is no error message and the program appears to function normally (e.g. it prompts for a filename for the output in print-to-file and for a folder into which to save the output)... only, there's no output.

We have this bug currently on LibreOffice 4.2.6.3 on three different Arch Linux machines. Printing still works on LibreOffice 4.2.4.2 on a Mac in our office running OS 10.6.8.

We had this same problem some months back and reported it on the LibreOffice forums. There was some discussion there, but nothing which helped resolve the problem. The problem cleared up then as mysteriously as it had appeared.

We hoped that it was fixed by an update in LibreOffice, but evidently not.

This time, the bug first appeared on a machine which the same day, only an hour or so before, with the same version of LibreOffice, and without any intervening restart or anything, had printed ok. It would appear not to be a new bug in 4.2.6.3, but maybe a longstanding but erratic bug.

Steps to reproduce:
1. Open a database in LibreOffice
2. Select File>Labels and use already-existing format for labels
3. Click on New Document
4. Choose print.

Current behavior: As above, everything appears fine except that there is no output (not even if we select print-to-file).

Expected behavior: To get output.

              
Operating System: Linux (Other)
Version: 4.2.6.2 release
Comment 1 robert 2014-09-14 17:49:05 UTC
Have tried to start to edit labels (file → open → labels). Only worked the first time I tried. Then the wizard crashes the whole LO while creating the new document. Tested with LO 4.2.6.3 and LO 4.3.2.1. System here: OpenSUSE 64bit rpm Linux.
The first time I got a document. This could be printed well ...
Comment 2 Philippe Morin 2014-11-14 22:27:17 UTC
I also have this problem!
Comment 3 Philippe Morin 2014-11-14 22:28:58 UTC
(In reply to Philippe Morin from comment #2)
> I also have this problem!

I use 4.2.7.2 on Mac OS X 10 (Yosemite)
Comment 4 Alex Thurgood 2014-12-17 13:40:37 UTC
Tested with

Version: 4.3.3.1
Build ID: 7d55112667c8fcddb67bc3803796b46c93aa56b0

OSX 10.10.1

1) Open a database file.
2) File - New - Labels
3) Choose pre-existing format (I chose Avery A4)
4) Click on New Document
5) Now try to print document to printer (Kyocera networked FS C5150 DN)
6) Printing fails with printer error message requesting insertion of Monarch size envelope in Manual Paper feed.

Observations : the page attribute is set to User 10cm x 10cm, which is clearly wrong, as per my choice it should have been A4.

This is not imho a database issue, rather a Writer module issue. Changing component accordingly and confirming.
Comment 5 Alex Thurgood 2014-12-17 14:01:19 UTC
It is also probably a DUP
Comment 6 Alex Thurgood 2014-12-17 15:15:30 UTC
DUP not found after brief search
Comment 7 Steve Saus 2014-12-18 03:51:51 UTC
This "workaround" worked:


1. Set up your merged document. 
2. **Save the set up document without trying to merge it**
3. Close all LibreOffice applications.  Kill the daemon if you have it running (I don't).
4. Re-open your set-up document.  It will ask you if you wish to reconnect to sources.  Answer *yes*.
5. Print.

Things that did NOT seem to make a difference:
1. Saving the document without closing and reopening LO before attempting mail merge.
2. Rebooting the PC.

The key seems to be in the reconnecting to the source, if that helps y'all figure out where the bug is, that'd be awesome.
Comment 8 Alex Thurgood 2015-01-03 17:39:18 UTC
Adding self to CC if not already on


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.