Closed
Bug 184405
Opened 23 years ago
Closed 23 years ago
Browser crashes on startup if font file isn't world readable
Categories
(Core Graveyard :: GFX: Gtk, defect)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 183729
People
(Reporter: bdaniel, Assigned: asa)
References
Details
(Keywords: crash, stackwanted)
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20021130
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20021130
The browser crashed with a signal 11. Running with strace, I saw the following
relevant lines:
open("/usr/share/fonts/ttf/winnt/times.ttf", O_RDONLY) = -1 EACCES (Permission
denied)
--- SIGSEGV (Segmentation fault) ---
unlink("/home/bdaniel/.mozilla/default/ly1r37hr.slt/lock") = 0
_exit(11) = ?
After I changed the permissions of the font files to world readable, everything
worked correctly.
Reproducible: Always
Steps to Reproduce:
1. Make sure the appropriate font file is readable only by root
2. Start mozilla
Actual Results:
To the user's perspective, nothing happened at all. On the command line, I saw
that mozilla returned 11.
Expected Results:
Mozilla should have started up
I'm using Mandrake 8.2 with Ximian desktop.
The workaround is simple, if you know what the problem is. It's not immediately
obvious though
Comment 1•23 years ago
|
||
Thanks for the very detailed bug report.
Can you generate a stack trace using GDB to see where it crashes ?
Severity: normal → critical
Keywords: crash,
stackwanted
Comment 2•23 years ago
|
||
can you download a Talkback-enabled build and report Talkback ID
"mozilla/bin/components/talkback/talkback" ?
I cannot reproduce the crash using Mozilla 20021207 (CVS) on Linux with all .ttf
font files being -rw------- and owned by root, Mozilla started from a standard user.
Do you have a XFT build or specific prefs for fonts in your prefs.js (and user.js) ?
| Reporter | ||
Comment 3•23 years ago
|
||
I downloaded a talkback-enabled build, and the problem did not occur. I ran that
with strace as well, and it looks like it didn't try to open the affected font
file. My original build still crashes if it's not world readable.
My installation is from the Mandrake 8.2 cooker Mozilla 1.2.1 RPM. I didn't see
any references to any ttf files in my prefs.js, and I don't see a user.js on my
system.
Comment 4•23 years ago
|
||
Verified. had this problem too, and yes, it's when using an XFT-enabled build
(Gentoo's in my case). As root, mozilla starts just as always, users don't even
see an error message.
Comment 5•23 years ago
|
||
Is this only with an Xft build? I need to track this if it is Xft-only.
Comment 6•23 years ago
|
||
On gentoo, if you build mozilla with gtk2, XFT gets disabled. This build ran.
I rebuilt with gtk1 and xft2, and the behaviour mentioned above arised.
So methinks, as gtk1 or 2 shouldn't make a difference in this case, that it is
indeed an XFT problem.
If you cannot reproduce, I could build different mozillas here and further
narrow the testcase, but I need about 5 hours here to build this beast... I can
send you a gdb stacktrace, too, if you point me to a simple guide on how to do
it properly.
Updated•23 years ago
|
Blocks: xft_tracking
Updated•23 years ago
|
Flags: blocking1.3b+
Updated•23 years ago
|
Flags: blocking1.3b+
Comment 7•23 years ago
|
||
http://www.mozilla.org/unix/debugging-faq.html
if you're using the standard mozilla startup script, just do
% mozilla -g -d gdb
(gdb) run
[wait for mozilla to crash]
(gdb) bt
(attach the output from "bt" here)
Comment 8•23 years ago
|
||
Status: UNCONFIRMED → ASSIGNED
Component: Browser-General → GFX: Gtk
Ever confirmed: true
Comment 9•23 years ago
|
||
Marking as a dup since the other bug has better debugging information.
*** This bug has been marked as a duplicate of 183729 ***
Status: ASSIGNED → RESOLVED
Closed: 23 years ago
Resolution: --- → DUPLICATE
Updated•17 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•