public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Francesco Talamona <ti.liame@email.it>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: Newly emerged cups 1.2.1-r2 won't print, won't talk to admin tools
Date: Sat, 8 Jul 2006 00:41:27 +0200	[thread overview]
Message-ID: <200607080041.27366.ti.liame@email.it> (raw)
In-Reply-To: <9acccfe50607071508k5331c3ben538a94186210d3fe@mail.gmail.com>

On Saturday 08 July 2006 00:08, Kevin O'Gorman wrote:
> 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?
Really strange, it seem a cupsd process is responding some way

Is it there something listenting on port 631?

cribrum ~ # /etc/init.d/cupsd stop
 * Stopping cupsd ...                                                                                             
[ ok ]
cribrum ~ # lpstat -t
lpstat: Unable to connect to server

> 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.
Side notes: 
1) I had to generate /etc/cups/ssl/server.crt 
and /etc/cups/ssl/server.key by hand to connect via https web 
interface.

2) did you follow ewarn hints?
[...]
 * 
 * The configuration changed with cups-1.2, you may want to save the old
 * one and start from scratch:
 * # mv /etc/cups /etc/cups.orig; emerge -va1 cups
 * 
 * You need to rebuild kdelibs for kdeprinter to work with cups-1.2
 * 
 * /usr/lib/cups exists - You need to remerge every ebuild that
 * installed into /usr/lib/cups and /etc/cups, qfile is in 
portage-utils:
 * # FEATURES=-collision-protect emerge -va1 
$(qfile -qC /usr/lib/cups /etc/cups | sed "s:net-print/cups$::")
 * 
[...]

ciao
	Francesco
-- 
Linux Version 2.6.17-gentoo-r1, Compiled #1 PREEMPT Mon Jul 3 22:29:51 
CEST 2006
One 2.2GHz AMD Athlon 64 Processor, 2GB RAM, 4410.66 Bogomips Total
aemaeth
-- 
gentoo-user@gentoo.org mailing list



  reply	other threads:[~2006-07-07 23:18 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-07 22:08 [gentoo-user] Newly emerged cups 1.2.1-r2 won't print, won't talk to admin tools Kevin O'Gorman
2006-07-07 22:41 ` Francesco Talamona [this message]
2006-07-08  2:04   ` [gentoo-user] " 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=200607080041.27366.ti.liame@email.it \
    --to=ti.liame@email.it \
    --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