CUPS not working with network printer

I confirm this issue printing on a Lanier LD032c-PS, Ubuntu Linux Edgy, Unix printer (LPD) connection with a PCL 5c driver. I managed to get a colored test page printed perfectly, but apart from that, it is exactly the issue you describe. Yet, mine says 3% complete, so I win ;)

We have changed the default print management system in Ubuntu from gnome-cups-manager to system-config-printer because g-c-m is no longer maintained. Could you please check if this is still a problem in Gutsy or Hardy? Thanks!

Look at the last attachment of bug 183219. I could imagine that the decribed workarround may solve your problem too.

Best regards

Dogbert

I installed Ubuntu Gusty and also have the same problem, I wish the last upgrade of the hal-system-printer and the system-config-printer does not work anymore. The bug 183219 does not helped me.

I can print from my gutsy installation with any program. I installed my printer in a separate hardy installation and nothing comes out of the printer. The system sometimes shows a textballon saying in Dutch something like "it seems there is no connection with the printer?"
I'm printing via a sitecom printserver that is connected to my router.
Also from other computers with win XP or Vista on it is works fine.

When I boot from the live CD Hardy and install the printer, the same thing happens. What's different between Gutsy and Hardy that makes my printer unconnectable for my applications and what could I do to print again?

thanks,
Jeroen

Same thing as Adonet. I use Kubuntu 7.10 and printing is ok. But with Kubuntu 8.04, things are different with my wifi connection. Unable to print a complete document. The printer stop after few lines. I use HP Deskjet 5440 with a Iogear printserver PS121 linked to my router by ethernet cable. The problem happend with my IBM T23 laptop with a pcmcia Dlink card airplus.

But if I plug my laptop to the network with a ethernet cable instead using wifi, I can print correctly on Kubuntu 8.04 !!!

Another interesting thing is if I use Ubuntu 8.04 instead of Kubuntu 8.04, I can use wifi and it print correctly.

So I can confirm that Ubuntu 8.04 works fine either wifi and cable. I can also confirm that Kubuntu 8.04 works fine with a cable but doesn't work ok with the wifi.

i just have inspiron mini from dell with ubunto os. I was trying to print through network printer but it does not print. My printer is SamsungS 4521 F series. Message is cups missing filter. How can i solve it

You might start reading and posting here if your system is based on jaunty Jackalope 9.04:
https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/382379
Till Kamppeter helped me quite a lot with this problem. Now I can print again.

Note that it is important to know whether your ubuntu is the LTS version 8.04 (a.k.a. Hardy Heron) or the latest version 9.04 (a.k.a. Jaunty Jackalope)

These ubuntus have quite different reasons for not printing to a network printer.

Solution on Hardy heron based systems can be found here:
http://ubuntu-install.blogspot.com/2008/11/use-printserver-in-ubuntu-804-hardy.html

good luck

Jeroen

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Thank you for taking the time to report this bug and helping to make Ubuntu better. My apologies as I should not have marked this Invalid. The issue that you reported is one that should be reproducible with the live environment of the Desktop CD of the development release - Maverick Meerkat. It would help us greatly if you could test with it so we can work on getting it fixed in the next release of Ubuntu. You can find out more about the development release at http://www.ubuntu.com/testing/ . Thanks again and we appreciate your help.

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!