unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Kyle Andrews <kyle.c.andrews@gmail.com>
To: "Wiktor Żelazny" <wz@freeshell.de>
Cc: help-guix@gnu.org
Subject: Re: Printer configuration
Date: Fri, 26 Jun 2020 18:12:23 -0400	[thread overview]
Message-ID: <87ftahlbnc.fsf@gmail.com> (raw)
In-Reply-To: <20200626194213.ukctcxxg42tzmxbb@wzguix>


Wiktor Żelazny writes:

> On Fri, Jun 26, 2020 at 02:13:14PM -0400, Kyle Andrews wrote:
>>
>> Wiktor Żelazny writes:
>>
>> > Does /gnu/store/.../cups/filter/rastertoqpdl exist?
>>
>> Yes, it exists in the splix package, but not in the cups package.
>> Looking at the Guix source code I saw that ~system-config-printer~ (in
>> ~guix/gnu/packages/gnome.scm~) takes input from cups on build, but not
>> from splix or other print drivers. Could that be part of the problem?
>
> I wouldn’t be surprised. On the other hand, it does not import other
> extensions, such as hplip and foomatic-filters, either.
>
> Did you run guix system reconfigure after adding the packages to
> config.scm? Did you try removing and adding the printer again
> afterwards?
>
> Does a /var/guix/profiles/system/profile/lib/cups/filter/rastertoqpdl
> symlink exist in your filesystem? I think you could try changing the
> rastertoqpdl path defined in the system-config-printer configuration (or
> CUPS configuration, assuming it’s just a CUPS GUI frontend) from
> /gnu/store/… to that path. /gnu/store/ contents are volatile. Again,
> just guessing; perhaps the path is hardcoded into the CUPS/splix build
> and uneditable.
>
> WŻ

Hi WZ,

> Did you run guix system reconfigure after adding the packages to
> config.scm? Did you try removing and adding the printer again
> afterwards?

I did reconfigure, but I didn't try removing and adding the printer
again.

> Does a /var/guix/profiles/system/profile/lib/cups/filter/rastertoqpdl
> symlink exist in your filesystem? I think you could try changing the
> rastertoqpdl path defined in the system-config-printer configuration (or
> CUPS configuration, assuming it’s just a CUPS GUI frontend) from
> /gnu/store/… to that path. /gnu/store/ contents are volatile. Again,
> just guessing; perhaps the path is hardcoded into the CUPS/splix build
> and uneditable.

It does appear to exist. Actually, I figured out how to successfully
print a document using ~libreoffice --headless -p test.odt~. So, I think
my printer problem is actually reflecting a problem with
system-config-printer.

Kyle



  reply	other threads:[~2020-06-26 22:27 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-26  2:11 Printer configuration Kyle Andrews
2020-06-26  3:06 ` Kyle Andrews
2020-06-26  7:32 ` Wiktor Żelazny
2020-06-26 16:56   ` Kyle Andrews
2020-06-26 17:27     ` Wiktor Żelazny
2020-06-26 18:13       ` Kyle Andrews
2020-06-26 19:42         ` Wiktor Żelazny
2020-06-26 22:12           ` Kyle Andrews [this message]
2020-06-27  7:02             ` Wiktor Żelazny
2020-06-27 16:02               ` Kyle Andrews
2020-06-26 20:19         ` Tobias Geerinckx-Rice

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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87ftahlbnc.fsf@gmail.com \
    --to=kyle.c.andrews@gmail.com \
    --cc=help-guix@gnu.org \
    --cc=wz@freeshell.de \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).