Ubuntu 8.04 kernel cannot print to sitecom printserver

The updated 2.6.24-17-generic doesn't print either.

Anyone?

The update to kernel 2.6.24-18-generic does not change anything for me.
Still unable to print over the network.

Reference link to my problem:
http://ubuntuforums.org/showthread.php?t=797508

There still isn't any workable solution available.

I have exactly the same problem with my Sitecom Print server, Hardy and a Deskjet-920C printer.
Everythink work fine with two PC's running Gutsy and LPD/LPR unix and one PC running Windows XP.

Does anybody know what happens with these bug reports. Is someone working with it, or should we take some further action?

Jeroen

I am now able to print as of the 2.6.24-19-generic kernel update today!!!

:) :) :)

Thank you.

My system still cannot print in a usefull way. Now I got one page out of three and the system keeps asking whether of not the orinter is connected. They seem to be on their way, but still have a long way to go I'm afraid.

I keep on using ubuntu 7.10 gutsy Gibbon for the time being.

Jeroen

The update to 2.6.24-19-generic kernel changes something but the printer doesn't work correctly./ Same problem as adonet.

Maybe this problem is linked with the bug "unable to resolve host (pc's name)" when you use static addresses.
The first page is correctly printed only if you print one line but it is not the case for a full page or if you restart a print operation.
I have 3 PC's in production using gutsy without any problem

Lucien

http://users.skynet.be/linux-rixensart

My ability to print after updating to the 2.6.24-19-generic kernel was short lived. This morning I was no longer able to print.
I tried the work around posted by Patrick Schueller in Bug #237759, and now I can print again.

"with your favourite editor, add a line with

net.ipv4.tcp_frto = 0

to /etc/sysctl.conf (as usual, back it up before changing). Reboot or 'sudo sysctl -p' and probably also 'sudo /etc/init.d/cupsys restart' and enjoy (but ensure there aren't 20 documents in the queue before trying this )..."

Wonderful, with the workaround given by Givelove/Patrick Schueller my printer HP Deskjet-920C works perfectly via a printserver

Many thanks to everybody,

Lucien

I got in another forum this suggestion and after some reboots it works:

I think I have solved my problem - on my system the printserver printing issue appears to be down to permissions on config files stored on /home.

I have /home on a separate partition from my system and when I upgraded i simply reformatted the system partition and reinstalled. When you do this you create a new user, which might be the same username and password as you used on the old install, but as far as the system is concerned is different. Consequently your new login can not access the .XXXXXX configuration files on /home.

Thanks to nelz at linuxformat.co.uk for spotting this. The solution is to run in the terminal:
    sudo chown -R username: ~username

Where username is the username you login with after a restart. You should reboot after doing this.

I got one error message after doing this. Then I rebooted and still couldn't print. I rebooted again in gutsy and lost the print ability there as well. I repeated the chown command in gutsy, rebooted and could print again. I rebooted in hardy and a miracle happened: The printer started printing, from Hardy that is.

Thanks to
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/213081/comments/28

Jeroen

I have what appears to be the same issue (based on the forum thread).

I have an HP LaserJet 4 connected via parallel port. Under Gutsy it worked. Under Hardy it doesn't. I have two computers, one with a fresh install of Hardy, and one with an upgrade from Gutsy.

It doesn't seem to be an apparmor problem.

Assigning this to a different package; hopefully the package maintainer will take note

This is clearly a kernel bug, as the presented workaround changes the configuration of the kernel. Moving to the kernel. Possible fix is to set the configuration of the kernel appropriately by default.

Unfortunately the kernel people haven't responded to the bug since it was filed (and are generally unresponsive on other kernel bugs I am subscribed to). Since it is a printing issue, can't you own it?

The problem is that I cannot fix the kernel.

You should assign the bug to the package in which /etc/sysctl.conf is.

Adding a task for the procps package, as it provides the /etc/sysctl.conf file.

Two months later I still can print using the solution I mentioned on june, 24th
But as you might have noticed this thread is about printing on a printer thats connected to the computer via a printserver that's connected with a router. Not directly to a printer thats on the parallel port.

Hi Adonet,

Sorry for the delayed response here. Would you be willing to test the latest Alpha for the upcoming Intrepid Ibex 8.10 release - http://www.ubuntu.com/testing . The reason I ask is that is contains a newer 2.6.26 based kernel and is actively being developed by the Ubuntu kernel team. You should be able to test via a LiveCD. If the issue still exists, if you could attach the following debugging information that would be great (also please attach each file separately):

* uname -a > uname-a.log
* cat /proc/version_signature > version.log
* dmesg > dmesg.log
* sudo lspci -vvnn > lspci-vvnn.log

If you could also capture the dmesg output after attempting to print that would be great. For more information regarding the kernel team bug policy, please refer to https://wiki.ubuntu.com/KernelTeamBugPolicies . Thanks in advance.

Hi Leann Ogasawara

I downloaded the alpha 3 of Ubuntu 8.10.. Runned the liveCD, Installed the printer that's connected to my sitecom printserver and the test page came out of the printer. No problems at all.

here are the files you requested:

Jeroen

Now I installed ubuntu 8.10 Intrepid alpha 3 and I installed the same printer And I could print without any trouble.

I attached the same files again (now from the installed version) in a .tar file.

Jeroen

Thanks for testing adonet. From your comments it sounds like this is resolved for the upcoming Intrepid release. I'm going to tenatively mark this "Fix Released" for now. Feel free to set the status back to "New" if you see any regressions. Unfortuantely against Hardy this does not qualify for a Stable Release Update. Thanks.