From: MechDR <MechDR@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: hplip 3.22.10 broke my printer setup
Date: Fri, 27 Jan 2023 14:21:05 +0100 [thread overview]
Message-ID: <20230127132105.BEf8AqzcZs-vLkq9gcCtFJYVX-CpHDzs6YBDgGHeljQ@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-41695@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 661 bytes --]
New comment by MechDR on void-packages repository
https://github.com/void-linux/void-packages/issues/41695#issuecomment-1406499818
Comment:
@biopsin I have the nonfree repo installed, it's not there (shrug).
How do I provide error logs? lpr's verbose features were removed in earlier versions and debug features are not present in the version I have. Does it generate error logs? Or maybe error logs from the print queue... where do they reside?
On a side note, not related, I think the plugin is just a bunch of binaries spliced up in single plugin that provides support for various proprietary printing/scanning technologies. Correct me if I'm wrong.
next prev parent reply other threads:[~2023-01-27 13:21 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-17 16:38 [ISSUE] " MechDR
2023-01-17 16:44 ` paper42
2023-01-17 17:51 ` MechDR
2023-01-17 17:51 ` MechDR
2023-01-17 17:56 ` MechDR
2023-01-17 17:57 ` MechDR
2023-01-17 20:59 ` paper42
2023-01-17 21:00 ` paper42
2023-01-18 4:32 ` dataCobra
2023-01-18 4:38 ` dataCobra
2023-01-18 4:41 ` dataCobra
2023-01-18 4:51 ` biopsin
2023-01-23 7:28 ` dataCobra
2023-01-23 16:13 ` MechDR
2023-01-24 17:02 ` MechDR
2023-01-24 19:41 ` biopsin
2023-01-25 15:32 ` MechDR
2023-01-25 16:52 ` biopsin
2023-01-25 16:59 ` biopsin
2023-01-26 17:15 ` MechDR
2023-01-26 17:57 ` MechDR
2023-01-27 5:32 ` biopsin
2023-01-27 5:36 ` biopsin
2023-01-27 13:18 ` MechDR
2023-01-27 13:19 ` MechDR
2023-01-27 13:21 ` MechDR [this message]
2023-01-27 13:27 ` MechDR
2023-01-27 13:31 ` MechDR
2023-01-27 13:31 ` MechDR
2023-02-14 14:20 ` MechDR
2023-02-14 14:21 ` [ISSUE] [CLOSED] " MechDR
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=20230127132105.BEf8AqzcZs-vLkq9gcCtFJYVX-CpHDzs6YBDgGHeljQ@z \
--to=mechdr@users.noreply.github.com \
--cc=ml@inbox.vuxu.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;
as well as URLs for NNTP newsgroup(s).