Cant print in Hardy (thoug I could in Gutsy)

[adonet]

Thanks, but no, my username was already in that group. My printer is NOT a USb printer. Its a parallel HP Laserjet 4000 printer connected to a sitecom printserver. The printserver is connected to my router with a fixed IP address. If I ping this IP nr, I receive nice answers. So the printserver is connected
In Gutsy I use printerpoort

socket://192.168.2.10:9100

and it works. In Hardy it doesn't.

sudo hp-setup

doesn't see my printer and I can't print.

Does anyone have another idea?

Thanks

[stansford]

I'm not able to print to my HP Laserjet 4000 printer when I use Ubuntu 8.04 (Hardy). When I use Ubuntu 7.10 (Gutsy) on the same PC (another partition with dual boot) it all works fine. I installed the printer on the same way. Re-installing the printer doesn't help. Removing hplip and CUPS and re-installing these packages does't help.
Even re-installing Hardy doesn't help

When I try to print anything the printopdrachtbeheerder (screen where I see the printing commands) sometimes accepts the printcommand, and sometimes it doesn't. After a while it asks me If the printer is connected or not.

When in a console I give this command: sudo hp-check -r
it gives one error and one warning:

There are no CUPS printer queues found

and

Checking SIP version...
error: SIP not installed or version not found.

Checking for CUPS...
Status: taakplanner is actief
Version: 1.3.7
error_log is set to level: warn

I cant find a way to add any CUPS printer Queue and SIP is not in my repositories.


I can ping the printserver. It has a valid IP nr (192.168.2.10) and replies. I can login to the printserver and find all the communication methods are turned on.

I tried: socket://192.168.2.10:9100 as printer port. Does't work (though it works in Gutsy (7.10)
I tried ipp://192.168.2.10/printers/1 Doesn't work
I tried lpd://192.168.2.10 Doesn't work

The printer cannot be browsed for (it couldn't in 7.10 Gutsy too)

I tried tot install hplip 2.8.4 from the HP website without any result. The HP device manager that comes with it doesn't see the connected printer.

What can I do apart from downgrading to Ubuntu 7.10 ?

Any help or suggestions would be very nice.

Jeroen

As far as I know the lpd command is lpd://192.168.2.10/L1 how about trying that?
Also try the ipp command using: ipp//192.168.2.10/ipp/P1
or ipp//192.168.2.10:631/ipp/P1

I have an epson that used to work under gutsy but doesn't under hardy, printing via a 3com print server. Unfortunately the printserver itself died a day ago, so perhaps that was the main problem for me!

However when it was working I setup a new printer under the GNOME printing screen from the main menus and chose "LPD" as the type of printer. The key entry was the "L1" which isn't intuitive but has to be used and must go in the queue field for the thing to work. It did the trick for me, hope it works for you, otherwise I can't help you more.

[esmrg]

I also lost printing ability after Hardy installed. I send a job to cups, then cups stops it. I checked dmesg and this is what I get:

[16394.427672] audit(1211154077.674:6): type=1503 operation="inode_permission" requested_mask="::rw" denied_mask="::rw" name="/dev/tty" pid=23459 profile="/usr/sbin/cupsd" namespace="default"

It is a usb printer and appears to be connected:

[15619.787827] usblp0: USB Bidirectional printer dev 4 if 0 alt 0 proto 2 vid 0x04B8 pid 0x0005
[15619.787851] usbcore: registered new interface driver usblp

I thought it may be a permission issue, so I tried to print as root. Same thing.

I looked in /var/log/cups/error_log and got this:

E [18/May/2008:16:27:12 -0700] [Job 114] ijsgutenprint: the version of Gutenprint software installed (5.0.2) does not match the PPD file (5.0.1).
E [18/May/2008:16:27:12 -0700] [Job 114] ijsgutenprint: bad key code -4

So I tried reinstalling the printer. Nope.

Any ideas?

[adonet]

Adding yourself to the USB users might help if you've got an USB connected printer. There are threads about that issue.

This thread is about printing via the router to a printserver connected printer.

[adonet]

The lpd command responds that it is connected to the printer. A print command from yesterday rolls out of the printer, but nothing happens but waiting for half an hour.

[adonet]

Three days later still waiting....

Doesn't anybody have this problem. Doesn't somebody have a solution? I0d like to be able to print. from hardy.

[redoscar3]

Adonet,

I just found your thread and like you, am having trouble printing via LPD in Hardy. I've installed Hardy on my Acer 3003LCi laptop. My printer is a Samsung ML1710 served by a Trendnet ethernet to USB print server.

With Dapper through Gutsy, it has been pretty easy to get printing configured on this machine. But with Hardy, I still haven't had any luck. When I try to print a document, the Samsung starts to run, but then enters an error state. So I have to power off the printer to reset it. All other printers on the network print without issue.

So you are not alone, but I have not yet solved the problem. If I find something, I will let you know.

Red

[derfinsterling]

Did printing work after you put Apparmor in to complain mode?

The errors you listed suggest something wrong with the entries in /var/log/messages, which is causing logprof to choke. If printing works with Apparmor disabled, then I'll tell you how to clean your message log and get the relevant data.

Putting it in complain mode worked for me... what now?

[redoscar3]

Hello again,

I was finally able to try putting AppArmor into complain mode and that allowed my Hardy install to print to my Samsung printer. So what do I need to do from here to re-enable AppArmor but still continue getting printing to work? Is there a thread that describes the process to reconfigure around offending issues? This seems to be my last problem with Hardy that I need to get resolved.

Thanks for everyone help so far.

Red

[adonet]

I'm glad you can print at last. Look for an AppArmor specialist who might help you.

AppArmor in complainmode didn't do anything for me. So that isn't the problem for me.
Is there anybody who didn't make a fresh install of Hardy, but an upgrade from gutsy who has the same problem?

Is booting Hardy with the older Gutsy kernel probably a solution?