From: Alejandro <elcorreodeale@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] can't print from firefox, but CUPS says OK, also poppler
Date: Wed, 29 Apr 2009 17:13:46 -0300 [thread overview]
Message-ID: <60a795cd0904291313s13ff7d2aj6d654fb671ba2cd3@mail.gmail.com> (raw)
In-Reply-To: <yu91vrbnwsr.fsf@nyu.edu>
[-- Attachment #1: Type: text/plain, Size: 1434 bytes --]
2009/4/29 Allan Gottlieb <gottlieb@nyu.edu>
> At Thu, 23 Apr 2009 08:59:50 +0200 Morten Holt <thawk@t-hawk.com> wrote:
>
> > Allan Gottlieb wrote:
> >> 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.
> > Sounds like the same issue I have, do you get log entries like:
> > Request from "localhost" using invalid Host: field "::1"
> > in /var/log/cups/error_log?
> >
> > If you find a solution to this, please let me know here, I can't seem to
> > find a solution to the issue, and appearantly nobody has any ideas.
>
> Sorry I didn't notice your msg earlier.
> My issue was fixed with a version bump to cups.
> Do you still have trouble with 1.3.10-r1.
>
> allan
>
>
This is because cups start using ipv6 by default. Using your previous cuos
config should fix this.
[-- Attachment #2: Type: text/html, Size: 2141 bytes --]
next prev parent reply other threads:[~2009-04-29 20:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <ctNl3-1AW-1@gated-at.bofh.it>
[not found] ` <ctNEy-20b-21@gated-at.bofh.it>
2009-04-23 6:59 ` [gentoo-user] can't print from firefox, but CUPS says OK, also poppler Morten Holt
2009-04-23 7:15 ` Xavier Parizet
2009-04-29 18:23 ` Allan Gottlieb
2009-04-29 20:13 ` Alejandro [this message]
[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
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
2009-04-26 15:15 ` Allan Gottlieb
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=60a795cd0904291313s13ff7d2aj6d654fb671ba2cd3@mail.gmail.com \
--to=elcorreodeale@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