Bug#815001: Causes HP LaserJet 9000 Series printers to crash with error 49.60FF
tags 815001 moreinfo
thanks
Thank you for your report, Ryan.
On Wed 17 Feb 2016 at 10:05:49 -0500, Ryan Kavanagh wrote:
> Justification for severity "important": renders package unusable on
> systems only having access to HP LaserJet 9000 printers, and regardless,
> CUPS should never behave in such a way as to kill the central office
> printer.
>
> Steps to reproduce: Print something.
>
> Expected result: Your document gets printed.
>
> Obtained result: The printer crashes with error 49.60FF and a message to
> turn the printer off and on. Moreover, simply deleting the job and
> rebooting the printer does not cause the error to go away: as soon as it
> turns back on and finishes with its "Initializing..." screen, it
> displays the same error message. To recover the printer, it's necessary
> to repeatedly press the "Stop" button during printer boot-up and select
> the option to cancel the current job from the menu.
Please see the wiki on how to put CUPS into debug mode and obtain an
error_log for a job that triggers the problem. The log can be attached
to your next mail sent here.
> The relevant section from my printers.conf:
>
> <Printer ghc6107bw>
> UUID urn:uuid:99d34098-0ee1-3d62-6398-cf24ecad5996
> Info ghc6107bw
> MakeModel HP LaserJet 9000 Series Postscript (recommended)
> DeviceURI lpd://.../ghc6107bw
Does the problem exhibit itself for a socket://... conection and a
misbehaving file or if a PCL PPD is used instead of a PostScript one?
> State Idle
> StateTime 1455720153
> ConfigTime 1454096429
> Type 8433876
> Accepting Yes
> Shared No
> JobSheets none none
> QuotaPeriod 0
> PageLimit 0
> KLimit 0
> OpPolicy default
> ErrorPolicy stop-printer
> </Printer>
>
> I'm not quite sure when this problem first appeared. I remember having
> been able to print without issue in September, and the problem has
> cropped up since. I'd be happy to try bissecting versions to find when
> the problem first appeared, if someone could point me to the likely
> source of the problem (cups? cups-daemon? cups-filters?).
Does this happen for all files or is it limited to particular types.
Regards,
Brian.
Reply to: