public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: gottlieb@nyu.edu
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] trouble installing cups
Date: Mon, 16 Sep 2013 18:28:05 -0400	[thread overview]
Message-ID: <874n9kqu4q.fsf@nyu.edu> (raw)

When I reinstall CUPS /etc/cups/cupsd.conf is *not* updated.
Details follow.

Cups was behaving badly: the web interface could not be used.  The
browser would quickly say no process was listening on localhost:631

I compared cupsd.conf to the same file on another working system and
noticed the following differences

  1. *Many* pairs of lines were missing.  The first line of each pair
     was blank; the second a comment.  Presumably this has no effect.

  2. The initial block comment was missing.  Again no effect.

  3. One very influential change
       Listen localhost:631
     was replaced by a second copy of
       Listen /run/cups/cups.sock
     When I manually put back localhost:631
     the cups web interface again behaved normally.

  4. The following block was *added* at the end
        JobPrivateAccess default
        JobPrivateValues default
        MaxLogSize 2000000
        SubscriptionPrivateAccess default
        SubscriptionPrivateValues default

     The first, second, fourth, and fifth generated "Unknown directive"
     messages in /var/log/cups/error.log

So I reinstalled cups but /etc/cups/cupd.conf was not changed and still
has its old date and contents.  The merge looks clean (output below)

I am wondering if there is something wrong with my setup.
I have the userpriv feature enabled.

Any help would be appreciated.
thanks,
allan

================================================================

 * Messages for package net-print/cups-1.6.3-r2:

 * Package:    net-print/cups-1.6.3-r2
 * Repository: gentoo
 * Maintainer: printing@gentoo.org
 * USE:        X acl amd64 dbus elibc_glibc filters kernel_linux pam python_single_target_python2_7 python_targets_python2_7 ssl threads usb userland_GNU
 * FEATURES:   preserve-libs sandbox userpriv usersandbox
 * Determining the location of the kernel source code
 * Found kernel source directory:
 *     /usr/src/linux
 * Found sources for kernel version:
 *     3.11.0-gentoo-rcs-1.3
 * Applying cups-1.6.0-dont-compress-manpages.patch ...
 * Applying cups-1.6.0-fix-install-perms.patch ...
 * Applying cups-1.4.4-nostrip.patch ...
 * Applying cups-1.5.0-systemd-socket-2.patch ...
 * Applying cups-1.6.2-statedir.patch ...
 * Applying cups-1.6.3-colord-profile.patch ...
 * Running aclocal -I config-scripts ...
 * Running autoconf ...
 * LANGS="ca es fr ja ru"
 * LINGUAS=""
 * Skipping make test/check due to ebuild restriction.
 * Updating icons cache ...
 * Updating desktop mime database ...
>>> Auto-cleaning packages...


             reply	other threads:[~2013-09-16 22:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-16 22:28 gottlieb [this message]
2013-09-16 23:39 ` [gentoo-user] trouble installing cups Neil Bothwick
2013-09-17  1:23   ` gottlieb
2013-09-17  9:22     ` Neil Bothwick
2013-09-17 15:17       ` gottlieb

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=874n9kqu4q.fsf@nyu.edu \
    --to=gottlieb@nyu.edu \
    --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