From: ludo@gnu.org (Ludovic Courtès)
To: Oleg Pykhalov <go.wigust@gmail.com>
Cc: 33105@debbugs.gnu.org
Subject: bug#33105: cups Can't create temporary file or stopped "Filter failed"
Date: Wed, 24 Oct 2018 14:52:22 +0200 [thread overview]
Message-ID: <877ei75wxl.fsf@gnu.org> (raw)
In-Reply-To: <87woqcea7q.fsf@gmail.com> (Oleg Pykhalov's message of "Sat, 20 Oct 2018 21:36:57 +0300")
Hi Oleg,
Oleg Pykhalov <go.wigust@gmail.com> skribis:
> I read gnu/services/cups.scm and found that the /var/spool/cups/
> directory should be owned by ‘lp’ user:
>
> (define %cups-activation
> ;; Activation gexp.
> (with-imported-modules '((guix build utils))
> #~(begin
> (use-modules (guix build utils))
> (define (mkdir-p/perms directory owner perms)
> (mkdir-p directory)
> (chown "/var/run/cups" (passwd:uid owner) (passwd:gid owner))
> ;; ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> (chmod directory perms))
> ;; …
> (let ((user (getpwnam "lp")))
> ;; …
> (mkdir-p/perms "/var/spool/cups/tmp" user #o755) ; <----------
> ;; …
> ))))
>
>
>
> Maybe we should make /var/spool/cups/tmp directory owned by ‘lp’ user,
> too? WDYT?
>
> Test page was printed successfully with:
>
> $ sudo ls -ld /var/spool/cups/tmp
> drwxr-xr-x 2 lp lp 4096 Oct 20 21:20 /var/spool/cups/tmp
I don’t know the answer :-), but from what you’re saying, it looks like
making /var/spool/cups/tmp ‘lp’-owned is the right thing.
If it works for you, I guess you can go ahead!
Ludo’.
prev parent reply other threads:[~2018-10-24 12:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-20 18:36 bug#33105: cups Can't create temporary file or stopped "Filter failed" Oleg Pykhalov
2018-10-21 6:53 ` Efraim Flashner
2018-10-24 12:52 ` Ludovic Courtès [this message]
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=877ei75wxl.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=33105@debbugs.gnu.org \
--cc=go.wigust@gmail.com \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.