From: zenny <zenny@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: cups-pdf producing a single blank page after upgrade today (2021-05-01)
Date: Thu, 17 Jun 2021 18:30:07 +0200 [thread overview]
Message-ID: <20210617163007.Phnx40_nlQpVmTIovUgFmZZ0TKA7mVUoBNOLEYUmFlg@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-30615@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 859 bytes --]
New comment by zenny on void-packages repository
https://github.com/void-linux/void-packages/issues/30615#issuecomment-863370997
Comment:
> > Hi, do you know how long it's been since your last update?
>
> a week earlier.
>
> > Both ghostscript and cups were updated semi-recently (ghostscript being the most recent one). You could try downgrading either of them to test :)
>
> Ok thanks for the pointer.
@ericonr The issue is not yet resolved. :(
Both cups-pdf and cups-filters are installed. Physical printers are working alright.
Fyi, tried with the solutions provided in https://askubuntu.com/questions/601836/cups-pdf-prints-a-blank-page, didn't work either. ;-)
Just wondering, does it have anything to do with this repo: https://github.com/alexivkin/CUPS-PDF-to-PDF?!
Any inputs to get out of this issue shall be appreciated.
next prev parent reply other threads:[~2021-06-17 16:30 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-01 17:06 [ISSUE] " zenny
2021-05-01 21:58 ` ericonr
2021-05-03 10:55 ` zenny
2021-06-17 16:09 ` zenny
2021-06-17 16:23 ` zenny
2021-06-17 16:24 ` zenny
2021-06-17 16:30 ` zenny [this message]
2021-06-17 16:31 ` zenny
2021-06-17 16:45 ` zenny
2021-06-17 16:49 ` zenny
2021-06-18 10:57 ` zenny
2021-06-18 11:11 ` zenny
2021-06-18 11:31 ` zenny
2021-06-18 12:00 ` zenny
2021-06-18 12:18 ` zenny
2021-06-22 17:30 ` Piraty
2021-06-22 17:44 ` zenny
2021-06-22 18:14 ` zenny
2021-07-05 13:07 ` Piraty
2021-07-06 14:34 ` zenny
2021-07-07 9:25 ` [ISSUE] [CLOSED] " Piraty
2021-07-07 9:25 ` Piraty
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=20210617163007.Phnx40_nlQpVmTIovUgFmZZ0TKA7mVUoBNOLEYUmFlg@z \
--to=zenny@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).