From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 12661] New: cups problems in buildroot
Date: Wed, 18 Mar 2020 15:16:43 +0000 [thread overview]
Message-ID: <bug-12661-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=12661
Bug ID: 12661
Summary: cups problems in buildroot
Product: buildroot
Version: 2019.11.2
Hardware: PC
OS: Linux
Status: NEW
Severity: normal
Priority: P5
Component: Other
Assignee: unassigned at buildroot.uclibc.org
Reporter: skif at skif-web.ru
CC: buildroot at uclibc.org
Target Milestone: ---
Created attachment 8401
--> https://bugs.busybox.net/attachment.cgi?id=8401&action=edit
configs and logs
If printing test-page (from cups web-interface), got error "Exception: open no:
No such file or directory" in web-interface
If printing text-file (fstab for example, lp /etc/fstab), got error "Exception:
open no: No such file or directory" in web-interface.
If printing binary file, (head -n 1 /bin/cp >/1;lp -d test /1) all works fine
Used printer - hp laserJet pro m402dn
Used driver - generic post-script (work fine fron linux-mint and gentoo)
Used defaconfig - qemu_x86_84_defconfig
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2020-03-18 15:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-18 15:16 bugzilla at busybox.net [this message]
2020-03-18 19:30 ` [Buildroot] [Bug 12661] cups problems in buildroot bugzilla at busybox.net
2020-03-18 19:43 ` bugzilla at busybox.net
2020-04-23 6:43 ` bugzilla at busybox.net
2020-05-18 5:25 ` bugzilla at busybox.net
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=bug-12661-163@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--cc=buildroot@busybox.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.