On Wednesday 25 October 2006 14:52, Gustin Johnson wrote:
> I used to work at a software company many moons ago.  One of the best
> errors they had was "Something happened somewhere".
>

Sounds like an error on that other OS. "Something broke in a DLL. <insert 
useless cryptographic error number>".

Or, that site you ran across...

"No info available.....was this helpful?"

My personal favorite from way back, "Who is General Failure and why is He 
reading my disk?"

> [EMAIL PROTECTED] wrote:
> > Sometimes I like to think that "nothing" has changed, but that's never
> > the case. If nothing had changed then it wouldn't have stopped working.
> > *You* may not have done anything, but something did something to
> > something.
> >
> > Not helpful, I know.
> >
> > J
> >
> > Original Message:
> > -----------------
> > From: Mitchell Brown [EMAIL PROTECTED]
> > Date: Wed, 25 Oct 2006 14:22:00 -0600
> > To: [email protected]
> > Subject: Re: [clug-talk] All of a sudden
> >
> >
> > Thanks Gustin. Even if I did know how to clear the jobs from the cline,
> > it won't let me print anything. Windows won't un"pause" it, and I have no
> > idea why. My config file is intact, and I haven't updated the machine
> > since God knows when (thats another story)... So, I beg to differ  -- --
> > nothing has changed :-/
> >
> > On 10/25/06, Gustin Johnson <[EMAIL PROTECTED]> wrote:
> > The errors pretty much tell the story:
> > "access denied"
> >
> > admin request on bad
> > resource '/printers/SAM'
> >
> > "anonymous" not
> > authorized to delete job id 382 owned by "Mitchell"
> >
> > Likely you will need to login to the Linux server and kill jobs from
> > there.  It would probably be a good idea to dig into the cups
> > documentation.
> >
> > Also, I am not sure how PCLinuxOS handles updates/upgrades.  What sold
> > me on Debian many years ago was that upgrades did not blow away my
> > configs when upgrading packages (something that both Gentoo and
> > Slackware did to me at very inopportune moments).  This may have
> > happened to you.
> >
> > *Something* happened, you just have to figure out what.
> >
> > Mitchell Brown wrote:
> >>>> My printer doesn't work. It's been working fine since close to
> >>>> eternity. Now, nothing prints... My Windows machines list 35 jobs in
> >>>> the print queue, and show jobs from all users on the network. The
> >>>> "Pause printing" checkmark won't uncheck, and Cancel All Jobs doesn't
> >>>> work either - the bottom of the screen says "access denied" ...
> >>>>
> >>>> Print server (venus) is running PCLinuxOS (Mandriva)... The following
> >>>> is a short exerpt from the log:
> >>>>
> >>>>     E [25/Oct/2006:12:46:03 -0500] cancel_all_jobs: admin request on
> >>>> bad resource '/printers/SAM'!
> >>>>     E [25/Oct/2006:12:46:20 -0500] Unable to open /etc/cups/passwd.md5
> >>>> - No such file or directory
> >>>>     E [25/Oct/2006:12:46:20 -0500] cancel_job: "anonymous" not
> >>>>     authorized to delete job id 382 owned by "Mitchell"!
> >>>>     I [25/Oct/2006:12:46:33 -0500] Installing config file
> >>>>     "/etc/cups/cupsd.conf"...
> >>>>     I [25/Oct/2006:12:46:33 -0500] Loaded configuration file
> >>>>     "/etc/cups/cupsd.conf"
> >>>>     I [25/Oct/2006:12:46:33 -0500] Configured for up to 100 clients.
> >>>>     I [25/Oct/2006:12:46:33 -0500] Allowing up to 100 client
> >>>> connections per host.
> >>>>     I [25/Oct/2006:12:46:33 -0500] Partial reload complete.
> >>>>     I [25/Oct/2006:12:46:50 -0500] Adding start banner page "none" to
> >>>>     job 407.
> >>>>     I [25/Oct/2006:12:46:50 -0500] Adding end banner page "none" to
> >>>> job
> >
> > 407.
> >
> >>>>     I [25/Oct/2006:12:46:50 -0500] Job 407 queued on 'SAM' by
> >>>> 'Steven'. E [25/Oct/2006:12:47:10 -0500] cancel_all_jobs: admin
> >>>> request on bad resource '/printers/SAM'!
> >>>>     E [25/Oct/2006:12:47:17 -0500] Unable to open /etc/cups/passwd.md5
> >>>> - No such file or directory
> >>>>     E [25/Oct/2006:12:47:17 -0500] cancel_job: "anonymous" not
> >>>>     authorized to delete job id 372 owned by "Steven"!
> >>>>     E [25/Oct/2006:12:47:58 -0500] start_printer: admin request on bad
> >>>>     resource '/printers/SAM'!
> >>>>     E [25/Oct/2006:12:48:00 -0500] start_printer: admin request on bad
> >>>>     resource '/printers/SAM'!
> >>>>     E [25/Oct/2006:12:48:29 -0500] start_printer: admin request on bad
> >>>>     resource '/printers/sam'!
> >>>>     E [25/Oct/2006:12:48:32 -0500] cancel_all_jobs: admin request on
> >>>> bad resource '/printers/sam'!
> >>>>
> >>>>
> >>>> The printer name is "SAM" and my brother is "Steven" trying to print
> >>>> stuff. All settings are wide-open, there's no authentication
> >>>> whatsoever on this printer.
> >>>> Why is it all of a sudden not working? :(
> >>>>
> >>>>
> >>>> --
> >>>> pub 1024D/9091C422 02/05/2006 Mitchell Brown <[EMAIL PROTECTED]
> >>>> <mailto:[EMAIL PROTECTED]>>
> >>>>     Primary key fingerprint:  812B 94BC EA0D 345A CC1C 2ED9 F7F6 5CCF
> >>>> 9091 C422
> >>>>
> >>>>
> >>>> ----------------------------------------------------------------------
> >>>>--
> >>>>
> >>>> _______________________________________________
> >>>> clug-talk mailing list
> >>>> [email protected]
> >>>> http://clug.ca/mailman/listinfo/clug-talk_clug.ca
> >>>> Mailing List Guidelines (http://clug.ca/ml_guidelines.php)
> >>>> **Please remove these lines when replying
>
> _______________________________________________
> clug-talk mailing list
> [email protected]
> http://clug.ca/mailman/listinfo/clug-talk_clug.ca
> Mailing List Guidelines (http://clug.ca/ml_guidelines.php)
> **Please remove these lines when replying
>
>
>
> _______________________________________________
> clug-talk mailing list
> [email protected]
> http://clug.ca/mailman/listinfo/clug-talk_clug.ca
> Mailing List Guidelines (http://clug.ca/ml_guidelines.php)
> **Please remove these lines when replying

_______________________________________________
clug-talk mailing list
[email protected]
http://clug.ca/mailman/listinfo/clug-talk_clug.ca
Mailing List Guidelines (http://clug.ca/ml_guidelines.php)
**Please remove these lines when replying

Reply via email to