Package Details: foo2zjs-nightly 20201127-1

Git Clone URL: https://aur.archlinux.org/foo2zjs-nightly.git (read-only, click to copy)
Package Base: foo2zjs-nightly
Description: foo2zjs Printer Drivers (automatically updated). Includes also foo2hp, foo2hbpl, foo2oak, foo2xqx, foo2qpdl, foo2slx, foo2hiperc and foo2lava drivers.
Upstream URL: http://foo2zjs.linkevich.net/
Licenses: GPL, custom
Conflicts: foo2zjs
Provides: foo2zjs
Replaces: foo2zjs
Submitter: intelfx
Maintainer: fermino
Last Packager: fermino
Votes: 53
Popularity: 0.38
First Submitted: 2016-11-12 03:35 (UTC)
Last Updated: 2024-11-14 18:38 (UTC)

Dependencies (8)

Required by (0)

Sources (37)

Pinned Comments

Latest Comments

« First ‹ Previous 1 .. 6 7 8 9 10 11 12 13 14 15 16 .. 20 Next › Last »

ron2138 commented on 2018-06-10 11:01 (UTC) (edited on 2018-06-10 14:15 (UTC) by ron2138)

@bitsfritz (commented on 2018-06-09 21:19): I confirm. I get this too. A workaround for those having only one printer is to replace line 40 of /usr/bin/foo2zjs-loadfw, currently

MODEL="$FOO2ZJS_FW_MODEL"

with

MODEL=(replace this parenthesis with the model as /usr/lib/udev/rules/71-hplj10xx.rules records it in ENV{FOO2ZJS_FW_MODEL}.)

Can some one explain, real slow, why the systemd unit is required in the first place? Why not use a udev RUN command? In addition, I don't understand how this setup is supposed to deal with the case that one repeatedly turns his printer on and off while the PC is running. As far as I can tell, it won't run again the systemd unit, which makes the printer uninitialized.

bitsfritz commented on 2018-06-09 21:19 (UTC) (edited on 2018-06-09 21:46 (UTC) by bitsfritz)

again cannot connect my Laserjet 1000

... Jun 09 22:21:22 dumbledore systemd[1]: Starting Load HP ZJS/XQX printer firmware for /sys/devices/pci0000:00/0000:00:1a.7/usb1/1-5/1-5.4/1-5.4.4... Jun 09 22:21:22 dumbledore udev-configure-printer[1114]: add usb-001-009 Jun 09 22:21:22 dumbledore foo2zjs-loadfw[1115]: Downloading firmware for printer model '' serial '' at devpath '/devices/pci0000:00/0000:00:1a.7/usb1/1-5/1-5.4/1-5.4.4' Jun 09 22:21:22 dumbledore foo2zjs-loadfw[1115]: Model number is empty (borked udev configuration?) ...

is this a regression from "bitsfritz commented on 2016-11-01 15:14" ?

severach commented on 2018-06-09 00:30 (UTC)

Nuke the offending lines with a hook.

ron2138 commented on 2018-06-08 23:25 (UTC) (edited on 2018-06-08 23:40 (UTC) by ron2138)

@intelfx: As for my comment on 2018-06-01 03:29 regarding udev rules conflicts, I think you misunderstood me. As far as I understand, it is hplip rules that interfere with zjs supported printers. I think zjs rules are fine, hplip rules should be improved. I believe the problem is very old, though I haven't tried to determine when it was started. It could be that few people need both hplip and foo2zjs concurently. More detalis are at https://wiki.archlinux.org/index.php/CUPS/Printer-specific_problems#foo2zjs_Driver.

intelfx commented on 2018-06-02 23:11 (UTC) (edited on 2018-06-03 09:46 (UTC) by intelfx)

@dalu: Reproduced your issue. It's a race in author-provided Makefile. Fixed that.

@frealgagu, @badbytes, @markscamilleri, @codibit: Checksums fixed, patches rebased, package updated.

NB: The first checksum is intended to be SKIP — this is a "nightly" package that tracks the latest source.

@ron2138: Actually, I do not use this driver anymore. If there are any udev rule conflicts now, please tell me exactly which.

ron2138 commented on 2018-06-01 03:29 (UTC)

You might want to be aware of https://bugs.archlinux.org/task/58815. The upstream report mentions https://bbs.archlinux.org/viewtopic.php?id=218509, so foo2zjs is the victim.

codibit commented on 2018-05-31 06:24 (UTC) (edited on 2018-05-31 06:52 (UTC) by codibit)

Patch 0004-Makefile-fix-generating-.ppd-in-place.patch is being rejected because upstream package has now commented out the affected lines in the Makefile (among other things, I guess, I can't compare to 20180508 because I can't get a copy of the older source package).

The reported sha256 checksum df60985d6bc06fdea029e62d200f9f20b4026a8b4e11d39144636c75dc8b3d5b matches the files with the current official sha1sum of 7e8b3dd43afde815d83baeb0a8165c81fac71f06.

New version was released Sat May 19 14:04:21 2018 CDT.