[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#714323: marked as done (HP Laserjet 8150N: PPD doesn't really control printer)

Your message dated Sat, 11 Nov 2017 12:40:18 +0000
with message-id <11112017123840.303aca08a090@desktop.copernicus.org.uk>
and subject line Re: Bug#714323: HP Laserjet 8150N: PPD doesn't really control printer
has caused the Debian Bug report #714323,
regarding HP Laserjet 8150N: PPD doesn't really control printer
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
714323: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=714323
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: printer-driver-postscript-hp
Version: 3.13.4-1

Hi!

So I got somewhat larger-than-usual printer, a HP 8150N, with an
additional 2000 pages feeder. When I use the hplip driver stack, it
seems I can print, but only using paper source #2 (the usual A4
source).

Sources are:

	(1) - Manual feed (for envelopes etc.)
	(2) - Top A4 internal cassette
	(3) - Bottom A3 internal cassette
	(4) - Optional 2000 sheet feeder

There are two output trays on my printer, the bottom-up output on top
of the printer, and the face-up to it's left.


With the hplip driver, I can source sheets from (2), but selecting the
high-volume source will have no effect. Additionally, I cannot select
the alternative face-up output to the left of the printer.

Using printer-driver-postscript-hp, the supplied/generated PPD offers
me everything I want: chooseable source and destination, along with
many more options.

However, when I select a source different than "Auto", the printer
always asks me to feed the manual (1) source. So there's a change in
behavior, but it's not completely right. (I've never actually put in
paper there, so I cannot say if output to the left actually works.)

As the PPD seems to have everything I want, I'd like to debug it, but
I'm somewhat at a loss here. I can easily intercept the communication
between CUPS's output and the printer and sniffered me a nice one-page
PS file.

%!PS-Adobe-3.0
%%For: (jbglaw)
%%Title: (ebookratgeber2013.pdf)
%%Creator: GPL Ghostscript 905 (ps2write)
%%LanguageLevel: 2
%%CreationDate: D:20130627231559+02'00'
%RBINumCopies: 1
%%Pages: (atend)
%%BoundingBox: (atend)
%%EndComments
%%BeginProlog
currentfile /ASCII85Decode filter /LZWDecode filter cvx exec
J.'GP1)YJ2:a-L/6rF=&5]f",9VMV4PfsINPg$$lJV;<[.@O%03.smQ('PQ#V^%=ggiP:i9P6m1
&e,,#6QsIUEP1^W4j%>VfmLeP21i['0XteJ5'-rMBI73qYi]MqRS:_)[:!GtMG0%^!tgdCBfAL(
[...]

I think the next step would be to un-ASCII85Decode and un-LZWDecode
that blob? That should give me the actual stream that the printer is
working on, right? Any hints on how I can extract it? Once it's there,
it wouldn't be too hard to look throught the output and match it
againts PCL or thatever is in there.

So I'd really like to work on it, to fix this PPD so that it actually
works, but I guess I'll need a little help for a start.

Thanks a lot,
Jan-Benedict

-- 
      Jan-Benedict Glaw      jbglaw@lug-owl.de              +49-172-7608481
Signature of:         Alles wird gut! ...und heute wirds schon ein bißchen besser.
the second  :

Attachment: signature.asc
Description: Digital signature


--- End Message ---
--- Begin Message --- 
On Thu 27 Jun 2013 at 23:43:14 +0200, Jan-Benedict Glaw wrote:

> Package: printer-driver-postscript-hp
> Version: 3.13.4-1
> 
> Hi!
> 
> So I got somewhat larger-than-usual printer, a HP 8150N, with an
> additional 2000 pages feeder. When I use the hplip driver stack, it
> seems I can print, but only using paper source #2 (the usual A4
> source).
> 
> Sources are:
> 
> 	(1) - Manual feed (for envelopes etc.)
> 	(2) - Top A4 internal cassette
> 	(3) - Bottom A3 internal cassette
> 	(4) - Optional 2000 sheet feeder
> 
> There are two output trays on my printer, the bottom-up output on top
> of the printer, and the face-up to it's left.
> 
> 
> With the hplip driver, I can source sheets from (2), but selecting the
> high-volume source will have no effect. Additionally, I cannot select
> the alternative face-up output to the left of the printer.
> 
> Using printer-driver-postscript-hp, the supplied/generated PPD offers
> me everything I want: chooseable source and destination, along with
> many more options.
> 
> However, when I select a source different than "Auto", the printer
> always asks me to feed the manual (1) source. So there's a change in
> behavior, but it's not completely right. (I've never actually put in
> paper there, so I cannot say if output to the left actually works.)
> 
> As the PPD seems to have everything I want, I'd like to debug it, but
> I'm somewhat at a loss here. I can easily intercept the communication
> between CUPS's output and the printer and sniffered me a nice one-page
> PS file.
> 
> %!PS-Adobe-3.0
> %%For: (jbglaw)
> %%Title: (ebookratgeber2013.pdf)
> %%Creator: GPL Ghostscript 905 (ps2write)
> %%LanguageLevel: 2
> %%CreationDate: D:20130627231559+02'00'
> %RBINumCopies: 1
> %%Pages: (atend)
> %%BoundingBox: (atend)
> %%EndComments
> %%BeginProlog
> currentfile /ASCII85Decode filter /LZWDecode filter cvx exec
> J.'GP1)YJ2:a-L/6rF=&5]f",9VMV4PfsINPg$$lJV;<[.@O%03.smQ('PQ#V^%=ggiP:i9P6m1
> &e,,#6QsIUEP1^W4j%>VfmLeP21i['0XteJ5'-rMBI73qYi]MqRS:_)[:!GtMG0%^!tgdCBfAL(
> [...]
> 
> I think the next step would be to un-ASCII85Decode and un-LZWDecode
> that blob? That should give me the actual stream that the printer is
> working on, right? Any hints on how I can extract it? Once it's there,
> it wouldn't be too hard to look throught the output and match it
> againts PCL or thatever is in there.
> 
> So I'd really like to work on it, to fix this PPD so that it actually
> works, but I guess I'll need a little help for a start.

Dear Debian User,

Futher information on your issue was asked for a few months ago but
there has been no response to the rquest. Use of our limited, volunteer
supported resources is best served by not keeping around inactive bugs
for longer than desirable, so the report is now being closed.

You may, of course, wish to review the reported problem. It would be
appreciated if any future investigation could be conducted using the
testing or unstable distributions. If considered necessary, a new bug
report, possibly referencing this one, would be submitted.

Thank you for your report and understanding.

Regards,

Brian.

--- End Message ---
Reply to: