On Sat, 27 Jun 2015 22:16:54 +0100
Brian <a...@cityscape.co.uk> wrote:
> On Sat 27 Jun 2015 at 14:03:00 -0700, bri...@aracnet.com wrote:
>
> People upgrading from a *working* Wheezy cups have generally not noticed
> any change in their printing experience.
>
>
the upgrade went very well as has always been my experience with Debian :-)
so things are still strange.
upon re-boot the ipp connection set-up did work BUT ONLY FOR ICEWEASEL.
evince can see the printer but can't print because:
Returning IPP client-error-bad-request for Print-Job
(ipp://192.168.1.1:631/printers/Brother_DCP-8110DN) from 192.168.1.40
libreoffice writer can't see the printer at all.
So i went back in to cups administration and found my good friend :
dnssd://Brother%20DCP-8110DN._ipp._tcp.local/
which is the working connection i had before. it decided to show up when it
wouldn' before, possibly related to libavahi ?
so here's where it gets weird. i selected the dnssd printer connection. i
restarted cups and cups-browsed (do i need cups-browsed ?) and then tried
evince again, but i still get the same message:
Returning IPP client-error-bad-request for Print-Job
(ipp://192.168.1.1:631/printers/Brother_DCP-8110DN) from 192.168.1.40
why am i getting ipp in the error log when i've switched to the dnssd
connection ???
it looks like evince is still getting the old printer advertisement, or
something...
of course- how these apps are actually retrieving the printer interface is a
great mystery. i'm assuming they are built with some sort of cups access
library ?
Brian
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20150627181540.49c8e...@cedar.deldotd.com
