Bug 146666 - Writer: Duplex print not working with HP LaserJet 1320
Summary: Writer: Duplex print not working with HP LaserJet 1320
Status: RESOLVED INSUFFICIENTDATA
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
7.2.4.1 release
Hardware: x86-64 (AMD64) Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-01-09 13:52 UTC by Blandyna
Modified: 2023-07-03 03:12 UTC (History)
2 users (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 Blandyna 2022-01-09 13:52:57 UTC
Description:
Duplex print in Writer not working as duplex. The pages were rotated, but nod printed on the back side. 
I wanted to print 4 sites with duplex = 2 pages paper. After the print I had 4 pages paper. 

Printer: HP LaserJet 1320 with duplex.

Writer: 7.2.5.2

Steps to Reproduce:
1. Document in Writer with more than 1 page.
2. CTRL + P: Duplex on long side.
3.

Actual Results:
Duplex not wirking.

Expected Results:
Duplex is working.


Reproducible: Always


User Profile Reset: No


OpenGL enabled: Yes

Additional Info:
Version: 7.2.5.2 (x64) / LibreOffice Community
Build ID: 499f9727c189e6ef3471021d6132d4c694f357e5
CPU threads: 6; OS: Windows 10.0 Build 19043; UI render: Skia/Vulkan; VCL: win
Locale: de-DE (de_DE); UI: de-DE
Calc: threaded
Comment 1 Timur 2022-01-15 15:09:48 UTC
Did it work before, with which version? If so, it would a new bug,
Otherwise, seems duplicate of bug 60428.
Comment 2 Blandyna 2022-01-15 15:47:44 UTC
I haven't the previous version of LibreOffice. Sorry.
Comment 3 Telesto 2022-01-16 09:47:00 UTC
No issue with my Epson Workforce
Version: 7.4.0.0.alpha0+ (x64) / LibreOffice Community
Build ID: 628fedabdd27ad08e9a42f47106864751e493c2c
CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: Skia/Raster; VCL: win
Locale: nl-NL (nl_NL); UI: en-US
Calc: CL
Comment 4 sockseight 2022-12-03 11:29:51 UTC
Hello Blandvna,

Thank you for reporting the bug.
it seems you're using an old version of LibreOffice.
Could you please try to reproduce it with the latest version of LibreOffice
from https://www.libreoffice.org/download/libreoffice-fresh/ ?

I have set the bug's status to 'NEEDINFO'. Please change it back to
'UNCONFIRMED' if the bug is still present in the latest version.

If the issue is still seen please clarify the following,

Please attach a sample document, as this makes it easier for us to verify the bug. 

I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' once the requested document is provided.

IMPORTANT!!
(Please note that the attachment will be public, remove any sensitive information before attaching it. 
See https://wiki.documentfoundation.org/QA/FAQ#How_can_I_eliminate_confidential_data_from_a_sample_document.3F for help on how to do so.)
Comment 5 QA Administrators 2023-06-02 03:17:04 UTC Comment hidden (obsolete)
Comment 6 QA Administrators 2023-07-03 03:12:10 UTC
Dear Blandyna,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INSUFFICIENTDATA 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

MassPing-NeedInfo-FollowUp