Closed Bug 218691 Opened 21 years ago Closed 21 years ago

font permission errors crash browser without any info printed to stderr

Categories

(SeaMonkey :: General, defect)

x86
Linux
defect
Not set
critical

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 183729

People

(Reporter: boatswain6, Unassigned)

Details

(Keywords: crash)

User-Agent:       Mozilla/5.0 (compatible; Konqueror/3.1; Linux)
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.5a) Gecko/20030904 Mozilla Firebird/0.6.1

If truetype fonts that MozillaFirebird expects to use are not readable by the user, 
the browser will pop out of existence without any info to a terminal or gui.  This 
baffled users on Gentoo forums.  Others observed this behavior in Thunderbird 
as well, but I have not confirmed this.  The bug is that there is no information that 
would indicate the problem to the user to stderr, X or otherwise. 

Reproducible: Always

Steps to Reproduce:
1.Import a font from a Windows partition or chmod a ttf font as 400 
2.Run fc-cache -f so to be sure the font is used or whatever else will accomplish 
this task. 
3.Open MozillaFirebird and surf to a site that will use said font. 
Actual Results:  
The browser closes without warning or error message.  If it was run from the 
terminal, no error message or information is printed to stderr to allow the user to 
determine the problem.  Naturally, the error does not occur if browser was run as 
root. 

Expected Results:  
If run from the terminal, it might reasonably be expected to have printed a 
message that suggested something along the lines of a difficulty finding/reading 
a font. 

This very well may affect other Mozilla apps.
setting severity: critical
adding keyword: crash

I don't think this belongs in Firebird, sending to Browser -> General for triage.
Assignee: blake → general
Severity: normal → critical
Component: General → Browser-General
Keywords: crash
Product: Firebird → Browser
QA Contact: asa → general
Version: unspecified → Trunk
boatswain6@yahoo.com: Could you reproduce it with Mozilla TalkBack enabled
nightbuild? If Mozilla will crash too, please provide TalkBack incident ID.
This also happens with mozilla/1.4 and 1.5 on fedora core 1. Just found the
bugzilla entry after I figured it out myself (testing which html tag would make
mozilla crash). Don't know how to activate the talkback.
Dup.

*** This bug has been marked as a duplicate of 183729 ***
Status: UNCONFIRMED → RESOLVED
Closed: 21 years ago
Resolution: --- → DUPLICATE
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.