From: "Kevin O'Gorman" <kogorman@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Emerge firefox 2.0.0.8 and now printing is hosed
Date: Wed, 24 Oct 2007 21:00:14 -0700 [thread overview]
Message-ID: <9acccfe50710242100s2c390bcdx975fc8426bc6f67f@mail.gmail.com> (raw)
In-Reply-To: <4ef07b8c0710242023y37071393xbd25331d71eb4f1@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1141 bytes --]
It's a gentoo ebuild, so I start here. For all I know, it was something
that happened here.
My OS is cranking along. It just spent 2 or 3 weeks recompiling itself with
GCC 4.1.2, upgrading from 3.something.
Only Qemu failed to come over. Then I promptly had to upgrade to a broken
firefox, but that's not a show-stopper for me.
++ kevin
On 10/24/07, Dan Cowsill <danthehat@gmail.com> wrote:
>
> On 10/24/07, Kevin O'Gorman <kogorman@gmail.com> wrote:
> > I've just emerged firefox 2.0.0.8 (I think it was 2.0.0.7 before), and
> now
> > attempts to print a web page bring me to a skimpy little dialog with
> just
> > two buttons: Cancel and OK. The OK button leads to an error dialog. So
> > printing is now impossible. Fortunately, I have seamonkey, which is
> working
> > just fine.
> >
> > But I'd like firefox to work too.
> >
> > ++ kevin
> >
> > --
> > Kevin O'Gorman, PhD
> >
>
> Might want to bring this up with the firefox people, not the Gentoo
> people.
>
> But hey! How's your os workin these days?
>
> --
> Dan Cowsill
> http://www.danthehat.net
> --
> gentoo-user@gentoo.org mailing list
>
>
--
Kevin O'Gorman, PhD
[-- Attachment #2: Type: text/html, Size: 1792 bytes --]
next prev parent reply other threads:[~2007-10-25 4:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-25 3:05 [gentoo-user] Emerge firefox 2.0.0.8 and now printing is hosed Kevin O'Gorman
2007-10-25 3:23 ` Dan Cowsill
2007-10-25 4:00 ` Kevin O'Gorman [this message]
2007-10-25 8:19 ` Dan Farrell
2007-10-25 14:58 ` Dan Cowsill
2007-10-25 16:09 ` [gentoo-user] " »Q«
2007-10-25 20:27 ` Arttu V.
2007-10-26 2:06 ` Kevin O'Gorman
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=9acccfe50710242100s2c390bcdx975fc8426bc6f67f@mail.gmail.com \
--to=kogorman@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