unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Peter <stuffbox@tpg.com.au>
To: Tobias Geerinckx-Rice <me@tobias.gr>
Cc: help-guix@gnu.org
Subject: Re: Guix Printing Problems
Date: Fri, 24 Sep 2021 04:50:14 +1000	[thread overview]
Message-ID: <DAFA5CE4-9A3A-4892-B82E-36DDBB0A3CFE@tpg.com.au> (raw)
In-Reply-To: <871r5f8ohg.fsf@nckx>

Hi Tobias

Thanks very much for your response.

Sadly, my situation is unchanged. Not entirely unchanged, as your suggestions helped me realise what I was doing wrong regarding the web-interface. I can now access the full CUPS data via http://localhost:631, but all that gives me is more commands to try that Guix won't run! Advice I can't follow.

I added 'lp' (and also 'lpadmin' from someone else's suggestion) to the groups section, but that's made no difference either. The annoying reality remains: the system can host the discovery of every imaginable detail about the printer -- down to how many pages I've ever printed! -- but having made sufficient connection to pull in all that data, claims it cannot find the printer. Checkmate. Nonsense.

On the good side, I've learned a lot during the struggle, and I'll leave the installation in place for the moment. However, unless something turns up to turn 'foxed' into 'fixed', a system that doesn't print just isn't practical.

Can we persuade the legendary RMS to turn his fruitful attention to the cause he promotes!

But sincere thanks once again, and all the best to you and yours.

Peter



  reply	other threads:[~2021-09-23 19:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-23 11:30 Guix Printing Problems Peter
2021-09-23 12:11 ` Tobias Geerinckx-Rice
2021-09-23 18:50   ` Peter [this message]
2021-09-23 12:16 ` Efraim Flashner

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=DAFA5CE4-9A3A-4892-B82E-36DDBB0A3CFE@tpg.com.au \
    --to=stuffbox@tpg.com.au \
    --cc=help-guix@gnu.org \
    --cc=me@tobias.gr \
    /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).