Can't print to Oki C5550 MFP via USB

Bug #227342 reported by Qluripax
4
Affects Status Importance Assigned to Milestone
cupsys (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: cupsys

Using Ubuntu 8.04 (upgraded from 7.10). The system is updated today.

Having an Oki C5550 MFP connected over USB. The printer is recognized both in gnome-cups-manager and cups web-interface. The printer is installed with a .ppd-file from Oki (their windows repositories).
The printer is not listed at linuxprinting.org, but as it is an postscript printer I assumed that I can use an windows .ppd-file. And I don't think this is the problem.

Everything seams fine but the printer don't work. When printing the answer I got from cups is "device not ready". I have searched around a lot on the net but can't find anything. Can it be HAL instead of cupsys that is the problem? I also have an HP Officejet 7130 connected to the server via hplip, can it be a conflict with hp?

Anyway here is the output from lpstat -v:
enhet för C5550_MFP: usb://OKI%20DATA%20CORP/C5550%20MFP
enhet för officejet_7100: hp:/usb/officejet_7100_series?serial=HU36NCM0306K
enhet för officejet_7100_series: hp:/usb/officejet_7100_series?serial=HU36NCM0306K
enhet för officejet_7100_series_fax: hpfax:/usb/officejet_7100_series?serial=HU36NCM0306K
enhet för PDF: cups-pdf:/

(right, I'm a Swede) And from lpinfo -v:
network socket
network beh
direct hpfax
direct hp
network http
network ipp
network lpd
direct parallel:/dev/lp0
direct hal:///org/freedesktop/Hal/devices/usb_device_6bc_11c_noserial_if1_printer_noserial
file cups-pdf:/
direct scsi
network smb

I'm including the printingbuginfo in a separate file.

I would appreciate some help finding a solution of this.

Revision history for this message
Qluripax (qluripax) wrote :
Revision history for this message
Pascal De Vuyst (pascal-devuyst) wrote :

Looking at your lpinfo -v output your printer doesn't seem to be detected by CUPS.
Can you attach the /var/log/messages information as described in the printer detection section of https://wiki.ubuntu.com/DebuggingPrintingProblems.

Changed in cupsys:
assignee: nobody → pascal-devuyst
status: New → Incomplete
Revision history for this message
Qluripax (qluripax) wrote :

I thought that the row "direct hal://..." was where CUPS detected the printer.
Anyway, here it is. It's covering the latest 24 hours. As this is a small but production server the log is covering more printers than this.

Revision history for this message
Qluripax (qluripax) wrote :

I've tried a lot of debugging but it feels that I don't come down to the right level..
Anyway, after removing appamor and a reboot of the server I got the following in cups web-interface: "Could initialize HAL daemon: (null)"

I have also tried the network interface and the only thing I got then was "busy, retrying". Network interface is no option for me in production as we are two companies that shares this printer (and the other company don't dare to have Linux computers on their network).

I'm an Linux administrator - not a hacker - but are there any debugging tools that I can use to come down a bit deeper in this? The printer is relative expensive and I am allowed to use it for free so it's quite interesting for me to have this fixed... Thanks!

Revision history for this message
Qluripax (qluripax) wrote :

I've worked a lot to debug this and I can now print over the network interface but not over USB.
The interesting thing is that it works with dapper (6.06 LTS). I installed an dapper on virtual box and that way it works. This seams to be the same as in bug https://bugs.launchpad.net/ubuntu/+source/cupsys/+bug/35638/comments/106
If so this ain't a cups bug but hal.

So the question is, shall I reassign this to hal or shall I write a new bug report?

Revision history for this message
Qluripax (qluripax) wrote :

Have tried to debug this further. I've tried a lot of Linux-distributions, dsl, knoppix, debian, mandriva, gentoo, puppy etc. I've moved the printer to a brand new machine, I've changed the USB-cables.. all with the same disheartening result.

So this seams not to be a Ubuntu bug nor Cups but a HAL or a Linux USB bug... I'll try to ask a question on hal-cups-utils about how to handle this further.

Changed in cupsys:
assignee: pascal-devuyst → nobody
status: Incomplete → New
Revision history for this message
Dark.Crow (d+rkcrow) wrote :

I had the same "Could initialize HAL daemon: (null)" with an HP USB printer. After a check on the errorlog of cups with a warning about no rights at /var/cache/cups.. i changed the rights, but did not work. cleared cache ( rm /var/cache/cups -R) and the line left as snow before the sun in my browser with cups admin page.

Hope this helps

Revision history for this message
Qluripax (qluripax) wrote :

Thanks, I've tried that too - but without success.
As I didn't got this one to work I bought a new printer but I still got the the printer in house, so I can do tests on it if I got more from you...
Can also complete my earlier bugreports with the fact that printing via the network interface (on the printer) works well. But as I mention above, thats no option for me during daily work.

Revision history for this message
Pascal De Vuyst (pascal-devuyst) wrote :

Qlurix,
Still missing the printer detection information from https://wiki.ubuntu.com/DebuggingPrintingProblems as mentioned in comment 2.

Changed in cupsys (Ubuntu):
status: New → Incomplete
Revision history for this message
xteejx (xteejx-deactivatedaccount) wrote :

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!

Changed in cupsys (Ubuntu):
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.