public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Alan E. Davis" <lngndvs@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] CUPS problem
Date: Sun, 6 Jan 2008 13:27:13 +1000	[thread overview]
Message-ID: <7bef1f890801051927k1ec28f62u7b3f477bcb779aa1@mail.gmail.com> (raw)

CUPS has been working flawlessly for quite some time, one of the feats
of newer GNU/Linux installs (to one who couldn't get an HP mainstream
inkjet working right some 10 years ago).    Simultaneously, I notices
that Apple now owns the copyright, and after a recent upgrade, stopped
working.

I have to blame myself, because running cfg-update, the changes to
/etc/cups/cupsd.conf were considerable, involving three, and not two
files to be merged.  The interface of xxdiff is not intuitive, to me:
I've blundered through it's kludgey structure for a while, but this
time I was genuinely confused.  Furthermore, I made the mistake of
taking a stab in the dark.

So I uninstalled CUPS completely, and reinstalled.  Then installed the
printer again.  It is doing the same thing: the interface at
localhost:631 says that the printer is ready to print.  Any job sent
to the queue, including test prints, are immediately "stopped".
Reprint a job, and it is immediately stopped.

Hypotheses:
   New ASUS M2N-E Motherboard (was working before upgrading CUPS)
   Configuration file issues.  (I have deleted the entire directory
/etc/cups, and the new derault file was replaced with a simplified one
scavenged of a mailing list, but with no improvement.
   Unknown factors (where to start?)

So I am turning to the mailing list for suggestions.

Any ideas?

Thank you,

Alan Davis

-- 
Alan Davis, Kagman High School, Saipan  lngndvs@gmail.com

"It's never a matter of liking or disliking ..."
       ---Santa Ynez Chumash Medicine Man
-- 
gentoo-user@lists.gentoo.org mailing list



             reply	other threads:[~2008-01-06  7:43 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-06  3:27 Alan E. Davis [this message]
2008-01-06  8:00 ` [gentoo-user] CUPS problem Dale
2008-01-06 16:48   ` Mick
2008-01-07  0:00     ` Alan E. Davis
2008-01-07  0:24       ` Dale
2008-01-07  0:44         ` Alan E. Davis
2008-01-07  1:02           ` Dale
2008-01-07  5:06         ` Randy Barlow
2008-01-07  5:25           ` Dale
2008-01-07  5:32             ` Randy Barlow
2008-01-07  5:53               ` Dale
2008-01-08  9:56                 ` Mick
2008-01-08 23:43                   ` Alan E. Davis
2008-01-09  5:51                     ` Randy Barlow
2008-01-09 11:01                       ` Alan E. Davis
2008-01-09 13:00                     ` Mick
2008-01-09 13:09                       ` Alan E. Davis
2008-01-09 14:11                         ` Alan McKinnon
  -- strict thread matches above, loose matches on Subject: below --
2007-12-07 19:45 [gentoo-user] cups problem Roger Mason
2007-12-07 19:57 ` Billy Holmes
2007-12-07 20:42   ` Roger Mason
2007-12-07 20:53     ` Billy Holmes
2007-12-07 21:56 ` Randy Barlow
2007-12-08 12:23   ` Roger Mason
     [not found] <200609260955.20095.gentoo@appjaws.plus.com>
2006-09-26 13:58 ` Boyd Stephen Smith Jr.
2006-06-25  0:28 Michael W. Holdeman
2006-06-25  1:21 ` darren kirby
2006-06-25  2:01   ` Michael W. Holdeman
2006-06-25  3:19     ` darren kirby

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=7bef1f890801051927k1ec28f62u7b3f477bcb779aa1@mail.gmail.com \
    --to=lngndvs@gmail.com \
    --cc=gentoo-user@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