From: Marc Joliet <marcec@gmx.de>
To: Gentoo-User ML <gentoo-user@lists.gentoo.org>
Subject: Re: [gentoo-user] can't print from firefox, but CUPS says OK, also poppler
Date: Thu, 23 Apr 2009 09:28:26 +0200 [thread overview]
Message-ID: <20090423092826.19bd6691@marcec.huntemann.uni-oldenburg.de> (raw)
In-Reply-To: <yu9fxg0sld6.fsf@nyu.edu>
[-- Attachment #1: Type: text/plain, Size: 1290 bytes --]
Am Wed, 22 Apr 2009 12:29:09 -0400
schrieb Allan Gottlieb <gottlieb@nyu.edu>:
> At Wed, 22 Apr 2009 12:18:58 -0400 Allan Gottlieb <gottlieb@nyu.edu> wrote:
>
> > For some reason printing from firefox has stopped working.
> > When I ^P or file-->print and select a printer (there are two),
> > the "print" button is greyed out. With "print to file", the button is
> > live and the pdf file is successfully created
> >
> > I can print via lpr.
> >
> > If, in firefox, I goto localhost:631 (the cups home page on this machine),
> > I can print test pages to either machine.
> >
> > Is there a way I can ask firefox to tell me why the print button is
> > greyed out?
>
> Some further information.
> Evince has the same situation, "print" is greyed out.
>
> I have the newest stable poppler/evince installed and recall that
> have upgraded poppler recently. Should I be downgrading.
>
> Below is the output of eix -I poppler -o evince
>
> thanks,
> allan
>
[snip]
See bug #266678, especially comment #8. A revision bump of cups ought to be
under way.
HTH
--
Marc Joliet
--
Lt. Frank Drebin: "It's true what they say: cops and women don't mix. Like
eating a spoonful of Drāno; sure, it'll clean you out, but it'll leave you
hollow inside."
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2009-04-23 7:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-22 16:18 [gentoo-user] can't print from firefox, but CUPS says OK Allan Gottlieb
2009-04-22 16:29 ` [gentoo-user] can't print from firefox, but CUPS says OK, also poppler Allan Gottlieb
2009-04-23 7:28 ` Marc Joliet [this message]
2009-04-26 15:15 ` Allan Gottlieb
[not found] <ctNl3-1AW-1@gated-at.bofh.it>
[not found] ` <ctNEy-20b-21@gated-at.bofh.it>
2009-04-23 6:59 ` Morten Holt
2009-04-23 7:15 ` Xavier Parizet
2009-04-29 18:23 ` Allan Gottlieb
2009-04-29 20:13 ` Alejandro
[not found] <cu1es-6JY-15@gated-at.bofh.it>
[not found] ` <cu1es-6JY-17@gated-at.bofh.it>
[not found] ` <cu1es-6JY-13@gated-at.bofh.it>
[not found] ` <cu1o7-6WC-19@gated-at.bofh.it>
2009-04-23 10:24 ` Morten K. Holt
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=20090423092826.19bd6691@marcec.huntemann.uni-oldenburg.de \
--to=marcec@gmx.de \
--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