Red Hat Bugzilla – Bug 245642
NCP printer option on cups system-config-printer
Last modified: 2008-08-02 19:40:37 EDT
Description of problem: There is no option NCP on system-config-printer. There
was on the old versions of Fedora. But now there is all other options, except
I've installed ipx-utils and ncpfs. I can mount the volume perfectly, but thereś
no NCP option on system-config-printer.
The command pqlist works fine.
how can I print in a novell queue?
Did you find the problem? Did it happened with you?
Hi, yes, I have reproduced it. We need to ship CUPS backend for NCP (probably
wrapper around nprint). But please be patient, I have a lot of urgent work now...
Sorry about the insistence.
I realy don´t want boring you. But the functions of the printer is realy
important to me, and I think to lots of people.
Is there any other option, how to print in a NCP printer without that backend
Or do you have a preview when the packet will be available?
Thank you very much,
I don´t know how can I ask in a polite way. But, any new?
I spare some time and here is what I discover...
CUPS backend for NCP already exists (file /usr/lib/cups/backend/ncp).
system-config-printer gets list of devices by running this script without
parametres. This part of script is invoked:
if [ -z "$*" ]
# This is where we would enumerate all the URIs we support.
# Patches welcome.
So here is IMHO the problem, the script do actually nothig. It's owned by cups
package, so maybe maintaner of cups package can tell us more.
Another thing -- it's possible, that GUI for setting NCP in
system-config-printer doesn't exist too.
Can you print manually with those commands -- pqlist, pserver, pqstat, pqrm,
nprint from ncpfs package?
The information we've requested above is required in order
to review this problem report further and diagnose/fix the
issue if it is still present. Since there have not been any
updates to the report since thirty (30) days or more since we
requested additional information, we're assuming the problem
is either no longer present in the current Fedora release, or
that there is no longer any interest in tracking the problem.
Setting status to "CLOSED INSUFFICIENT_DATA". If you still
experience this problem after updating to our latest Fedora
release and can provide the information previously requested,
please feel free to reopen the bug report.
Thank you in advance.
Note that maintenance for Fedora 7 will end 30 days after the GA of Fedora 9.