Bug 517007 - USB printer not configured automatically
Summary: USB printer not configured automatically
Alias: None
Product: Fedora
Classification: Fedora
Component: system-config-printer
Version: rawhide
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Tim Waugh
QA Contact: Fedora Extras Quality Assurance
Depends On:
Blocks: F12Target fitandfinish
TreeView+ depends on / blocked
Reported: 2009-08-12 10:15 UTC by Adam Huffman
Modified: 2009-11-20 12:35 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2009-11-20 12:35:21 UTC
Type: ---

Attachments (Terms of Use)
content of /var/log/messages at time of printer connection (2.79 KB, text/plain)
2009-08-12 13:41 UTC, Adam Huffman
no flags Details

Description Adam Huffman 2009-08-12 10:15:24 UTC
Description of problem:
During yesterday's Fit And Finish Day, I tested connecting a USB printer.

The printer was detected and a small icon appeared in the notification area.  However, printer auto-configuration was not completed and it did not appear in the printer list.

The printer is an HP PhotoSmart C4480.

Version-Release number of selected component (if applicable):
Whichever version was in the Fit And Finish live CD.

How reproducible:

Steps to Reproduce:
Actual results:

Expected results:

Additional info:

Comment 1 Tim Waugh 2009-08-12 12:16:33 UTC
Please edit /etc/rsyslog.conf and change this line:

*.info;mail.none;authpriv.none;cron.none                /var/log/messages

to this (i.e. change 'info' to 'debug'):

*.debug;mail.none;authpriv.none;cron.none                /var/log/messages

Then run 'service rsyslog reload'

After that, make sure you don't have a queue configured for that printer, make a note of the exact time, then connect it and power it on.

What's in /var/log/messages after the point it is connected?

Comment 2 Adam Huffman 2009-08-12 13:41:30 UTC
Created attachment 357170 [details]
content of /var/log/messages at time of printer connection

Comment 3 Adam Huffman 2009-08-12 13:42:20 UTC
There was a message from the notification icon that there wasn't a driver for the printer.

Comment 4 Tim Waugh 2009-08-12 15:28:54 UTC
That's because there isn't an exact match for that model, and we don't automatically configure queues if we aren't confident they will work.

The closest match it found was the c4380 driver, although it *ought* to have considered the c4400 driver the closest.  It still wouldn't count this as an exact match, so wouldn't automatically configure a queue for that.

I think it needs to be taught how to spot the keyword "series", and use it to deduce whether this driver should count as an exact match.

Comment 5 Tim Waugh 2009-08-12 15:37:10 UTC
Actually it seems to be simpler than this.

Could you please install the 'hpijs' package and let me know whether the printer is automatically configured when connected?

Comment 6 Tim Waugh 2009-11-20 12:35:21 UTC

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