253005 - crash when you enter a letter in the SearchPkg box

Status: RESOLVED EXPIRED

(Core Graveyard :: GFX: Gtk, defect)

Description

[Patrick Useldinger]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7) Gecko/20040626 Firefox/0.9.1
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7) Gecko/20040626 Firefox/0.9.1

Appears to be linked to Freetype2 when it is compiled with the "hinting" option.
Happens on both Mozilla 1.7 and Firefox 0.9.1.

Reproducible: Always
Steps to Reproduce:
1. Enter a letter in the SearchPkg box
2. Mozilla dies
3.

Actual Results:  
/usr/lib/mozilla-firefox/run-mozilla.sh: line 451:  1751 Segmentation fault    
 "$prog" ${1+"$@"}

Comment 1

[Boris Zbarsky [:bzbarsky]]

Linux fonts bug, not core layout bug....

Comment 2

[Christopher Blizzard (:blizzard)]

There isn't enough information in here to diagnose this bug.  Did you do a build
yourself?  If so, what build options did you use?  (about:buildconfig will
reveal this.)

Do you know how to get a stack trace?

My first guess is that based on the css on the site that you have some fonts in
your path that aren't readable by you or you have a .fon file in your path
somewhere.  This is probably a dup of one of the usual Xft upstream bugs.

Comment 3

[Patrick Useldinger]

No build, I used the Mozilla package included in Slackware 10.
It's not with a particular site, it's with all of them, and many Slackware users
experience the same, according to the forums.

No, I don't know how to get a stack trace. Can you point me to an explanation?

Comment 4

[Christopher Blizzard (:blizzard)]

It sounds like there are problems with your upstream xft/xfree86 package.  I
think that most of the other distros have picked up the fixes that keep those
crashes from happening.

Comment 5

[Gervase Markham [:gerv]]

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 6

[Gervase Markham [:gerv]]

This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.