From: "Kevin O'Gorman" <kogorman@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Newly emerged cups 1.2.1-r2 won't print, won't talk to admin tools
Date: Fri, 7 Jul 2006 15:08:01 -0700 [thread overview]
Message-ID: <9acccfe50607071508k5331c3ben538a94186210d3fe@mail.gmail.com> (raw)
Yesterday, I emerged cups 1.2.1-r2. Now I cannot print at all.
I use KDE, and the configuration tools cannot make a connection.
Even bare-bones init stuff doesn't work right:
/etc/init.d/cupsd stop
says it stopped the server, but
/etc/init.d/cupsd start
WARNING: "cupsd" has already been started
but 'ps' show that it has NOT been started.
lpstat -t
shows confusing info about my printer:
treat init.d # lpstat -t
scheduler is running
system default destination: lp0
device for lp0: parallel:/dev/lp0
device for lp0: /dev/null
lp0 not accepting requests since Fri Jul 7 14:23:34 2006 -
Paused
lp0 accepting requests since Fri Jul 7 14:15:50 2006
printer lp0 disabled since Fri Jul 7 14:23:34 2006 -
Paused
printer lp0 is idle. enabled since Fri Jul 7 14:15:50 2006
lp0-2458 root 14336 Fri Jul 7 14:21:24 2006
lp0-2459 root 14336 Fri Jul 7 14:55:25 2006
treat init.d #
SO: is it enabled or not?
I guess I'll submit a bug, but I'd like to know if it's best to go
back to cups-1.1.23-r7,
which I had before, and for which I have a binary package.
++ kevin
--
Kevin O'Gorman, PhD
--
gentoo-user@gentoo.org mailing list
next reply other threads:[~2006-07-07 22:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-07 22:08 Kevin O'Gorman [this message]
2006-07-07 22:41 ` [gentoo-user] Re: Newly emerged cups 1.2.1-r2 won't print, won't talk to admin tools Francesco Talamona
2006-07-08 2:04 ` Kevin O'Gorman
2006-07-08 4:12 ` Kevin O'Gorman
2006-07-08 6:08 ` Francesco Talamona
2006-07-08 16:41 ` Kevin O'Gorman
2006-07-07 22:44 ` Kevin O'Gorman
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=9acccfe50607071508k5331c3ben538a94186210d3fe@mail.gmail.com \
--to=kogorman@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