On 02/01/2014 05:32 PM, David C. Rankin wrote:
On 01/30/2014 07:44 PM, Darrell Anderson wrote:
Share the exact steps.
That you see a list of available printers probably means CUPS is
configured correctly.
My printer is connected as a network device. After you share the
exact steps I'll try to duplicate here.
Darrell
Open Start Menu -> Print System -> Print Manager (or use kcontol)
**Administrator Mode**
Add Printer/Class
(Wizard Appears)
Remote CUPS Server (IPP/HTTP) -> Next
Normal user: david/pw -> Next
Host: nirvana/Port: 631 -> Next
Choose Printer: LaserJet -> Next
'Printer Model Selection' (2-pane window) Manufacturer on Rt. Model on Lt.
You see momentary 'Loading....' in Lt. window, then nothing, both panes blank
Cancel/Cancel can't go any further
**Normal Mode**
Add Printer/Class
(Wizard Appears)
Remote CUPS Server (IPP/HTTP) -> Next
Normal user: david/pw -> Next
Host: nirvana/Port: 631 -> Next
Choose Printer: LaserJet -> Next
'Printer Model Selection' (2-pane window) Manufacturer on Rt. Model on Lt.
Choose: Manuf->HP Model->Laserjet 4 -> Next
Choose: HP Laserjet 4 (Foomatic + hplip) [recommended] -> Next
Error Dialog:
Unable to load the requested driver:
Unable to create the Foomatic driver [HP-LaserJet_4,hplip]. Either that driver
does not exist, or you don't have the required permissions to perform that
operation.
Now on 'Printer Test' Page after error
[Test] - It prints! (top margin a bit off, but it prints)
Finish with Name Printer, etc. and printer added to kprinter dialog.
$ lpstat -a
HPLaserjet4 accepting request since Sat 01 Feb 2014 05:28:39 PM CST
Test printing from kwrite - OK
So I do get a working printer installed, I just get a Error Dialog telling me it
isn't going to work... That's a new one. Any thoughts?
And... the only reason I got a working printer is I made myself a member of the
'sys' group otherwise creation of /etc/cups/printer.conf would have failed due
to lack of permission. Since I was a member of the sys group, permission for
cups operation was satisfied, however, apparently printer driver generation with
the 'foomatic-db-generation' package uses another scheme prompting the error.
How to solve for a normal user?
--
David C. Rankin, J.D.,P.E.