Closed Bug 260675 Opened 20 years ago Closed 19 years ago

Non-existing printer in $PRINTER together with CUPS crashes Mozilla/Firefox

Categories

(Core :: Printing: Output, defect)

Product:
Core
Component:
Printing: Output
Version:
1.0 Branch
Platform:
x86
Linux
Type:
defect
Priority:
Not set
Severity:
critical

Tracking

()

Status:
RESOLVED DUPLICATE of bug 281367

People

(Reporter: nic-mozilla, Unassigned)

References

Details

Attachments

(1 file)

strace -f output of firefox sigsegv when trying to print
167.97 KB, text/plain
Details 
User-Agent:       Mozilla/5.0 (X11; U; Linux i686; rv:1.7.3) Gecko/20040914 Firefox/0.10
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; rv:1.7.3) Gecko/20040914 Firefox/0.10

On any page selecting a print related menu option will crash Firefox PR1.

Reproducible: Always
Steps to Reproduce:
1. Start firefox
2. Select print menu option

Actual Results:  
Crash.
When running from commandline:-
./lib/firefox/run-mozilla.sh: line 159:  2822 Segmentation fault      "$prog"
${1+"$@"}

Expected Results:  
Open print dialog, print page.

Do not have this problem with 0.9.3.

Running debian unstable:
ii  xprt                    4.3.0.dfsg.1-7          X print server (XFree86 version)
ii  xprt-common             0.0.9.final.001-6       Xprint - the X11 print
system (configuration files)
ii  xprt-xprintorg          0.0.9.final.001-6       Xprint - the X11 print
system from xprint.org (binary)
ii  cupsys         1.1.20final+rc Common UNIX Printing System(tm) - server
ii  cupsys-bsd     1.1.20final+rc Common UNIX Printing System(tm) - BSD comman
ii  cupsys-client  1.1.20final+rc Common UNIX Printing System(tm) - client pro
nic@thunder:~$ xplsprinters
printer: plaser@:64
printer: xp_ps_spooldir_HOME_Xprintjobs@:64
printer: xp_pdf_spooldir_HOME_Xprintjobs@:64
nic@thunder:~$ lpstat -v
device for plaser: ipp://thunder:631/printers/plaser

Closer examination showed the /etc/cups/printer.conf was empty. Obviously
deleted during an update. Note this didn't affect kprinter based printing as
this was pointed at the network file server.

I re-configured the printer though http://localhost:631, and printing from
firefox began to work again.  

There is still the question though, of why 0.9.3 with the same system doesn't
crash when accessing printing.
Version: unspecified → 1.0 Branch
I think I have this bug too. Firefox 1.0PR on Linux. Not sure how to find my
Talkback IDs from all the crashes.
I uninstalled cups, and now when I press Ctrl-P I get a print dialog instead of
a crash. Cups wasn't working properly on my machine anyway.
Interesting. I'm checking all the return codes from CUPS in the code...
Here's the code if anyone can see anything I am doing wrong...
I'm getting this crash too. The unusual thing is it only seems to happen with
certain users. I've dug for differences in environment and disk space and such,
but have found nothing.

Here is a GDB trace of one of the crashes:

(gdb) where
#0  0x00e0a7a2 in _dl_sysinfo_int80 () from /lib/ld-linux.so.2
#1  0x00a5e1a5 in raise () from /lib/tls/libpthread.so.0
#2  0x087812ea in nsPRUint32Key::Clone ()
#3  <signal handler called>
#4  0x081d796d in nsReadingIterator<unsigned short>::advance ()
#5  0x081d8216 in nsReadingIterator<unsigned short>::advance ()
#6  0x081d62c4 in nsReadingIterator<unsigned short>::advance ()
#7  0x08776dd1 in nsPRUint32Key::Clone ()
#8  0x0077b217 in XPTC_InvokeByIndex ()
   from /depot/mozilla-1.x/firefox-1RC/libxpcom.so
#9  0x08091f2f in ?? ()
#10 0x09cb89bc in ?? ()
#11 0x00000005 in ?? ()
#12 0x00000001 in ?? ()
#13 0xfee76f38 in ?? ()
#14 0x0965c3a0 in ?? ()
#15 0x09c4546c in ?? ()
#16 0xfee76e20 in ?? ()
#17 0x11f32071 in ?? ()
#18 0x00000005 in ?? ()
#19 0x00000000 in ?? ()
I just submitted a Talkback on this bug, but it didn't give me a talkback ID. I
reference this bug in the talkback, so hopefully someone will find it.

Is there a way to get the talkback ID from the Linux Quality Feedback Agent?


Okay, I've done some more research and have more information now.

If your PRINTER environment variable is blank or set to the name of a printer
that doesn't exist in /etc/cups/printers.conf, Firefox crashes when you do File
| print or preview or setup.

(In reply to comment #8)
Great detective work: $PRINTER not in /etc/cups/printers.conf. 

I don't have time right now to test it right now, but I can confirm that it
would have been the case when I was getting the crashes, and it is no longer the
case now that printing doers not crash.

More information: If a default printer is set in /etc/cups/printers.conf,
Firefox won't crash when $PRINTER is not set; instead it will use that printer
as default. So setting a default printer in CUPS FIXES the problem of crashing
when $PRINTER is not set.

However, setting a $PRINTER that does not exist in /etc/cups/printers.conf still
crashes Firefox. This can happen in many cases, so it should be fixed. I have a
feeling CUPS is sending Firefox data that it cannot parse when $PRINTER is set
to a non-existant printer.

Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5) Gecko/20041109 Firefox/1.0

This bug also happens for me.  Firefox 1.0, compiled myself on a redhat 7.3 based
system using gcc 3.3.2.

cups is not installed.  When the SIGSEGV occurs is dependant on the environment.
 When I have either the PRINTER or MOZ_PRINTER_NAME environment variables set, a
print preview causes the crash.  without those set the preview works but hitting
print on the printer dialog causes a crash.  I'll attach some straces.
note that I do not have cups installed (as seen in the strace)
This happens with the supplied Solaris-SPARC-2.8 1.0build also.  I was tracking
down why it would crash for some users and not others.  Finally figured out that
those with invalid CUPS printer names as their LPDEST environment variable saw
the crash.

(When we converted to CUPS we set up a frontend to lp[r] that converts old
printer names to new names.  So previously, this wasn't a problem. I have now
made sure that all users' LPDEST variables are set to valid CUPS printer names.)

For more details on CUPS under Solaris 8, see http://TokyoJim.com/cups.html

Solaris 10 will have CUPS built in.
*** Bug 271260 has been marked as a duplicate of this bug. ***
*** Bug 273627 has been marked as a duplicate of this bug. ***
*** Bug 268660 has been marked as a duplicate of this bug. ***
*** Bug 279680 has been marked as a duplicate of this bug. ***
*** Bug 297246 has been marked as a duplicate of this bug. ***
Assignee: firefox → printing
Status: UNCONFIRMED → NEW
Component: General → Printing
Ever confirmed: true
Product: Firefox → Core
QA Contact: general
Summary: File | Print, Page Setup or Preview crashs Firefox PR1 on any page. → Non-existing printer in $PRINTER together with CUPS crashes Mozilla/Firefox
This is probably bug 281367. That bug was fixed in mozilla 1.7.6 and firefox
1.0.1. This report and all of the dupes involve earlier versions.

*** This bug has been marked as a duplicate of 281367 ***
Status: NEW → RESOLVED
Closed: 19 years ago
Resolution: --- → DUPLICATE
I am running firefox 1.0.2 and still see frequent crashes when i attempt to print.
Gregory, the symptoms you describe in comment 11 have significant differences
from the ones described by the reporter of this bug. The strace output you
attached shows the CUPS library being loaded shortly before the crash, so it's
likely that bug 281367 was causing some of your crashes. However, crashing after
dismissing the print dialog would be a separate issue.

You should retest with a current version of firefox--preferably 1.1 alpha,
because I'm not sure the 1.0 branch is still accepting non-security changes--and
open a new bug describing the behavior that you're currently seeing.
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: