From: ludo@gnu.org (Ludovic Courtès)
To: Mekeor Melire <mekeor.melire@gmail.com>
Cc: 29219@debbugs.gnu.org
Subject: bug#29219: CUPS filter still can't access Ghostscript (gs)
Date: Thu, 09 Nov 2017 10:05:42 +0100 [thread overview]
Message-ID: <87r2t7q0t5.fsf@gnu.org> (raw)
In-Reply-To: <87efp8fqab.fsf@gmail.com> (Mekeor Melire's message of "Wed, 08 Nov 2017 21:50:52 +0100")
Hi,
Mekeor Melire <mekeor.melire@gmail.com> skribis:
> I added two printers through CUPS' web interface (localhost:631) using
> the PPD driver file which I downloaded (from openprinting.org): one
> called ljet4 (which calls Ghostscript) and one called Postscript (which
> just calls `cat`)⁰. The latter worked.
>
>
> But although I was expecting commit
> 1728c411718e3b358c06561d6e80b47d7b331617¹ to fix this issue, when I try
> the ljet4² driver, I still get this error in /var/log/cups/error_log³:
>
>
> sh: gs: command not found
> Process is dying with \"Unable to determine number of pages, page count: -1
> \", exit stat 3
>
>
> Is anybody able to reproduce this issue?
>
> How can I be sure that the cups-service I'm running is the recent one
> which includes that commit? (I tried pulling guix and rebuilding the
> system afterwards and restarting cups-service afterwards.)
Just make sure to reconfigure from a recent-enough commit (run ‘guix
--version’ as root to see which commit you’re using.)
If it turns out you’re already using CUPS with commit
1728c411718e3b358c06561d6e80b47d7b331617, could you reproduce the issue
while running “strace -p PID -f -s 345 -o log”, where PID is the PID of
cupsd as shown by ‘herd status cups’?
TIA!
Ludo’.
next prev parent reply other threads:[~2017-11-09 9:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-08 20:50 bug#29219: CUPS filter still can't access Ghostscript (gs) Mekeor Melire
2017-11-09 9:05 ` Ludovic Courtès [this message]
2017-11-09 19:19 ` Mekeor Melire
2017-11-10 12:22 ` Ludovic Courtès
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=87r2t7q0t5.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=29219@debbugs.gnu.org \
--cc=mekeor.melire@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.