Whenever I try to print from Okular, a box with this message appears: There are conflicts in duplex settings. Do you want to fix them? And printing is in fact funky: the options for double sided printing: Okular->Print->Options are strange. The option "Long Side Printing" is selected (though greyed out); the option "Off" is selectable, but if selected, no other option can be selected afterward. Firefox doesn't allow control of duplex printing using its native print dialog, but duplex can be controlled using the system dialog.
Does anyone know what's going on or how to fix it.
Printer: HP Color Laserjet M255dw
Cups Version: cups-2.4.2-4.fc36.x86_64
System Info: Operating System: Fedora Linux 36 KDE Plasma Version: 5.25.4 KDE Frameworks Version: 5.97.0 Qt Version: 5.15.5 Kernel Version: 5.19.4-200.fc36.x86_64 (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-4790K CPU @ 4.00GHz Memory: 15.5 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 4600 Manufacturer: ASUS
Am 30.08.22 um 16:14 schrieb Jonathan Ryshpan:
Whenever I try to print from Okular, a box with this message appears: There are conflicts in duplex settings. Do you want to fix them? And printing is in fact funky: the options for double sided printing: Okular->Print->Options are strange. The option "Long Side Printing" is selected (though greyed out); the option "Off" is selectable, but if selected, no other option can be selected afterward. Firefox doesn't allow control of duplex printing using its native print dialog, but duplex can be controlled using the system dialog.
Does anyone know what's going on or how to fix it.
Printer: HP Color Laserjet M255dw
Cups Version: cups-2.4.2-4.fc36.x86_64
No such problem with a may be similar device: HP Color Laserjet MFP M277dw (in contradiction to yours, it's a multifunction printer, as the name implies).
In Okular's printing dialogue, "off" is selected in double side printing, but I can select long/short side binding (and it works). So, I am sorry to say that I don't know how to fix your problem :-( Yours Klaus-Peter
Operating System: Fedora Linux 36 KDE Plasma Version: 5.25.4 KDE Frameworks Version: 5.96.0 Qt Version: 5.15.5 Kernel Version: 5.18.16-200.fc36.x86_64 (64-bit) Graphics Platform: X11
On Tue, 2022-08-30 at 07:14 -0700, Jonathan Ryshpan wrote:
Whenever I try to print from Okular, a box with this message appears: There are conflicts in duplex settings. Do you want to fix them? And printing is in fact funky: the options for double sided printing: Okular->Print->Options are strange. The option "Long Side Printing" is selected (though greyed out); the option "Off" is selectable, but if selected, no other option can be selected afterward. Firefox doesn't allow control of duplex printing using its native print dialog, but duplex can be controlled using the system dialog.
Does anyone know what's going on or how to fix it.
Printer: HP Color Laserjet M255dw
Cups Version: cups-2.4.2-4.fc36.x86_64
System Info: Operating System: Fedora Linux 36 KDE Plasma Version: 5.25.4 KDE Frameworks Version: 5.97.0 Qt Version: 5.15.5 Kernel Version: 5.19.4-200.fc36.x86_64 (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-4790K CPU @ 4.00GHz Memory: 15.5 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 4600
I tried running $ hp-check --run which appears to be largely undocumented, and which produced the following errors. The list looks very strange. Does anyone know what's going on? The entire output is attached as hp-check.log .
----------- | SUMMARY | -----------
Missing Required Dependencies ----------------------------- error: 'cups' package is missing or 'cups' service is not running. error: 'libjpeg-devel' package is missing/incompatible error: 'cups-devel' package is missing/incompatible error: 'cups-devel' package is missing/incompatible error: 'libusb1-devel' package is missing/incompatible error: 'sane-backends-devel' package is missing/incompatible error: 'avahi-devel' package is missing/incompatible error: 'net-snmp-devel' package is missing/incompatible error: 'python3-devel' package is missing/incompatible error: 'libtool' package is missing/incompatible error: 'rpm-build' package is missing/incompatible
Missing Optional Dependencies ----------------------------- error: 'polkit' package is missing/incompatible error: 'polkit-gnome' package is missing/incompatible error: 'PKG_FROM_PIP:notify2' package is missing/incompatible
Total Errors: 12 Total Warnings: 0
Am 05.09.22 um 23:11 schrieb Jonathan Ryshpan:
On Tue, 2022-08-30 at 07:14 -0700, Jonathan Ryshpan wrote:
Whenever I try to print from Okular, a box with this message appears: There are conflicts in duplex settings. Do you want to fix them? And printing is in fact funky: the options for double sided printing: Okular->Print->Options are strange. The option "Long Side Printing" is selected (though greyed out); the option "Off" is selectable, but if selected, no other option can be selected afterward. Firefox doesn't allow control of duplex printing using its native print dialog, but duplex can be controlled using the system dialog.
Does anyone know what's going on or how to fix it.
Printer: HP Color Laserjet M255dw
Cups Version: cups-2.4.2-4.fc36.x86_64
System Info: Operating System: Fedora Linux 36 KDE Plasma Version: 5.25.4 KDE Frameworks Version: 5.97.0 Qt Version: 5.15.5 Kernel Version: 5.19.4-200.fc36.x86_64 (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-4790K CPU @ 4.00GHz Memory: 15.5 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 4600
I tried running $ hp-check --run which appears to be largely undocumented, and which produced the following errors. The list looks very strange. Does anyone know what's going on? The entire output is attached as hp-check.log .
| SUMMARY |
Missing Required Dependencies
error: 'cups' package is missing or 'cups' service is not running. error: 'libjpeg-devel' package is missing/incompatible error: 'cups-devel' package is missing/incompatible error: 'cups-devel' package is missing/incompatible error: 'libusb1-devel' package is missing/incompatible error: 'sane-backends-devel' package is missing/incompatible error: 'avahi-devel' package is missing/incompatible error: 'net-snmp-devel' package is missing/incompatible error: 'python3-devel' package is missing/incompatible error: 'libtool' package is missing/incompatible error: 'rpm-build' package is missing/incompatible
Missing Optional Dependencies
error: 'polkit' package is missing/incompatible error: 'polkit-gnome' package is missing/incompatible error: 'PKG_FROM_PIP:notify2' package is missing/incompatible
Total Errors: 12 Total Warnings: 0
FWIW, hp-check gives me just the same errors about missing dependencies (some details in the log are different because my device HP Color LaserJet MFP M277dw includes scanning). So these messages are probably useless in your case - as far as I understand it, those dependencies are essential if you want to BUILD the hp libraries.
Interesting enough, hp-toolbox tells me that no hp devices can be found, although I definitely can use my printer/scanner. I found that my printer uses "driverless printing" through "IPP Everywhere". So you might investigate further in this direction: https://docs.fedoraproject.org/en-US/quick-docs/cups-useful-tricks/
On Tue, 2022-09-06 at 12:36 +0200, Klaus-Peter Schrage wrote:
FWIW, hp-check gives me just the same errors about missing dependencies (some details in the log are different because my device HP Color LaserJet MFP M277dw includes scanning). So these messages are probably useless in your case - as far as I understand it, those dependencies are essential if you want to BUILD the hp libraries.
This looks very reasonable, except for the message
error: 'cups' package is missing or 'cups' service is not running.
Cups certainly seems to be running on my system $ systemctl status cups.service ● cups.service - CUPS Scheduler Loaded: loaded (/usr/lib/systemd/system/cups.service; disabled; vendor preset: disabled) Active: active (running) since Tue 2022-09-06 19:08:56 PDT; 15min ago Very mysterious...
Interesting enough, hp-toolbox tells me that no hp devices can be found, although I definitely can use my printer/scanner. I found that my printer uses "driverless printing" through "IPP Everywhere". So you might investigate further in this direction: https://docs.fedoraproject.org/en-US/quick-docs/cups-useful-tricks/
hp-toolbox finds my printer without any trouble, not in the console message but in the GUI.
It's not clear what cups-useful-tricks is about; there seems to be unstated context. In any case the HP-M255dw is not capable of driverless operation:
$ sudo lsusb -v ... Bus 003 Device 004: ID 03f0:0a70 HP, Inc HP ColorLaserJet M255-M256 Device Descriptor: ... bInterfaceClass 7 Printer bInterfaceSubClass 1 Printer bInterfaceProtocol 2 Bidirectional
The web page indicates that bInterfaceProtocol must be 4 for the printer to be capable of driverless operation. So it looks like the document is not relevant to my situation. However I did install ipp-usb (and reboot), however without any apparent result.
On Tue, Aug 30, 2022 at 11:14 AM Jonathan Ryshpan jonrysh@pacbell.net wrote:
Whenever I try to print from Okular, a box with this message appears: There are conflicts in duplex settings. Do you want to fix them? And printing is in fact funky: the options for double sided printing: Okular->Print->Options are strange. The option "Long Side Printing" is selected (though greyed out); the option "Off" is selectable, but if selected, no other option can be selected afterward. Firefox doesn't allow control of duplex printing using its native print dialog, but duplex can be controlled using the system dialog.
Does anyone know what's going on or how to fix it.
Printer: HP Color Laserjet M255dw
HP "specs" say it has USB as well as wired or wireless network printing and that it supports Apple Airprint.
Which communications interface are are you using?
Airprint comes from IPP, which is the current "driverless" network protocol used by CUPS (from when CUPS was an Apple project). There are drivers that make USB look like IPP, but I assume those are printer-specific. Airprint may diverge from IPP in the future, but HP's specs say this model works with older macOS versions, so should support CUPS driverless printing for ethernet and wifi.
For USB, see https://github.com/OpenPrinting/ipp-usb. The "Issues" section has examples of troubleshooting on linux:
Thanks very much. On Tue, 2022-09-06 at 08:07 -0300, George N. White III wrote:
HP "specs" say it has USB as well as wired or wireless network printing and that it supports Apple Airprint.
Which communications interface are are you using?
USB.
Airprint comes from IPP, which is the current "driverless" network protocol used by CUPS (from when CUPS was an Apple project). There are drivers that make USB look like IPP, but I assume those are printer-specific. Airprint may diverge from IPP in the future, but HP's specs say this model works with older macOS versions, so should support CUPS driverless printing for ethernet and wifi.
For USB, see https://github.com/OpenPrinting/ipp-usb.%C2%A0 The "Issues" section has examples of troubleshooting on linux:
So there are, but none of them seems to have much to do with my situation.
On Tue, Sep 6, 2022 at 11:46 PM Jonathan Ryshpan jonrysh@pacbell.net wrote:
For USB, see https://github.com/OpenPrinting/ipp-usb. The "Issues" section has examples of troubleshooting on linux:
So there are, but none of them seems to have much to do with my situation.
The problems/printer models aren't the same, but some of the troubleshooting methods could help pin down the problem. One reason troubleshooting IPP-USB is hard (quoting the README):
Unfortunately, the naive implementation, which simply relays a TCP connection to USB, does not work. It happens because closing the TCP connection on the client side has a useful side effect of discarding all data sent to this connection from the server side, but it does not happen with USB connections. In the case of USB, all data not received by the client will remain in the USB buffers, and the next time the client connects to the device, it will receive unexpected data, left from the previous abnormally completed request.
Actually, it is an obvious flaw in the IPP-over-USB standard, but we have to live with it. The easy workaround would be to switch to a network connection. Opening an issue on the ipp-usb github site takes effort, but could be a useful contribution to the community.
On Wed, 2022-09-07 at 08:32 -0300, George N. White III wrote:
On Tue, Sep 6, 2022 at 11:46 PM Jonathan Ryshpan jonrysh@pacbell.net wrote:
For USB, see https://github.com/OpenPrinting/ipp-usb.%C2%A0 The "Issues" section has examples of troubleshooting on linux:
So there are, but none of them seems to have much to do with my situation.
The problems/printer models aren't the same, but some of the troubleshooting methods could help pin down the problem. One reason troubleshooting IPP-USB is hard (quoting the README): Unfortunately, the naive implementation, which simply relays a TCP connection to USB, does not work. It happens because closing the TCP connection on the client side has a useful side effect of discarding all data sent to this connection from the server side, but it does not happen with USB connections. In the case of USB, all data not received by the client will remain in the USB buffers, and the next time the client connects to the device, it will receive unexpected data, left from the previous abnormally completed request. Actually, it is an obvious flaw in the IPP-over-USB standard, but we have to live with it. The easy workaround would be to switch to a network connection. Opening an issue on the ipp-usb github site takes effort, but could be a useful contribution to the community.
This implies that cups needs to communicate with the printer to find out something (say whether the printer has duplex capability), but can't because of communication issues which would be solved if IPP-USB were working properly. A test would be to change the connection to the printer from USB to TCP/IP, i.e. I should disconnect USB, attach Ethernet on the printer, set up the printer for Ethernet and see what happens. Is all this correct?
I suspect that ipp-usb is not going to help because the HP m255dw printer doesn't seem to be supported: # ipp-usb check Configuration files: OK No IPP over USB devices found
On Wed, Sep 7, 2022 at 10:38 AM Jonathan Ryshpan jonrysh@pacbell.net wrote:
On Wed, 2022-09-07 at 08:32 -0300, George N. White III wrote:
On Tue, Sep 6, 2022 at 11:46 PM Jonathan Ryshpan jonrysh@pacbell.net wrote:
For USB, see https://github.com/OpenPrinting/ipp-usb. The "Issues" section has examples of troubleshooting on linux:
So there are, but none of them seems to have much to do with my situation.
The problems/printer models aren't the same, but some of the troubleshooting methods could help pin down the problem. One reason troubleshooting IPP-USB is hard (quoting the README):
Unfortunately, the naive implementation, which simply relays a TCP connection to USB, does not work. It happens because closing the TCP connection on the client side has a useful side effect of discarding all data sent to this connection from the server side, but it does not happen with USB connections. In the case of USB, all data not received by the client will remain in the USB buffers, and the next time the client connects to the device, it will receive unexpected data, left from the previous abnormally completed request.
Actually, it is an obvious flaw in the IPP-over-USB standard, but we have to live with it. The easy workaround would be to switch to a network connection. Opening an issue on the ipp-usb github site takes effort, but could be a useful contribution to the community.
This implies that cups needs to communicate with the printer to find out something (say whether the
printer has duplex capability), but can't because of communication issues
which would be solved if
IPP-USB were working properly.
In addition to getting printer capabilities, CUPS needs to send setup data (e.g., non-duplex request) to the printer followed by the print data. The problem for troubleshooting with USB is that some cleanup is needed after a failed job/test.
A test would be to change the connection to the printer from USB to TCP/IP,
i.e. I should disconnect USB,
attach Ethernet on the printer, set up the printer for Ethernet and see
what happens. Is all this correct?
TCP/IP is used on ethernet cables and WiFi. Ethernet generally requires a router with DHCP. Typical home internet these days provides a combined modem/router with both wifi and ethernet, so if you are using wfi you might have to move the printer close enough to the router to connect ethernet.
Wireless is also supported by your printer. Apple Airprint was invented to allow iPhone and iPad users to print directly to a printer, This makes my partner (and the stores that provide printer supplies!) very happy. Use whatever your network provides.
I suspect that ipp-usb is not going to help because the HP m255dw printer doesn't seem to be supported: # ipp-usb check Configuration files: OK No IPP over USB devices found
It is possible that HP has some special sauce for USB printing, but to be certain you probably need the help of the ipp-usb exports via their github Issues.