Bug 91169 - Envelope prints with black background
Summary: Envelope prints with black background
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
(earliest affected)
Hardware: Other macOS (All)
: medium major
Assignee: Not Assigned
Depends on:
Reported: 2015-05-08 17:29 UTC by R Unkefer
Modified: 2016-05-09 20:07 UTC (History)
4 users (show)

See Also:
Crash report or crash signature:

Scan of black background envelope (31.84 KB, image/jpeg)
2015-05-08 17:29 UTC, R Unkefer

Note You need to log in before you can comment on or make changes to this bug.
Description R Unkefer 2015-05-08 17:29:50 UTC
Created attachment 115454 [details]
Scan of black background envelope

The pulldown menu did not give me the correct choices, so am including them here:

MacBook Air, 1.4 GHz Intel Core i5, OSX 10.10.3
LibreOffice Version:
Build ID: c4c7d32d0d49397cad38d62472b0bc8acff48dd

Printer: Brother MFC-J470DW

1. Insert #10 envelope using wizard, type in address
2. Prints text box with address ok, all the rest of the envelope black (see attached scan)
3. New document: same address box on letter-sized paper, portrait orientation, everything fine
4. Change page size to #10 envelope, landscape, prints black again
5. New document, letter size
6. Change page size manually to 9.5" by 4.13", prints black again

Finally gave up and printed the address on a label.
Comment 1 A (Andy) 2015-05-08 18:03:26 UTC
For me not reproducible with LO, Win 8.1
Comment 2 Alex Thurgood 2015-05-09 14:05:47 UTC
Please provide more details as to how you configure your page settings when using the envelope wizard.

I don't get any black printing like in your screenshot, but a paper jam instead, on Samsung CLX-3170 FXN laser network printer.

The paper jam for me is caused by the wrong page size being sent to the printer, but this is a probably different problem from the one you are experiencing here.

This will need someone with Mac OSX and the Brother printer you are using to test.

Tested on OSX 10.10.3 with 

Build ID: 3ffed8635acd55a5989bf9a0f4bc9c20b0acd945
Locale : fr-FR (fr.UTF-8)
Comment 3 Buovjaga 2015-06-25 19:13:59 UTC
NEEDINFO per comment 2.
Comment 4 QA Administrators 2015-12-27 20:30:48 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:

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 5 QA Administrators 2016-05-09 20:07:18 UTC
Dear Bug Submitter,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INVALID due to inactivity and
a lack of information which is needed in order to accurately
reproduce and confirm the problem. We encourage you to retest
your bug against the latest release. If the issue is still
present in the latest stable release, we need the following
information (please ignore any that you've already provided):

a) Provide details of your system including your operating
   system and the latest version of LibreOffice that you have
   confirmed the bug to be present

b) Provide easy to reproduce steps – the simpler the better

c) Provide any test case(s) which will help us confirm the problem

d) Provide screenshots of the problem if you think it might help

e) Read all comments and provide any requested information

Once all of this is done, please set the bug back to UNCONFIRMED
and we will attempt to reproduce the issue. Please do not:

a) respond via email 

b) update the version field in the bug or any of the other details
   on the top section of our bug tracker

Warm Regards,
QA Team

This INVALID Message was generated on: 2016-05-09