Bug 140904 - mozilla and mozilla-based browsers crash when attempting to print if env PRINTER is set to non-existing printer
Summary: mozilla and mozilla-based browsers crash when attempting to print if env PRIN...
Alias: None
Product: Fedora
Classification: Fedora
Component: mozilla (Show other bugs)
(Show other bugs)
Version: 3
Hardware: All Linux
Target Milestone: ---
Assignee: Christopher Aillon
QA Contact: Ben Levenson
Depends On:
TreeView+ depends on / blocked
Reported: 2004-11-26 09:14 UTC by Piero Serini
Modified: 2008-08-02 23:40 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-10-31 16:13:56 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Piero Serini 2004-11-26 09:14:10 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.3)
Gecko/20041020 Galeon/1.3.18

Description of problem:
mozilla and mozilla-based browsers (firefox, galeon, etc.) crash
(die of SIGSEGV) when attempting to print (selecting File->Print)
if environment variable 'PRINTER' is set to non-existing printer.

strace and ltrace show the SIGSEGV occurs in a strncasecmp.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. export PRINTER=foobar # assuming no printer named 'foobar' exists
2. launch mozilla/firefox/galeon
3. Select File -> Print


Actual Results:  SIGSEGV

Expected Results:  popup of printing menu

Additional info:

workaround: unset PRINTER, or set it to a correct PRINTER.

Nonetheless, there may be a good reason for having it set to
something not in /etc/printcap.

Comment 1 Matthew Miller 2006-07-10 20:45:12 UTC
Fedora Core 3 is now maintained by the Fedora Legacy project for security
updates only. If this problem is a security issue, please reopen and
reassign to the Fedora Legacy product. If it is not a security issue and
hasn't been resolved in the current FC5 updates or in the FC6 test
release, reopen and change the version to match.

Thank you!

Comment 2 John Thacker 2006-10-31 16:13:56 UTC
Works fine in RHEL4 and FC6.  Suspect that it got fixed upstream.

Note You need to log in before you can comment on or make changes to this bug.