public inbox for gentoo-amd64@lists.gentoo.org
 help / color / mirror / Atom feed
From: Paul Stear <gentoo@appjaws.plus.com>
To: gentoo-amd64@lists.gentoo.org
Subject: Re: [gentoo-amd64] printing has stopped
Date: Fri, 7 Dec 2007 16:42:56 +0000	[thread overview]
Message-ID: <200712071642.56596.gentoo@appjaws.plus.com> (raw)
In-Reply-To: <5bdc1c8b0712070759x640dd70exa459e9a1fb777dad@mail.gmail.com>

On Friday 07 December 2007, Mark Knecht wrote:
> On Dec 7, 2007 6:33 AM, Paul Stear <gentoo@appjaws.plus.com> wrote:
> > Hi all,
> > This is weird, all of a sudden my printing has stopped working. Now
> > I'm not sure if this is as a result of updates or I have finger
> > trouble (probably this).
> > Anyway it appears that cups isn't working, I get this error:-
> > An error occurred while loading http://localhost:631/printers:
> > Connection to host localhost is broken.
> >
> > I have reinstalled cups, restarted cupsd,checked cups.conf and it
> > seems ok so I think I have done something that has affected
> > localhost, but I can't find anything wrong.
> > Here is my /etc/hosts:-
> >
> > # IPv4 and IPv6 localhost aliases
> > #127.0.0.1      localhost
> > 127.0.0.1       PC2.HOMENET     PC2     localhost
> > #::1    localhost
> >
> > I just don't know what to do next, any help appreciated
<snip>
> I had problems recently with updates to cups. I think I had to
> uninstall my printer and then reinstall it. Don't really remember.
>
> Linux printing - the least fun thing about Linux. ;-)
>
> - Mark

Thanks for the reply Mark.
I have this error in the error_log:-
I [07/Dec/2007:16:08:23 +0000] Full reload complete.
I [07/Dec/2007:16:08:23 +0000] Listening to 127.0.0.1:631 on fd 3...
I [07/Dec/2007:16:08:23 +0000] Listening to /var/run/cups/cups.sock on fd 
4...
I [07/Dec/2007:16:08:35 +0000] commptr=""
I [07/Dec/2007:16:08:35 +0000] 
Started "/usr/lib64/cups/cgi-bin/printers.cgi" (pid=9388)
E [07/Dec/2007:16:08:35 +0000] PID 9388 
(/usr/lib64/cups/cgi-bin/printers.cgi) stopped with status 22!
I [07/Dec/2007:16:08:35 +0000] Hint: Try setting the LogLevel to "debug" 
to find out more.

Any ideas?????
Thanks
Paul

-- 
This message has been sent using kmail with gentoo linux
-- 
gentoo-amd64@gentoo.org mailing list



  reply	other threads:[~2007-12-07 16:44 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-07 14:33 [gentoo-amd64] printing has stopped Paul Stear
2007-12-07 15:59 ` Mark Knecht
2007-12-07 16:42   ` Paul Stear [this message]
2007-12-07 17:09   ` Paul Stear
2007-12-07 17:16     ` Avuton Olrich
2007-12-07 17:57     ` Mark Knecht
2007-12-07 20:06       ` Chris Traylor
2007-12-08 11:56         ` Paul Stear
2007-12-08 18:37           ` Beso
2007-12-08 19:46             ` David Abbott
2007-12-08 20:30               ` Beso
2007-12-09  0:42                 ` [gentoo-amd64] " Duncan
2007-12-09  1:01           ` [gentoo-amd64] " David Fellows
2007-12-09  2:39           ` David Fellows
2007-12-09 13:26           ` [gentoo-amd64] printing has stopped - RESOLVED? Paul Stear
     [not found] ` <200712091235.05816.gentoo@appjaws.plus.com>
     [not found]   ` <200712091547.lB9FlFfQ019906@mailserv.unb.ca>
2007-12-09 16:39     ` [gentoo-amd64] printing has stopped Paul Stear
2007-12-09 16:47       ` Paul Stear
2007-12-10  1:20         ` David Fellows
2007-12-10  8:51           ` Paul Stear
2007-12-10 14:19             ` Mark Knecht

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200712071642.56596.gentoo@appjaws.plus.com \
    --to=gentoo@appjaws.plus.com \
    --cc=gentoo-amd64@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox