HP PSC-500 no_device_found

Bug #77630 reported by Gnu_Raiz
2
Affects Status Importance Assigned to Milestone
hplip (Ubuntu)
Incomplete
Undecided
Pascal De Vuyst

Bug Description

Binary package hint: hplip

This could be a variation of bug #23469, unlike that buy my printer is an HP-PSC 500 multi-function printer copier scanner. I am using Ubuntu edgy amd64, with the newest hplip 1.6.9-0ubuntu2. This printer is a parallel port printer hooked up to my parallel port. So usb has no concern on it.

If I run hp-setup not using gnome or cups I get this error!

error: No devices found.
error: Error occured during interactive mode. Exiting.

It also seems that others have been getting this message as well.

Revision history for this message
Andrew H (hamiltona) wrote :

I have the same problem. My printer is an HP PSC 1610xi that worked fine in Edgy, but now isn't detected in Feisty. It is connected via USB, and isn't recognized by the system at all. lsusb shows no printer connected.

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

Thanks for your bug.
For Edgy or Dapper please remove the lp module from /etc/modules and reboot.
This lets cupsys load both the lp and ppdev kernel module and creates /dev/parport0.
Run lpinfo -v from a terminal after rebooting, your parallel printer should be autodetected without problems now.

Changed in hplip:
assignee: nobody → pascal-devuyst
status: Unconfirmed → Needs Info
Revision history for this message
Till Kamppeter (till-kamppeter) wrote :

Gnu_Raiz, the problem reported by you is known and fixed in Feisty by making the CUPS startup script loading ppdev also if lp is already loaded. Duplicate of bug #29050.

Andrew H, you problem is different to the one reported by Gnu_Raiz. You are on USB and he is on parallel. And as lsusb does not sow your printer, yours is a kernel problem. Please open a new bug report on it (the kernel package is named "linux-source").

Backport fix requests for the parallel printer detection on Edgy and Dapper please add to bug #29050.

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.