Jaunty cannot print to Printer on a local printserver

Bug #365951 reported by adonet on 2009-04-24
Affects Status Importance Assigned to Milestone

Bug Description

A HP Laserjet printer is connected on a router via a printserver. The printer can be used bij alle computers that are connected on the router. It works from Hardy Heron 8.04.2 (didn't with 8.04 and 8.04.1 without a workaround). The printer works from Suse Linux, Fedora 10, Windows XP and Vista.

I use this URI: socket://

Ubuntu 9.04 Jaunty Jackalope cannot connect to the printer and just says that the printer might not be connected. On the printer the data receiving LED is blinking, but nothing happens.
Even not with the workaround that did the job in the early versions of Hardy Heron 8.04 and 8.04.1
That workaround was to add this line: net.ipv4.tcp_frto = 0
in this file: /etc/sysctl.conf
The bug in Hardy was found to be in the kernel.

Any help would be appreciated very much

adonet (jeroen-adolfse) on 2009-04-24
tags: added: connection
removed: conncetion
description: updated
affects: ubuntu → cups (Ubuntu)
adonet (jeroen-adolfse) on 2009-04-26
affects: cups (Ubuntu) → ubuntu
adonet (jeroen-adolfse) on 2009-04-26
description: updated

Please provide the output of the following command on a terminal for some useful printing related debugging information:
apport-collect -p cups 365951

Can you also provide a cups error_log after trying to print as described here: https://wiki.ubuntu.com/DebuggingPrintingProblems#cupserrorlog

Changed in ubuntu:
status: New → Incomplete
adonet (jeroen-adolfse) wrote :

In another forum thread I found out that many others had related problems and Till Kamppeter made a solution available in the jaunty repos.

You can read more about it on https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/382379



If I understand correctly the poppler update in jaunty fixed this bug, can we close this bug report then?

adonet (jeroen-adolfse) wrote :


Yes, We can close this bug as far as I'm concerned.

Thank you for your help.

Closed as a duplicate.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers