You are not logged in.

#1 2013-03-26 02:24:04

glenn69
Member
Registered: 2007-09-26
Posts: 111

USB printer no longer detected by cups

I've been using a USB brother HL-2170W printer for months.  Today it stopped printing.  If I check the web interface for cups I see that the status of the printer remains Processing - "Waiting for printer to become available."

I tried to delete the printer and re-install it, however cups no longer detects it as it always had in the past.

How do I troubleshoot this?

Offline

#2 2013-03-26 02:31:10

ewaller
Administrator
From: Pasadena, CA
Registered: 2009-07-13
Posts: 13,158

Re: USB printer no longer detected by cups

For starters, does it show up in the output of lsusb  ??
Is there anything interesting in the journal at the time you disconnect or reconnect the printer?


Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
You assume people are rational and influenced by evidence.  You must not work with the public much. -- Trilby
----
How to Ask Questions the Smart Way

Offline

#3 2013-03-26 02:36:25

glenn69
Member
Registered: 2007-09-26
Posts: 111

Re: USB printer no longer detected by cups

Yes, it shows up in lsusb as Bus 008 Device 002: ID 04f9:0035 Brother Industries, Ltd

journalctrl -f displayes this when I disconnect the printer then reconnect it

Mar 25 21:29:44 Arch-Home_x86_64 kernel: usb 8-1: USB disconnect, device number 6
Mar 25 21:29:44 Arch-Home_x86_64 kernel: usblp2: removed
Mar 25 21:29:44 Arch-Home_x86_64 systemd-udevd[2778]: failed to execute '/opt/VirtualBox/VBoxCreateUSBNode.sh' '/opt/VirtualBox/VBoxCreateUSBNode.sh --remove 189 901': No ...r directory
Mar 25 21:29:44 Arch-Home_x86_64 systemd[1]: Service printer.target is not needed anymore. Stopping.
Mar 25 21:29:44 Arch-Home_x86_64 systemd[1]: Stopping Printer.
Mar 25 21:29:44 Arch-Home_x86_64 systemd[1]: Stopped target Printer.
Mar 25 21:29:51 Arch-Home_x86_64 kernel: usb 8-1: new full-speed USB device number 7 using xhci_hcd
Mar 25 21:29:51 Arch-Home_x86_64 kernel: usblp 8-1:1.0: usblp2: USB Bidirectional printer dev 7 if 0 alt 0 proto 2 vid 0x04F9 pid 0x0035
Mar 25 21:29:51 Arch-Home_x86_64 mtp-probe[2781]: checking bus 8, device 7: "/sys/devices/pci0000:00/0000:00:15.2/0000:05:00.0/usb8/8-1"
Mar 25 21:29:51 Arch-Home_x86_64 mtp-probe[2781]: bus: 8, device: 7 was not an MTP device
Mar 25 21:29:51 Arch-Home_x86_64 systemd-udevd[2782]: failed to execute '/opt/VirtualBox/VBoxCreateUSBNode.sh' '/opt/VirtualBox/VBoxCreateUSBNode.sh 189 902 00': No such f...r directory
Mar 25 21:29:51 Arch-Home_x86_64 systemd[1]: Starting Printer.
Mar 25 21:29:51 Arch-Home_x86_64 systemd[1]: Reached target Printer.

Offline

#4 2013-03-26 02:59:17

ewaller
Administrator
From: Pasadena, CA
Registered: 2009-07-13
Posts: 13,158

Re: USB printer no longer detected by cups

The only thing that does  not make sense is:

Mar 25 21:29:51 Arch-Home_x86_64 systemd-udevd[2782]: failed to execute '/opt/VirtualBox/VBoxCreateUSBNode.sh' '/opt/VirtualBox/VBoxCreateUSBNode.sh 189 902 00': No such f...r directory

Is there an incidence of VirtualBox running?  Have you told VB to capture this USB device?  I don't know if it means anything, I am just probing for clues.


Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
You assume people are rational and influenced by evidence.  You must not work with the public much. -- Trilby
----
How to Ask Questions the Smart Way

Offline

#5 2013-03-26 03:57:16

glenn69
Member
Registered: 2007-09-26
Posts: 111

Re: USB printer no longer detected by cups

Virtualbox is not running.

The printer has always worked until the past couple of days.

Offline

#6 2013-03-27 17:50:59

vacant
Member
From: downstairs
Registered: 2004-11-05
Posts: 801

Re: USB printer no longer detected by cups

I discovered printing no longer works.

I have a Samsung ML-2010 connected via USB:

#/usr/lib/cups/backend/usb
DEBUG: list_devices
DEBUG: libusb_get_device_list=6
DEBUG2: Printer found with device ID: MFG:Samsung;CMD:GDI;MDL:ML-2010;CLS:PRINTER;STATUS:BUSY; Device URI: usb://Samsung/ML-2010?serial=3A37BKDP306080W.
direct usb://Samsung/ML-2010?serial=3A37BKDP306080W. "Samsung ML-2010" "Samsung ML-2010" "MFG:Samsung;CMD:GDI;MDL:ML-2010;CLS:PRINTER;STATUS:BUSY;" ""

#lpinfo -v
network ipps
network beh
network lpd
network socket
network ipp
network https
network http

Where has the "direct/usb" stuff gone from lpinfo?

Cups web interface won't find it. I can add the printer using lpadmin, then it shows up in the web interface. Trying to print it stays forever at: "Processing - "Waiting for printer to become available.", which is not surprising since the DEBUG2 line says "STATUS:BUSY".

I've stopped. reinstalled and started cups, also tried deleting cups files from /etc and /var before installing.

Offline

#7 2013-07-14 04:11:42

betso
Member
Registered: 2012-05-27
Posts: 1
Website

Re: USB printer no longer detected by cups

It took me the whole day to figure out the same problem as @vacant described and it turned out to be a matter of privileges.
Since I login with root on CUPS configuration, I never thought that this would be an issue.
Reading countless threads, I finally took a look at the /dev/bus/usb/xxx/xxx of the printer:

# ls -l /dev/bus/usb/005/019 
crw------- 1 root root 189, 530 Jul 13 23:32 /dev/bus/usb/005/019

I then added the users to the group lp and created /etc/udev/rules.d/10-usbprinter.rules, containing:

ATTR{idVendor}=="04e8", ATTR{idProduct}=="324c", MODE:="0660", GROUP:="lp"

Please not that "04e8" is the idVendor of Samsung and "324c" happens to be the idProduct of my printer (Samsung ML-1740).
You may want to check for yours by e.g. `lsusb`.

After reloading the udev rules with `udevadm control --reload-rules`, the printer was autodetected by CUPS.

I know that the thread is somewhat old but I hope to prevent someone else from having a day like mine today.


XODA, the KISSed Document Manager.

Offline

#8 2014-10-22 19:40:50

cabbage
Member
Registered: 2013-04-16
Posts: 6

Re: USB printer no longer detected by cups

Thank you betso!

I had a similar problem, unable to print becuase I'd installed the android-udev package and the device file now had group adbusers.

:-)

Offline

Board footer

Powered by FluxBB