public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Luis Gustavo Vilela de Oliveira <luisgustavo.vilela@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: chromium print bug?
Date: Mon, 12 Nov 2012 17:27:42 -0200	[thread overview]
Message-ID: <CAJk4mGLr_bjzD6R2N+Cb2y4of3OfBsyrJgZnq5NDs_Mu+Q2Log@mail.gmail.com> (raw)
In-Reply-To: <CAN0CFw0yVSunzjjZeB9dBeD315_sF5dL9Q4obDUt+nc2DxrY5A@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 848 bytes --]

My cups was down when a tested. The problem is exactly what *walt* points
before.


2012/11/12 Grant <emailgrant@gmail.com>

> >> Does anyone else's chromium get a little crazy when they try to bring
> >> up the print dialog without a printer attached?
> >
> >
> > Thanks for the workaround :)  Whenever I try to print to a file from
> chromium, the browser freezes and I need to kill the process to continue.
> >
> > I normally don't start cupsd unless I intend to print to my printer, but
> I tried starting cupsd just now and powering on my printer and that fixed
> the problem with printing to a file.
> >
> > This seems to be a bug in chromium.  Anyone have any experience with
> filing chromium bugs upstream?  Does it ever really get things fixed?  (I
> gave up on firefox bugs long ago.)
>
> Thanks guys, I'll submit the bug.
>
> - Grant
>

[-- Attachment #2: Type: text/html, Size: 1330 bytes --]

  reply	other threads:[~2012-11-12 19:29 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-11 19:49 [gentoo-user] chromium print bug? Grant
2012-11-11 22:21 ` Luis Gustavo Vilela de Oliveira
2012-11-12  1:13 ` [gentoo-user] " walt
2012-11-12 19:08   ` Grant
2012-11-12 19:27     ` Luis Gustavo Vilela de Oliveira [this message]
2012-11-12 19:43       ` Grant
2012-11-15  3:49         ` Mike Gilbert
2012-11-13 15:43   ` Carlos Sura

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=CAJk4mGLr_bjzD6R2N+Cb2y4of3OfBsyrJgZnq5NDs_Mu+Q2Log@mail.gmail.com \
    --to=luisgustavo.vilela@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