Bugzilla – Bug 132152
CUPS doesn't write the last printer's "Info" line from "/etc/cups/printers.conf" to "/etc/printcap"
Last modified: 2005-11-23 13:51:45 UTC
I suppose I've just come across a little bug in CUPS that seems to be present in SuSE-Linux-10.0-final and in SuSE-Linux-10.1-alpha2: The "Info" line of the last printer that is declared within the file "/etc/cups/printers.conf" is not written to "/etc/printcap". In other words: If I have, for example, five printers declared in "/etc/cups/printers.conf" (it doesn't matter if the printers are created by YaST2 or by the CUPS webbased management tool), only the "Info" lines of the first four printers will be written correctly to "/etc/printcap". The "Info" line of the fifth printer seems to be ignored. Instead of this information the name of the fifth printer is repeated in "/etc/printcap". Therefore, e.g. Samba doesn't propagate this informational text about the fifth printer to the Windows clients (because Samba normally just fetches that information from "/etc/printcap"). I've seen the bug at first on SuSE-10.0-final. You'll find my "/etc/cups/printers.conf" and the "/etc/printcap" that was created automatically by CUPS (after restarting CUPS) based on the printers defined in "/etc/cups/printers.conf" as an attachment. I could reproduce it after then using SuSE-10.1-alpha2 on a test machine.
Created attachment 56397 [details] "/etc/cups/printers.conf" from SuSE-10.0-final machine
Created attachment 56398 [details] "/etc/printcap" from SuSE-10.0-final machine
You are right. I can reproduce it.
Fixed in next version. The problem was that: cupsd writes printcap file, before he gathered full information about a printer. So its always the last entry of printcap file, which is wrong. Yes the file is written every time a new printer is discovered in printers.conf, and by writing one, the previous printers have full information. :-)