Bug 59734 - No such map printers.conf.byname.
Summary: No such map printers.conf.byname.
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kdeprint
Classification: Unmaintained
Component: general (show other bugs)
Version: unspecified
Platform: Compiled Sources Linux
: NOR normal
Target Milestone: ---
Assignee: KDEPrint Devel Mailinglist
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-06-13 18:17 UTC by NathanSmith_2003
Modified: 2011-05-27 17:45 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description NathanSmith_2003 2003-06-13 18:17:07 UTC
Version:            (using KDE KDE 3.1.2)
Installed from:    Compiled From Sources
Compiler:          gcc 2.96 
OS:          Linux

Bug:

Starting with (in my experience) kde 3.1, when printing, the warning message: "No such map printers.conf.byname. Reason: No such map in server's domain" is displayed. This is related to NIS. In kdelibs-3.1.2/kdeprint/lpdunix/kmlpdunixmanager.cpp:getEtcPrintersConfName(), a ypcat command is issued "ypcat printers.conf.byname > %1" to read the printer configuration file stored on the NIS server. However, for networks where the NIS server does not contain a printers.conf.byname file, ypcat will produce the above error and send it to stderr.

How it exhibits itself:

This is normally not a problem. However, when printing from some applications, such as acroread, they pick up this message as an error in printing and display a warning message box. The printing usually procedes without problem but this leaves a somewhat lacking user experience.

Solution?:

A simple solution is to change the command to "ypcat printers.conf.byname > %1 2>&1" which will send both stdout and stderr to the %1 sink. Parsing of the return may be required to determine whether or not printers.conf was actually successfully retrieved.
Comment 1 Cristian Tibirna 2005-08-22 21:54:03 UTC
UNCONFIRMED (batch reassigning messed this)
Comment 2 John Layt 2011-05-27 17:45:59 UTC
KDEPrint is obsolete, unmaintained and will never be revived.  Closing all open bugs.