HELP PLEASE!! Can't control CUPS??? WTF??
Stacy Walrip
> Suse 9.0 Professional using KDE (all up-to-date) kernel 2.4.X
> I've got bad print jobs que'd up in cups and I can NOT kill them.
> When I go to cups as localhost:631/admin and try to log in as
> administrator or root or ANYONE at all it will NOT let me in and I can NOT
> kill the print jobs, I get "client-error-forbidden"..
>
This was kind of complicated for me to fix for myself but in the /etc/cups/
directory their is a file called cups.conf, you have to edit this file and
select browser allow and set authentication to nothing or something like
that, read through the file and the comments can help walk you through it.
A google search for <browser allow CUPS> should help get you started also.
For a quick fix, you can app menu to control center,select peripherals,then
printers, click on administrator tab enter root password, and then select
the printer and delete the jobs under the jobs tab.
SuSE as well as many other distros disable CUPS browsing on default. Why? I
have NO IDEA! Frustrating isn't it?
Hope this helps,
Stacy
John McC
> Suse 9.0 Professional using KDE (all up-to-date) kernel 2.4.X
> I've got bad print jobs que'd up in cups and I can NOT kill them.
> When I go to cups as localhost:631/admin and try to log in as administrator
> or root or ANYONE at all it will NOT let me in and I can NOT kill the print
> jobs, I get "client-error-forbidden"..
>
> It will not take any password or username that I give it.
> I've removed CUPS through Yast and deleted the cups directories where ever I
> could find them on the system then reinstalled.
>
> NOTHING that I do will give me full control of CUPS again.
>
> I can print but when it screws up then I'm screwed. I have to let the
> printer spew hundreds of bad pages (thinking it's a postscript printer when
> it's not) until the job clears out of the que on it's on.
>
> This sucks. I mean sucks bad. I have a dozens and dozens of laser printers
> and big plotters that I have to test and when they don't work right I am
> screwed...
>
> I've GOT to get control of cups again, I even tried the KDE printing manager
> and it won't let me kill jobs there either...
> I get this from the print manager,
>
> "Unable to perform action "Remove" on selected jobs. Error received from
> manager:
> You don't have access to the requested resource."
>
>
> Well no shit Sherlock...
>
> HELP!!!
I've had problems printing in SuSE 9.0 Professional too. I usually have
to go into "KJobViewer" and delete the print job, unplug the printer USB
cable, go into Yast and remove the printer, plug the USB cable back in,
reinstall the printer in Yast and start the print job again. This
rediculous procedure takes time and is annoying. The printer
(Samsung ML1210 ) works perfectly in Windows. And it starts out perfectly
in SuSE too, but stops after three or four print jobs. Reinstalling SuSE
Linux from scratch doesn't help. Something is broken.
Tim Kynerd
Having used CUPS in SuSE 8.2 with no problems (I was surprised at how easy
it was to get it working), I was disappointed to find that I couldn't get
it to work in 9.0. I switched from CUPS to LPRng and my printer now works
again with no problems. I haven't needed to do anything advanced, though;
it's just a parallel printer connected directly to the computer, and I
haven't even needed to control it in any way -- well, I did need to cancel
some jobs yesterday, but I just used lprm and it worked fine.
My -:02.
--
Tim Kynerd Sundbyberg (småstan i storstan), Sweden tky...@spamcop.net
Sunrise in Stockholm today: 8:23
Sunset in Stockholm today: 15:35
My rail transit photos at http://www.kynerd.nu
Jim Anderson
> Thanks, I'll try this and let you know...
>
> Cheers!
During the SuSE 9.0 install there is a readme screen near then end of
the process that tells about the permission changes in 9.0 for CUPS
printing but, unfortunately, I didn't make notes. Apparently the
default print administrator for the browser is not root!
Anywho, I've had no problem killing my jobs in KJobViewer. As far as
installing printing to CUPS, I had no problem installing my networked
(HP JetDirects) Brother HL1440 laser and my Epson C82 with Yast.
Joseph David
> I've had problems printing in SuSE 9.0 Professional too. I usually have
> to go into "KJobViewer" and delete the print job, unplug the printer USB
> cable, go into Yast and remove the printer, plug the USB cable back in,
> reinstall the printer in Yast and start the print job again. This
> rediculous procedure takes time and is annoying. The printer
> (Samsung ML1210 ) works perfectly in Windows. And it starts out perfectly
> in SuSE too, but stops after three or four print jobs. Reinstalling SuSE
> Linux from scratch doesn't help. Something is broken.
I have a Samsung ML 1430 printer that give me trouble also. It seems that
after completing a print job, the printer "stops". When I go into the
Control Center>Peripherals>Printers>Administrator Mode I can restart it,
but only after it has gone into it's powersave mode (about 5 minutes
later). If I've sent a few jobs to the printer, it will print one job,
then stop again. I have to wait another 5 minutes or so, restart the
printer, print the next job, and so on. It always stops when there are
print jobs in the queue, and will only print one of those jobs each time I
restart the printer. Needless to say, this is annoying. Perhaps the
latest Samsung drivers would help.?
Michael Pokraka
> Suse 9.0 Professional using KDE (all up-to-date) kernel 2.4.X
> I've got bad print jobs que'd up in cups and I can NOT kill them.
> When I go to cups as localhost:631/admin and try to log in as
> administrator or root or ANYONE at all it will NOT let me in and I can NOT
> kill the print jobs, I get "client-error-forbidden".
The change to CUPS is one of the big readme items after installation of Suse
9.0. Pop on over to Suse's support database and type in cups, the third
item is
Printer Configuration from SUSE LINUX 9.0 on
I've quoted some of the relevant bits below, but it's basically secure by
default, you need a seperate password.
Cheers
Mike
cupsd Runs as the User lp
On start-up, cupsd changes from the user root to the user lp as specified
in /etc/cups/cupsd.conf:
User lp
Group lp
RunAsUser Yes
If "RunAsUser" is set to "No", cupsd will continue to run as root.
Advantage:
Improved security, as the CUPS print service does not run with unlimited
permissions, but only with permissions needed for the print service.
Disadvantage:
The authentication (the password verification) cannot take place via /etc
shadow, as lp does not have access to /etc/shadow. Rather, the
CUPS-specific authentication via /etc/cups/passwd.md5 must be used. In
etc/cups/cupsd.conf, this can be specified as follows:
<Location /admin>
AuthType BasicDigest
AuthClass Group
AuthGroupName sys
...
</Location>
Additionally, the following command must be used (as the user root) to
enter a CUPS-specific password for the user root in /etc/cups/passwd.md5:
lppasswd -g sys -a root
If "AuthType" is set to "Basic", the password verification will take place
with /etc/shadow. In this case, cupsd must run as root (i.e., "RunAsUser
No").