Bug 638274 - Cups "usb" backend is not discovering connected USB printer
Summary: Cups "usb" backend is not discovering connected USB printer
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: cups
Version: 13
Hardware: x86_64
OS: Linux
low
high
Target Milestone: ---
Assignee: Tim Waugh
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-09-28 16:21 UTC by Ruth Ivimey-Cook
Modified: 2011-06-28 12:13 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2011-06-28 12:13:26 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Ruth Ivimey-Cook 2010-09-28 16:21:03 UTC
Description of problem:
I have in the past connected my Epson 1270 printer to my Linux machine running previous Fedora releases and it's worked. Running Fedora 13 CUPS this is no longer working because CUPS refuses to talk "usb". That is, with the old setup (a usb://EPSON/Stylus%20Photo%201270 URI referencing the manuf/model names) or by trying to create a new setup, the printer is not found.

Version-Release number of selected component (if applicable):
1.4.4-10.fc13.x86_64

How reproducible:
For me, it just doesn't work! For example:

% lsusb
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 002: ID 0471:0307 Philips (or NXP) PCVC675K Webcam [pwc]
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 002: ID 04b8:0005 Seiko Epson Corp. Stylus D88+
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

The intended printer is thus on /dev/bus/usb/002/002

but running
% sudo /usr/lib/cups/backend/usb

produces no output. Inserting an "strace" reveals that the "usb" exe is looking in the "old" place for "lp" devs: /dev/usblp0..n, /dev/usb/lp0..n and /dev/usb/usblp0..n and I don't have them; I only have /dev/bus/usb/xxx

However if I make a symlink from /dev/bus/usb/002/002 to /dev/usblp2, I get this in the strace output:

open("/dev/usblp1", O_RDWR|O_EXCL)      = -1 ENOENT (No such file or directory)
open("/dev/usb/lp1", O_RDWR|O_EXCL)     = -1 ENOENT (No such file or directory)
open("/dev/usb/usblp1", O_RDWR|O_EXCL)  = -1 ENOENT (No such file or directory)
open("/dev/usblp2", O_RDWR|O_EXCL)      = 3
ioctl(3, SNDCTL_DSP_SYNC, 0x7fff8c35b0c0) = -1 ENOTTY (Inappropriate ioctl for device)
close(3)                                = 0
open("/dev/usblp3", O_RDWR|O_EXCL)      = -1 ENOENT (No such file or directory)

I see notes that SNDCTL_DSP_SYNC has also been called IODEV_GET_ID or some such, but whatever it's called it's not working.

I note elsewhere that a package called hal-cups has helped people, but it's not available in Fedora, and I presume there's a reason for that. 
  
Actual results:
No USB device listed in Add Printer for CUPS, whether using KDE, Wb page or Gnome config tools.

In addition, using the original config, CUPS couldn't find a usb: URI.

Expected results:
USB printer listed and works.

Comment 1 Tim Waugh 2010-09-28 16:54:01 UTC
/dev/bus/usb/*/* and /dev/usb/lp0 are quite different things.  We don't use the libusb support in Fedora yet as there is some functionality we would lose regarding error reporting.

First of all, let's take a step back: the problem is that you aren't getting a queue automatically created when you plug in the printer, correct?

So, after you've plugged in the printer, what does 'lpinfo -l -v' say, run as root?

Comment 2 Ruth Ivimey-Cook 2010-09-28 20:45:21 UTC
** It's working now. I moved from one USB port to another. The first showed it in lsusb, but for this port it now works. I guess you can close this, but it still seems weird to me...
**
Lpinfo output is below - and includes usb.

The other thing is that cupsd keeps dying (as in status "cupsd is stopped") - don't know if its related or not so I mention it here in case. Can't see anything in the error_log file to indicate this though, as the error log has a faitly continuous sequence of browse updates.

$ sudo lpinfo -l -v
Device: uri = usb://EPSON/Stylus%20Photo%201270
        class = direct
        info = EPSON Stylus Photo 1270
        make-and-model = EPSON Stylus Photo 1270
        device-id = MFG:EPSON;CMD:ESCPL2,BDC,D4;MDL:Stylus Photo 1270;CLS:PRINTER;DES:EPSON Stylus Photo 1270;
        location =

Comment 4 Tim Waugh 2010-09-29 09:52:34 UTC
If you change back to the original USB port, does it fail again?

Comment 5 Bug Zapper 2011-05-31 12:23:56 UTC
This message is a reminder that Fedora 13 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 13.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '13'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 13's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 13 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 6 Bug Zapper 2011-06-28 12:13:26 UTC
Fedora 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.