From: MechDR <MechDR@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: hplip 3.22.10 broke my printer setup
Date: Mon, 23 Jan 2023 17:13:20 +0100 [thread overview]
Message-ID: <20230123161320.N3O5XRW0Uo6hWLADKSsJcDs-knA01N_GYgI4mgiKJgE@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: 1157 bytes --]
New comment by MechDR on void-packages repository
https://github.com/void-linux/void-packages/issues/41695#issuecomment-1400609838
Comment:
@dataCobra
> Could you check if the printer does show up in cups and hplip setup when you update the packages?
It does show up as a printer in the printer manager, thus in CUPS and HPLIP as well. The printer is not removed, just errors out when you try and print to it.
> If so, could you please try to print a testpage directly from cups and one directly from hplip?
That doesn't work as well, nothing works. The printer is there, it's listed as present and connected, but doesn't print anything sent to it.
> It would also be helpful to see the error messages that you get while trying things out that did work before.
Will try that later on in the day, I'm kinda busy now. Will have to unhold the hplip package, but will make a snapshot before that, so that I can restore the working version after that.
@biopsin
> can you test print from terminal?
I haven't tried that, don't even know the commands, will look them up, will try when I do the other tests after I unhold the package.
next prev parent reply other threads:[~2023-01-23 16:13 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 [this message]
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
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=20230123161320.N3O5XRW0Uo6hWLADKSsJcDs-knA01N_GYgI4mgiKJgE@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).