Bug 71411 - PRINTING: Problem Printing Envelopes
Summary: PRINTING: Problem Printing Envelopes
Status: RESOLVED INVALID
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
3.5 all versions
Hardware: Other Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard: BSA
Keywords:
Depends on:
Blocks:
 
Reported: 2013-11-09 00:17 UTC by drsirucek
Modified: 2015-06-08 14:26 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:


Attachments
Scanned example of envelope that didn't print correctly (7.77 KB, application/pdf)
2013-11-09 00:17 UTC, drsirucek
Details
Envelope printed to PDF file in 4.4 alpha (14.30 KB, application/pdf)
2014-10-23 08:47 UTC, Buovjaga
Details

Note You need to log in before you can comment on or make changes to this bug.
Description drsirucek 2013-11-09 00:17:26 UTC
Created attachment 88915 [details]
Scanned example of envelope that didn't print correctly

Problem description: Left 1/2 of sender info is cut off. i.e. left 1/2 of my name and left 1/2 of address is all cut off. 

Steps to reproduce:
1. ....Create from and to portion of envelope in Libre
2. ....Insert
3. ....Print

Current behavior: Prints on envelope but is missing the entire left 1/2 of the senders information. 

Expected behavior: Should print senders information correctly.

              
Operating System: Ubuntu
Version: 3.5 all versions
Comment 1 Buovjaga 2014-10-23 08:47:53 UTC
Created attachment 108290 [details]
Envelope printed to PDF file in 4.4 alpha

I don't get cut off text.
Have you tried with 4.3?

Version used for test: 4.4.0.0.alpha1+
Build ID: a8c24b25fd9fb21097a08a22797bf61b59099ea1
TinderBox: Win-x86@39, Branch:master, Time: 2014-10-21_06:33:33
Comment 2 A (Andy) 2014-10-24 18:59:28 UTC
Which kind of envelope have you selected in FORMAT -> PAGE -> tab PAGE -> Paper Format?
Comment 3 tommy27 2014-10-27 19:55:57 UTC
please tell us the printer model too. any chance it is a Brother printer?
Comment 4 QA Administrators 2015-05-06 14:15:06 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/Bugzilla/Fields/Status/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 5 QA Administrators 2015-06-08 14:26:47 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

-- The LibreOffice QA Team 

This INVALID Message was generated on: 2015-05-06

Warm Regards,
QA Team