Re: Bookworm CUPS Printing Revisited
On 5/17/23 15:11, Charles Curley wrote:
Thanks to Brian <ad44@cityscape.co.uk> on the thread "Re: CUPS on
Bullseye and Bookworm" I now have CUPS working on dragon, my bookworm
i386 architecture laptop.
Or I should say, CUPS printing is more or less working but something
else (GTK printing?) isn't. I can find the driverless printer on the
network, create a print queue for it, and print to it.
root@dragon:~# driverless
ipps://HP%20LaserJet%20MFP%20M234sdw%20(C0FB67)._ipps._tcp.local/
root@dragon:~# lpadmin -p M234 -v "ipps://HP%20LaserJet%20MFP%20M234sdw%20(C0FB67)._ipps._tcp.local/" -E -m everywhere
root@dragon:~# lp -d M234 /usr/share/cups/data/form_english.pdf
request id is M234-3 (1 file(s))
root@dragon:~# lp -d M234 /etc/nsswitch.conf
request id is M234-4 (1 file(s))
root@dragon:~#
So far, so good.
I have two problems:
1) I cannot print from abiword. abiword finds three printer queues:
print to file (which works), M234 (as previously set up), and
HP_Laserjet_MFP_M234dsw_COFB67. The two printer queues do not work. The
former see the printer light up, the "busy" indicator light up briefly,
then nothing. The latter evinces no action on the printer at all.
(I selected abiword rather than LibreOffice because LO is a bit of a
resource hog.)
2) When I print from the command line, I get results printing to M234.
But when I try printing to the other queue (directly to the printer as
I understand it), I see:
charles@dragon:~$ lp -d HP_Laserjet_MFP_M234dsw_C0FB67 ~/test.document.pdf
lp: Error - The printer or class does not exist.
charles@dragon:~$
I copied the printer name from abiword's list of available printers. Is
that the correct way to specify a driverless printer? I also tried
copying and pasting the ipps:// and dnssd:// printers shown by lpinfo
-v. Same error.
According to https://wiki.debian.org/CUPSDriverlessPrinting, "the GTK
print dialog on buster and before (firefox and evince, for example),
has its own way of dealing with a network printer. Unfortunately,
applications that print through this dialog do not make use of CUPS'
temporary queue formation. To have a queue for an IPP printer visible
and usable, users should manually set up a queue with lpadmin, the CUPS
web interface or system-config-printer or rely on cups-browsed to do it
for them. The situation on bullseye and later has improved." Regression?
I started this original thread because I could not get a bullseye client
to work with this bullseye server but buster clients worked fine.. For
me, the fix was something that can only be described as serendipity.
Apt had installed a newer kernel about a week back, probably a security
fix, but since my whole system is behind the best guard dog ever, dd-wrt
in my router, and I had just rebooted from an overnight freeze up, I
ignored its blabbing that I needed to reboot until I had another similar
freeze up Monday morning and had to reboot with the front panel reset
button. New kernel now running, bullseye server to bullseye client now
Just Works.
Not supposed to be snarky, but...
Couple folks rather pointedly asked if I ever read changelogs. But
before they can be read, they have to be found. I just spent 2 hours
with mc, punching f3 on changelog.gz's, trolling thru /usr/share/docs
w/o finding an entry for kernels. So where do I find this famous
changelog I'm supposed to read? Or are we becoming windoze, and its a
secret?
Since 1992, a truely complete changelog is quite likely several
terabytes so a URL link to a tail output would suffice.
Cheers, Gene Heskett.
--
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
- Louis D. Brandeis
Genes Web page <http://geneslinuxbox.net:6309/>
Reply to: