$ lpoptions -p colorprintertest -l | grep ColorModel The printer thinks it is BW by default, too: How does it get there, and why monochrome, if the PPD is CMYK by default? I see option `Option print-color-mode monochrome` is at the bottom for no apparent reason. # DO NOT EDIT THIS FILE WHEN CUPSD IS RUNNING
# Printer configuration file for CUPS v2.4.2 Look into /etc/cups/nf for the current printer options: $ grep DefaultColorModel /etc/cups/ppd/colorprintertest.ppdĢ. Make sure its DefaultColorModel was CMYK from the start: Sudo lpadmin -p colorprintertest -E -m openprinting-ppds:0/ppd/openprinting/Ricoh/PS/Ricoh-MP_C3004_PS.ppd -v socket://printerĢ. Create a new printer using a PPD that has `DefaultColorModel: CMYK`: So one of my problems sits in the upgraded system only ( and not on the plainly installed one ).Īnyway I need that printer and its colors - it’s a terrible bug.ĭebian testing/bookworm, CUPS 2.4.2-1, cups-filters 1.28.15-1+build1. I wonder : what are my best chances to reinstall 22.04 while keeping $HOMEs ?īecause when I try the same thing from the other installed system, it works as you describe ( but unable to print in colors, only B&W whatever set in printer driver. Plus some errors regarding nouveau driver, nothing new. Any help will be appreciated, please.In red : août 23 15:08:26 PROLIANT python3: io/hpmud/jd.c 772: invalid hostĪoût 23 15:08:26 PROLIANT python3: io/hpmud/jd.c 731: invalid ipĪoût 23 15:08:26 PROLIANT hp-makeuri: hp-makeuri: error: Device not foundĪoût 23 15:08:39 PROLIANT python3: io/hpmud/jd.c 94: unable to read device-idĪoût 23 15:08:39 PROLIANT python3: io/hpmud/jd.c 746: invalid ip 192.168.92.185Īoût 23 15:08:39 PROLIANT hp-makeuri: hp-makeuri: error: Device not foundĪoût 23 21:15:23 PROLIANT systemd: rvice: Failed with result 'exit-code'.Īoût 23 21:15:23 PROLIANT systemd: Failed to start Refresh fwupd metadata and update motd. As stated the problem is completely unique to Debian Bullseye and due to lack of knowledge and experience i am at a loss how I could resolve it. I have changed permissions and still get the same result. Whilst following this procedure in Debian 11 the interface stops any printing with an error message 'filter failed'. The workaround consists of adding an additional executable filter (called rasterlilo 2) to the cups/filter folder, configuring it for root read/write permissions, all others read-only and then adding the printer to cups and providing a ppd driver for Ricoh 221-pd which usually works 100% efficiently. The workaround works in Arch, Fedora, Slackware, Ubuntu, Mint, etc etc etc, but not Debian. I have an ancient Ricoh SP-211 laser printer which is not directly supported in Linux however there is a workaround which works 100% in any distribution whatsoever except Debian.
Love Debian, does everything I want except for one major issue.
0 kommentar(er)
