From: Philip Webb <purslow@ca.inter.net>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] printing problems : hiccups solve them
Date: Thu, 5 Nov 2015 01:21:16 -0500 [thread overview]
Message-ID: <20151105062116.GA1711@ca.inter.net> (raw)
In-Reply-To: <20151103183358.GA1383@ca.inter.net>
151103 Philip Webb wrote:
> The basic problem is now clear : this printer won't print draft quality,
> but leaves blank bands across the output (no, it's not an old cartridge).
> Therefore, something has to tell it to print 'high-quality' or 'best'.
>
> In Mint, when that is set via the 631 menu, printing works correctly :
> I can print text files via Gvim (icon or :ha ) & Gedit, .odt via LO
> & PDF via Evince ; Gedit & Evince have their own quality settings.
>
> In Gentoo, the 631 setting has no effect, so all printing is draft.
> Only Kwrite has its own quality setting, which does work properly for text.
I've found the source of the problem.
It's necessary to choose the 'hpcups' driver, not the 'hpijs' driver,
when setting up the printer via the 631 menu.
Once that's done, Gvim Okular LO all print 'best' quality correctly.
There is also a quality setting hidden away in the LO menus :
tools -> options -> LO -> print : set 'high' = 300 dpi.
My route to the solution was via trying the 'gutenprint' pkg.
It doesn't offer a driver for an HP DJ 2510 , only 2500 or 2540,
but that led me to look thro' the other drivers in the 631 menu
& one of them was 'hpcups'.
I'm surprised -- well, am I really ? -- that there's no mention of all this
in any of the dox, wikis, Forum discussions etc etc I've scoured.
However as usual, all problems with Gentoo are 1 level deep :
find where it is & the solution falls into place promptly (smile).
--
========================,,============================================
SUPPORT ___________//___, Philip Webb
ELECTRIC /] [] [] [] [] []| Cities Centre, University of Toronto
TRANSIT `-O----------O---' purslowatchassdotutorontodotca
next prev parent reply other threads:[~2015-11-05 6:21 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-02 0:08 [gentoo-user] printing problems Philip Webb
2015-11-02 2:46 ` Daniel Frey
2015-11-02 6:52 ` Mick
2015-11-03 0:46 ` Philip Webb
2015-11-03 1:01 ` Daniel Frey
2015-11-03 18:33 ` Philip Webb
2015-11-03 22:49 ` Mick
2015-11-03 23:20 ` Philip Webb
2015-11-04 2:19 ` Philip Webb
2015-11-04 4:42 ` Dale
2015-11-05 3:34 ` [gentoo-user] printing problems : one solved Philip Webb
2015-11-05 6:21 ` Philip Webb [this message]
2015-11-05 6:38 ` [gentoo-user] printing problems : hiccups solve them Mick
2015-11-10 23:12 ` [gentoo-user] printing problems Frank Steinmetzger
2015-11-11 16:20 ` Daniel Frey
2015-11-11 20:36 ` Marc Joliet
2015-11-03 16:05 ` Dale
2015-11-03 19:56 ` Alan McKinnon
2015-11-04 4:38 ` Dale
2015-11-04 6:30 ` J. Roeleveld
2015-11-04 8:19 ` Dale
2015-11-04 8:44 ` J. Roeleveld
2015-11-04 9:55 ` Dale
2015-11-04 12:31 ` Peter Humphrey
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=20151105062116.GA1711@ca.inter.net \
--to=purslow@ca.inter.net \
--cc=gentoo-user@lists.gentoo.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