Bug#1085142: Bug#1084021: Produces PPD files with invalid hash character in size names.
- To: 1085142@bugs.debian.org
- Subject: Bug#1085142: Bug#1084021: Produces PPD files with invalid hash character in size names.
- From: Agustin Martin <agmartin@debian.org>
- Date: Tue, 28 Jan 2025 23:30:18 +0100
- Message-id: <[🔎] Z5laeqFVDMntzVFF@lenovo-sid.aq.upm.es>
- Reply-to: Agustin Martin <agmartin@debian.org>, 1085142@bugs.debian.org
- In-reply-to: <CAFsGsxJS+afsfGWBnA5G62BCECFEjE1PyYMRfr_ng4-w8jgOKA@mail.gmail.com>
- References: <172803610883.1400167.16876595635738964743.reportbug@butla> <1d0112fc-fc7b-4df3-9b04-a871bc5e0f66@alteholz.de> <CAFsGsxKtBNEApZisBp0vAR=2-=zHyN_gnjwrU5TfRL3yHJT1UA@mail.gmail.com> <b97755ec-6630-4768-9972-3f2a68f16805@alteholz.de> <CAFsGsxK1PA+4tThzjpOoq9Wa+SX01xns5m9vmoPYBeGQHL1FGA@mail.gmail.com> <CAFsGsxLa7XqbA5nUB8VyBTkEmcbL91OBqNSWdwc3NSLtC1K=KQ@mail.gmail.com> <CAFsGsxLKEmVvEAUHP4KdbdPC_W_U_QvSBq0sK3EaUZcPYojyyw@mail.gmail.com> <172803610883.1400167.16876595635738964743.reportbug@butla> <CAFsGsxJS+afsfGWBnA5G62BCECFEjE1PyYMRfr_ng4-w8jgOKA@mail.gmail.com> <172803610883.1400167.16876595635738964743.reportbug@butla>
[resending to hplip 1085142, where it was supposed to go, instead of cups]
On Tue, Oct 15, 2024 at 01:46:55PM +0200, Marcin Owsiany wrote:
> I reported this issue upstream to
> https://github.com/OpenPrinting/cups/issues/1078 and it turned out that the
> root cause was some invalid names in the ppd file.
> It had an invalid character in some of the size names - the '#' in
> "Envelope#10", "JapaneseEnvelope#3.FB" and "JapaneseEnvelope#4.FB".
>
> I think it's still wrong for cups to respond with a syntactically invalid
> response to get-printer-attributes in this case, so I'm keeping this bug
> open for now.
> I'll clone it into another bug against hpcups which I think is responsible
> for the PPD file.
Hi,
cups 2.4.11 (not yet packaged for Debian) is said in above
issues/1078 to have a workaround for this.
Regarding hplip, I looked at 3.24.4 upstream release (not yet
packaged for Debian) and seems it still has the same problem.
Looking at https://github.com/OpenPrinting/cups/issues/1078 I wonder if
attached sed script acting on ppd files under ppd dir does fix this issue (I
am a complete newbie to this and I do not have access to affected printer
nor know at all about ppd format).
Another thing, has this been reported to hplip upstream?
Regards,
--
Agustin
s/JapaneseEnvelope\#3\.FB/EnvChou3\.Fullbleed/g
s/JapaneseEnvelope\#3/EnvChou3/g
#
s/JapaneseEnvelope\#4\.FB/EnvChou4\.Fullbleed/g
s/JapaneseEnvelope\#4/EnvChou4/g
#
s/Envelope\#10\.FB/Env10\.Fullbleed/g
s/Envelope\#10/Env10/g
Reply to: