Bug 77438 - DUPLEX PRINT
Summary: DUPLEX PRINT
Status: RESOLVED INVALID
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
4.2.3.3 release
Hardware: Other Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-04-14 15:29 UTC by Leo Seghers
Modified: 2015-02-11 20:02 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Leo Seghers 2014-04-14 15:29:59 UTC
I've this DUPLEX problem.
With an HP Officejet Pro 8600 - Plus Printer, using driver HPLIP-3.14.4.
I'm using Ubuntu 13.10 - 64 Bit and LibreOffice 4.2.3.3. - Writer.
When I use the same document in "Abiword", then the DUPLEX fonction works.
When will it be finally solved?
Comment 1 Joel Madero 2014-06-05 03:40:02 UTC
We need more information from you - 

1) what print dialogs are you using? native or LibreOffice dialogs? 
- to find out go into tools -> options -> General and look to see if the Use LibreOffice dialogs is checked

2) Is this a new problem? Did it work with any older version of LibreOffice

3) Do you go into properties and turn on duplex printing? 
- File -> Print -> Choose printer, click properties and check to see if duplex is selected and on (or tell us if it's grayed out).


As to your question for "when will it be fixed" - you're more than welcome to submit a patch to fix it. We are an open source project largely built by volunteers, if a volunteer chooses to accept the bug (after it's accepted) it will get fixed. Another option is to fund a developer to resolve the problem.

Marking as NEEDINFO - once you provide the requested information as UNCONFIRMED.
Please don't respond via email - respond directly on the bug.
Comment 2 Joel Madero 2014-06-05 03:41:05 UTC
BTW - I can print duplex just fine on HP Photosmart 1115
Comment 3 QA Administrators 2015-01-10 18:06:53 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

Message generated on: 10/01/2015
Comment 4 QA Administrators 2015-02-11 19:55:36 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 FDO

Message generated on: 2015-02-11
Comment 5 QA Administrators 2015-02-11 20:02:04 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 FDO
Message generated on: 2015-02-11