Bug 745223

(In reply to comment #0)
> In Live beta 16, I set up a network printer.

Later you say "system-config-printer in Applications", so I guess you first invoked that application, then clicked Add, then expanded the Network Printer entry.

> Had to give the IP.

So I think you typed this into the Host field and clicked Find.  But before that, were you asked for authorization to modify the firewall?  Did you provide that?

> The HP
> Laserjet m1522 didn't show up as an option, so I selected Laserjet 1200.

I'm not sure here whether the "Find" correctly found your printer, or whether you had to manually enter a URI?  Are you talking about selecting a device here, or selecting a driver?

> That
> worked (only that the printer shows up twice).

I'm not sure which screen you're looking at for this; whether you're seeing two methods for communicating with the printer in the Connections box (or Device list), or whether you're looking at the Choose Driver screen.

From your comments later I gather you completed the process of adding this printer.

> Then I installed hplip for the
> right driver,

Ah, of course really we want automatic driver installation to do that for you.  To fix that I'll need to see the printer's IEEE 1284 Device ID.  Please see this page on how to obtain that:
https://fedoraproject.org/wiki/How_to_debug_printing_problems#What_make_and_model_is_my_printer.3F

> and wanted to delete the 1200 to start with a clean slate. Now
> s-c-p claimed there were no printers configured (?), went through the same
> manual configuration (add networked printer, give IP, forward), got the right
> driver now and was offered duplex (not on our printer). When I tried to set a
> short name for the printer, the naming etc window had "Apply" greyed out.

Did you give the same name as you had previously given for the queue that had disappeared?  Did you try giving different names for it?  Were there any messages in .xsession-errors about it?

> Tried
> several times, it seems only the location can (has to?) be set to be able to go
> forward.

No, the location field may be blank.

> The 1200 configured originally and the m1522 show up afterwards (both
> twice). 

Here, I think you may be talking about the main printer view, rather than the add-printer dialog?  How are they named?  Is there another CUPS server on your network?

What does 'lpstat -s' say?

Thanks.

(In reply to comment #1)
> (In reply to comment #0)
> > In Live beta 16, I set up a network printer.
> 
> Later you say "system-config-printer in Applications", so I guess you first
> invoked that application, then clicked Add, then expanded the Network Printer
> entry.

Yep.

> > Had to give the IP.
> 
> So I think you typed this into the Host field and clicked Find.  But before
> that, were you asked for authorization to modify the firewall?  Did you provide
> that?

Not as far as I remember. 

> > The HP
> > Laserjet m1522 didn't show up as an option, so I selected Laserjet 1200.

> I'm not sure here whether the "Find" correctly found your printer, or whether
> you had to manually enter a URI?  Are you talking about selecting a device
> here, or selecting a driver?

The add printer dialog that opened after the "Find" asked to select a make, and then a model.

> > That
> > worked (only that the printer shows up twice).
 
> I'm not sure which screen you're looking at for this; whether you're seeing two
> methods for communicating with the printer in the Connections box (or Device
> list), or whether you're looking at the Choose Driver screen.

This is the main window for s-c-p.

> From your comments later I gather you completed the process of adding this
> printer.

Yes.

> > Then I installed hplip for the
> > right driver,

> Ah, of course really we want automatic driver installation to do that for you. 
> To fix that I'll need to see the printer's IEEE 1284 Device ID.  Please see
> this page on how to obtain that:
> https://fedoraproject.org/wiki/How_to_debug_printing_problems#What_make_and_model_is_my_printer.3F

# lpinfo -l -v gives no information (just "unknown" and such)
# /usr/lib/cups/backend/snmp xx.xx.xx.xx
network socket://xx.xx.xx.xx "HP LaserJet M1522nf MFP" "HP LaserJet M1522nf MFP" "MFG:Hewlett-Packard;CMD:PJL,PML,PCLXL,POSTSCRIPT,PCL;MDL:HP LaserJet M1522nf MFP;CLS:PRINTER;DES:Hewlett-Packard LaserJet M1522nf MFP;MEM:MEM=53MB;COMMENT:RES=600x2;" "HP LaserJet M1522nf MFP"
# grep '^*NickName:' /etc/cups/ppd/dcsc.ppd 
*NickName: "HP LaserJet m1522nf MFP pcl3, hpcups 3.11.10"

> > and wanted to delete the 1200 to start with a clean slate. Now
> > s-c-p claimed there were no printers configured (?), went through the same
> > manual configuration (add networked printer, give IP, forward), got the right
> > driver now and was offered duplex (not on our printer). When I tried to set a
> > short name for the printer, the naming etc window had "Apply" greyed out.
 
> Did you give the same name as you had previously given for the queue that had
> disappeared? 

Humm... I don't remember if I gave the first round configuration a name, but if I did it must have been the same.
 
>              Did you try giving different names for it?  Were there any
> messages in .xsession-errors about it?

Sorry, didn't look (LiveCD for testing and all that).

> > The 1200 configured originally and the m1522 show up afterwards (both
> > twice). 
 
> Here, I think you may be talking about the main printer view, rather than the
> add-printer dialog?  How are they named?  Is there another CUPS server on your
> network?

Main window of s-c-p. The names were the made-up name HP-M1522* twice and HP-1200* (or some such) twice. Perhaps the "*" were slightly different.

> What does 'lpstat -s' say?

OK, will have to go through the whole setup again with a LiveCD then...

I've filed bug #745498 and bug #745499 to track the IEEE 1284 Device ID issue.

Again in LiveCD 16 beta. Step by step:

Go to Applications -> Printing; About says it's system-config-printer 1.3.6.
Go to Add, it asks to adjust the firewall, check yes.
Go to Network Printer -> Find network printer. Enter IP address, press Find, offers port. Then finds a JetDirect printer, queue PASSTHRU (it seems I didn't give it enough time to go here yesterday). Press Probe, says "Searching for printers" and then nothing. Press Forward, goes "Searching for drivers." Sure takes its time...
New Printer window now. Choose Driver selected, go with that. Nope! If I select "Search for a printer driver to download" it identifies the printer correctly. Press Search, no visible reaction (just that the button greys out and says "Searching"). Either it takes a long time or it just got wedgded, no way to tell... BTW, going to "Select printer from database" and back now shows "Searching" but not greyed out. Pressed it again, only gets greyed out.
Go to "Select ...", HP, Forward, LaserJet 1200, Forward, accept the "printer" name, Accept. New window: "CUPS server error/There was an error during the CUPS operation: 'server-error-internal-error'". Main s-c-p window shows no configured printers.

Try again, now the name offered is HP-LaserJet-1200, and the printer is added (!), and it offers to print out a test page.
And in the main s-c-p page now I have printer and HP-LaserJet-1200, the first as default. Each appears once only.

# lpstat -s
system default destination: printer
device for HP-LaserJet-1200: socket://xx.xx.xx.xx:9100
device for printer: lpd://xx.xx.xx.xx/PASSTHRU

And there is no other CUPS around on this network, AFAIK.

(In reply to comment #4)
> Go to Network Printer -> Find network printer. Enter IP address, press Find,
> offers port.

OK, this is a JetDirect queue (i.e. socket://...).  You don't need to change the port number; it's always 9100 in my experience.

> Then finds a JetDirect printer, queue PASSTHRU (it seems I didn't
> give it enough time to go here yesterday).

In fact that would be a LPD/LPR queue (JetDirect queues don't have names).  PASSTHRU would be the discovered name of the queue.

> Press Probe, says "Searching for
> printers" and then nothing.

... so there wasn't any need to press Probe there.  It isn't obvious, I guess, that the JetDirect port number and LPD/LPR queue names are fine as they are. :-(

> Press Forward, goes "Searching for drivers." Sure
> takes its time...

Yes, that's almost entirely due to foomatic; there are moves afoot to improve that (bug #731683).

> New Printer window now. Choose Driver selected, go with that. Nope!

Oh, what happened?  It had pre-selected a driver for you, and you'd clicked Forward, but got an error?  Or couldn't click Forward?  Or no driver selected?  Something else?

> If I select
> "Search for a printer driver to download" it identifies the printer correctly.
> Press Search, no visible reaction (just that the button greys out and says
> "Searching"). Either it takes a long time or it just got wedgded, no way to
> tell...

Yes, that won't work at the moment at all (openprinting.org is down).

> Go to "Select ...", HP, Forward, LaserJet 1200, Forward, accept the "printer"
> name, Accept. New window: "CUPS server error/There was an error during the CUPS
> operation: 'server-error-internal-error'". Main s-c-p window shows no
> configured printers.

That's strange.  Can you search for server-error-internal-error in /var/log/cups/error_log to get some context about why that happened? (It might not be there; debugging defaults to off.)

Is that repeatable?

It selects the name 'printer' as a last resort, meaning:

* no Device ID was detected for the device
* the PPD didn't have a modelName attribute

I don't know why trying again would change either of those.

This message is a reminder that Fedora 16 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 16. 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 '16'.

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 16'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 16 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 to click on 
"Clone This Bug" and open it against that version of Fedora.

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

Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 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.