Red Hat Bugzilla – Bug 439170
[RFE] Scan for printer(s) button
Last modified: 2008-09-01 07:47:01 EDT
Description of problem:
When pressing New Printer button an automatic scan
Is not better to move this *feature* to a seperated button
[ Scan for printers ]
Gets annoying specially when you know that the current network your
on has no printer and or at the same time your adding a lot of other
printers and you have to wait for the scan each and every time you make a new
Version-Release number of selected component (if applicable):
Steps to Reproduce:
We have to scan at least once -- it's just asking CUPS for its list of devices.
We don't get to say "only show local devices" or anything like that.
However, we could cache the list and provide a refresh button.
Can Windows Printer via Samba have a separated scan button or be inter graded to
the refresh button as well.
SMB printers are only searched for when you actually click on 'Windows Printer
via Samba'. All CUPS tells us about that is that the backend is prepared to be
used; the Samba backend is not able to search for existing SMB shares. (Does
that answer your question?)
Indeed it does, thanks for the info.
But could we move that scan from the click windows printer via
samba to a special scan button instead of that happening automatic when
selecting/clicking windows printer via samba.
So these are actually 2 buttons one refresh the other search for windows
Actually today a change was checked into CUPS upstream that means that CUPS 1.4
*will* be able to only show us local devices unless we ask for network devices.
Marking this as F10Target so we can pick that up.
Adding FutureFeature keyword to RFE's.
(In reply to comment #4)
> But could we move that scan from the click windows printer via
> samba to a special scan button instead of that happening automatic when
> selecting/clicking windows printer via samba.
No, that isn't how it works. It isn't a simple 'press a button and get a list'
type thing -- it's a tree that must be navigated, and which may require
authentication at various stages.
Anyway, I've created a trac entry for this: