Created attachment 635342 [details] add a new printer dialog screenshot Description of problem: Couldn't add printer by address When I set checkbox "Search by Address" and enter printer ip adress, nothing happens.
Created attachment 663605 [details] Filter printer by address not work
As you can see on screenshot https://bugzilla.redhat.com/attachment.cgi?id=663605 when I enter ip adress I couldn't see only needed printer in list.
I have this problem as well. Whats more the descriptions dont show what port the service is on. Most our printers have a web interface which can not be printed to, but it shows up as another printer (this happens in windows too, but the description contains the word web so I can tell the difference). I have the problem of 3 identically named printers, so 2 interfaces each, so 6 options I cant tell the difference between. I need the non-web interface on 10.0.2.33 (port 9100?), but can not see which one to select. Screenshot via this link shows the info I have available to me, and my failed attempts to narrow it down with "search by address". http://i48.tinypic.com/2w49nbl.png
Update: my problem is the same, but fedora 17 thus slightly different screenshot.
This is still here in Fedora 20 - as in Comment #2 there is no way to directly enter an IP address/hostname for a printer, only filter the printers automatically discovered. There is an old JetDirect box on IP address 10.1.1.95 where I am but the JetDirect box is too old to do zeroconf and its printer does not appear in the control-center print dialog no matter how long I wait. Neither MacOS X nor Windows 7 can automatically discover the printer either so I think there is an argument that automatically seeing it is unlikely (perhaps this is Bug #871272). However, both MacOS X and Windows provide a way to enter an IP address (on MacOS X you click on the IP tab and select the HP Jetdirect - Socket protocol, on Windows 7 you click "The printer that I want isn't listed" and select Add a printer using a TCP/IP address or hostname). For Fedora it is possible to add the printer but only via system-config-printer which is not linked to from control-center.
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. 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 '18'. 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 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 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, you are encouraged change the 'version' to a later Fedora version prior to Fedora 18's end of life. 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.
This bug is happening in Fedora 20 but I can't update the product...
Hi, I'll look at this next week as I don't have a network printer nearby now. Regards Marek
Hi Sitsofe, I've tried to add a network printer by IP address (entered in to the search entry + enter) and control-center found it and installed it correctly (the only port I kept available there was 9100). Could you try to run this command and paste its result here? "/usr/lib/cups/backend/snmp 10.1.1.95" Regards Marek
/usr/lib/cups/backend/snmp 10.1.1.95 doesn't return anything (which doesn't surprise me as I think the printer is too basic to do SNMP). Here's the nmap output for it: # nmap -T4 officejetg95 Starting Nmap 6.40 ( http://nmap.org ) at 2014-01-30 17:21 GMT Nmap scan report for officejetg95 (10.1.x.x) Host is up (0.0032s latency). rDNS record for 10.1.x.x: officejetg95.x.x Not shown: 990 closed ports PORT STATE SERVICE 21/tcp open ftp 23/tcp open telnet 80/tcp open http 280/tcp open http-mgmt 515/tcp open printer 631/tcp open ipp 5120/tcp open unknown 9100/tcp open jetdirect 9220/tcp open unknown 9290/tcp open unknown MAC Address: 00:10:83:xx:xx:xx (Hewlett-packard Company) Nmap done: 1 IP address (1 host up) scanned in 21.42 seconds # nmap -sU -T4 officejetg95 Starting Nmap 6.40 ( http://nmap.org ) at 2014-01-30 17:22 GMT Nmap scan report for officejetg95 (10.1.x.x) Host is up (0.0026s latency). rDNS record for 10.1.x.x: officejetg95.x.x Not shown: 995 closed ports PORT STATE SERVICE 68/udp open|filtered dhcpc 137/udp open|filtered netbios-ns 161/udp open|filtered snmp 427/udp open|filtered svrloc 32768/udp open|filtered omad MAC Address: 00:10:83:xx:xx:xx (Hewlett-packard Company) Nmap done: 1 IP address (1 host up) scanned in 194.69 seconds
$ /usr/lib/cups/backend/snmp 10.10.1.213 network socket://10.10.1.213:9100 "HP LaserJet P3010 Series" "HP LaserJet P3010 Series" "MFG:Hewlett-Packard;CMD:PJL,BIDI-ECP,PJL,POSTSCRIPT,PDF,PCLXL,PCL;MDL:HP LaserJet P3010 Series;CLS:PRINTER;DES:Hewlett-Packard LaserJet P3010 Series;" ""
Hi, I'm working on implementation of addition of LPD and AppSocket printers but since I'm quite busy I'm still not finished. It should be available in gnome-control-center 3.14 (Fedora 21?) Regards Marek
(In reply to Marek Kašík from comment #12) > Hi, > > I'm working on implementation of addition of LPD and AppSocket printers but > since I'm quite busy I'm still not finished. It should be available in > gnome-control-center 3.14 (Fedora 21?) > > Regards > > Marek I've just pushed patches implementing this functionality upstream. It will be available in Fedora 21 as part of gnome-control-center 3.14. Regards Marek
As Marek said this has been fixed in Fedora 21's control-center-3.14.2-2.fc21.x86_64. Now I can type a hostname and upon doing so two options (LPD and AppSocket) are presented. After using AppSocket and choosing the correct driver print worked fine to the G95. Thanks for fixing this! (Note I can't change the state of this issue since I wasn't the one who filed it)