From: Mick <michaelkintzios@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] printing problems
Date: Tue, 3 Nov 2015 22:49:28 +0000 [thread overview]
Message-ID: <201511032249.50716.michaelkintzios@gmail.com> (raw)
In-Reply-To: <20151103183358.GA1383@ca.inter.net>
[-- Attachment #1: Type: Text/Plain, Size: 1917 bytes --]
On Tuesday 03 Nov 2015 18:33:58 Philip Webb wrote:
> 151102 Daniel Frey wrote:
> > I had so many problems with hplip I stopped using it. I found another
> > way to use my hp CP1025nw with foomatic and that works trouble-free.
> > It's a driver for Laserjet printers, it won't work on deskjets AFAIK.
> > The driver is foo2zjs: http://foo2zjs.rkkda.com/ , wh uses Ghostscript.
> > I looked and it looks like that won't help you.
>
> Yes, they all seem to be for laser printers. I do very little printing,
> but once or twice a year need to print something,
> so my cheap little HP DJ 2510 is adequate.
>
> 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.
> In addition, the icon doesn't work in Gvim, tho' :ha does.
>
> So for everyday purposes, I can print anything by rebooting into Mint.
> However, I'm not happy that there's a bug (or more) of some sort in Gentoo.
> I'm not at all sure where it could be or how to report it.
> It cb caused by the difference in desktops, Xfce on Mint, Fluxbox on Gentoo
> : perhaps the bigger desktop managers do the job themselves,
> whereas something else needs fixing with the lightweight Fluxbox.
>
> Further comments mb useful to everyone.
>
> PS thankyou to Dale, whose general experience is similar to my own.
Is your gentoo user a member of lp & lpadmin group?
--
Regards,
Mick
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2015-11-03 22:49 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 [this message]
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 ` [gentoo-user] printing problems : hiccups solve them Philip Webb
2015-11-05 6:38 ` 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=201511032249.50716.michaelkintzios@gmail.com \
--to=michaelkintzios@gmail.com \
--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