void-linux / void-linux/void-packages

escputil

Open
#52,354 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug needs-testing
Dominant language
Shell
Stars
3.4k
Forks
2.8k
Avg merge
2d 5h
Merged PRs (30d)
299

Description

Is this a new report?

Yes

System Info

Void Linux x86_64

Package(s) Affected

Gutenprint 5.3.4, epson-inkjet-printer-escpr-1.8.1_1

Does a report exist for this bug with the project's home (upstream) and/or another distro?

$ uname -r
6.6.52_1

Expected behaviour

clean epson print head on void linux

Actual behaviour

clean epson print head on linux

Steps to reproduce

$ escputil -n --raw-device /dev/usb/lp0

ERROR: ***Gutenprint 5.3.4 assertion list != NULL failed! file print-list.c, line 212. Please report this bug!
Abortado

$ escputil -n /dev/usb/lp0

ERROR: ***Gutenprint 5.3.4 assertion list != NULL failed! file print-list.c, line 212. Please report this bug!
Abortado

$ ldd which escputil
linux-vdso.so.1 (0x00007ffd1446d000)
libgutenprint.so.9 => /usr/lib/libgutenprint.so.9 (0x00007f87d57b4000)
libc.so.6 => /usr/lib/libc.so.6 (0x00007f87d55ca000)
libm.so.6 => /usr/lib/libm.so.6 (0x00007f87d54e8000)
libdl.so.2 => /usr/lib/libdl.so.2 (0x00007f87d54e3000)
/lib64/ld-linux-x86-64.so.2 => /usr/lib64/ld-linux-x86-64.so.2 (0x00007f87d585d000)

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the reported escputil commands against Gutenprint 5.3.4 on Void Linux, including both /dev/usb/lp0 invocation forms. Inspect the Void package configuration and the reported Gutenprint assertion in print-list.c; done means identifying a package or upstream fix that allows the Epson print-head cleaning command to run without aborting.

Written by the indexing model from the issue text.

Assessment

Tech stack
linux, shell
Domain
cli, operating-systems
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
32/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.