Your message dated Thu, 27 Feb 2014 14:14:46 +0100
with message-id <[email protected]>
and subject line Moreinfo: closing
has caused the Debian Bug report #294428,
regarding Firefox crashes on printing with legitimate CUPS configuration
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
294428: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=294428
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: firefox
Version: 1.0+dfsg.1-5

According to "/etc/cups/printers.conf" -


        [...]
        # Each printer starts with a <Printer name> definition.  Printer names
        # can be up to 128 characters in length and are *not* case sensitive.
        #
        # One <DefaultPrinter name> entry can appear in this file; if you don't
        # define a default destination, the first printer or class becomes the
        # default.
        [...]


- & sure enough, I can print from Firefox to <DefaultPrinter name> just fine. However, when instead using <Printer name> - because there is only one printer - Firefox crashes on "Print..." & "Print Preview".

I can't find where details of the crash get logged. I did try two different machines & confirmed that with the same configuration, except for <DefaultPrinter name> in one case & <Printer name> in another, Firefox works in the former case & crash in the latter.

cupsys 1.1.23-4 is installed. The configuration is attached.

Regards,

Jack

Attachment: printers.conf
Description: Binary data


--- End Message ---
--- Begin Message ---
Hello,

I am closing these bugs. They have the needinfo tag for a while (since
2006 for some of them) and no answer on the issue. Many of
them are fixed upstream.

If you are still experiencing the issue, please reopen the bug with the
necessary information.

Sylvestre

--- End Message ---

Reply via email to