Github messages for voidlinux
 help / color / mirror / Atom feed
From: MechDR <MechDR@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: hplip 3.22.10 broke my printer setup
Date: Thu, 26 Jan 2023 18:15:38 +0100	[thread overview]
Message-ID: <20230126171538.9A118T6xmgvpiUKzPRPrqqHWYD1FwooZiXRgsjP1NdM@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: 2605 bytes --]

New comment by MechDR on void-packages repository

https://github.com/void-linux/void-packages/issues/41695#issuecomment-1405334980

Comment:
@biopsin So, I uninstalled everything, deleted /lib/hp (it wasn't empty when I uninstalled hplip and hplip-gui) and then installed hplip again. Then I tried to install hplip-plugin, but apparently it's not in the repo... which kinda defeats the purpose of having it installed instead of having hplip pull the plugin from HP's site... if I have to repack the thing from xbps-src, what's the point, I have to manually do stuff instead of having the hplip-plugin updated automatically when hplip gets updated as well. The only scenario in which this "setup" (having hplip and hplip-gui in the default repos, but not hplip-plugin) makes sense is if I actually don't use the hplip-plugin package from xbps-src and just run hp-setup and let it download the plugin... it's easier than downloading the whole repo just to use the template to repackage the same plugin that hplip will download if it's ran again and the printer set up again.

I understand that there are legal reasons why Void can't hold the plugin in the repo, but having the plugin template... I mean... there might be a point in having the template, as a backup scenario, in case for whatever reason, hp-setup can't/won't download the plugin, but in any other case, I really don't see a point in having the hplip-plugin template/package in xbps-src.

Regardless, I cloned the repo, repackaged the hplip-plugin, installed it alongside hplip, removed and added the printer again (this time, yes, the 3.22.6 versions of the hplip filters/plugins were gone from the driver/filter list, the 3.22.10 versions were the only ones that were present), but... the printer won't print... the same thing again, it just errors out, except this time, it says that it's stopped, not idle after it errors out, and the print job just gets deleted automatically. Have no idea why it behaves a bit differently than the previous scenario. In any case, I decided to try and remove hplip-plugin, remove the printer again and add it through hp-setup, so that hplip can download the plugin directly from the site (of course, it warns you that Void is not on the list of supported distros). And this combo, worked. Ran hp-setup -i, it downloaded the plugin, made the adequate settings for the printer (printer name, location and whatnot) and it just worked, out of the box.

So, basically, the printer doesn't work with the repacked version of the plugin, but does work if hp-setup downloads and installs it from HPs site.

  parent reply	other threads:[~2023-01-26 17:15 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 [this message]
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=20230126171538.9A118T6xmgvpiUKzPRPrqqHWYD1FwooZiXRgsjP1NdM@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).