129087 - Font name can't be converted

Status: RESOLVED INVALID

(Core :: Internationalization, defect)

Description

[Joe Ogulin]

Over the last several days, when mozilla has crashed, I've received the
following error message:

Warning: Missing charsets in String to FontSet conversion
Warning: Cannot convert string
"-bitstream-swiss*742-medium-r-normal--19-140-85-85-p-*" to type FontSet

I don't know if I'm just missing a particular font or if that's not proper
format or if there's a crazy part to that string that wasn't expected.

Comment 1

[Boris Zbarsky [:bzbarsky]]

Font stuff is intl

Comment 2

[Roy Yokoyama]

shanjian and bstell may be able to tell more about the linux font status.

Comment 3

[kill this account]

kiltedknight: Can you reproduce this?

If you can then perhaps we can collect a bit of data.

If you can reproduce this would you set the environment variable NS_FONT_DEBUG
to FFF and redirect moz's output to a file?

Since this will generate a large amount of data you might want to truncate
(not delete) the file periodically (eg: 'echo "" > file') to keep it
from growing too large.

Comment 4

[Joe Ogulin]

A copy of the file has been sent to shanjian and bstell.

Comment 5

[Joe Ogulin]

Attachment: debug data from NS_FONT_DEBUG=FFF

And now it's posted here too... didn't see this option before I sent it out.

Comment 6

[kill this account]

In attachment 73247 [details] I don't see that font being loaded by the font code.

Could it be loaded from another part of the code?

Joe: Could you put printf's around (both before and after) all the load font 
calls? It would be good to display the result of the call.
http://lxr.mozilla.org/seamonkey/search?string=gdk_font_load

Comment 7

[Andrew Schultz]

Joe: does this occur any any URL in particular?  if so, which one?

Comment 8

[Joe Ogulin]

It occurs at no URL in particular.

I've been using the talk-back build of 0.9.8 (build 2002020415), so it's been
sending stuff in that way too.  Don't know if that will help either.

Comment 9

[Andrew Schultz]

if you run mozilla/components/talkback/talkback, it will give you a list of the
talkback reports you have sent in.  If you report the talkback IDs here, they
can pull up the reports and figure out where it's crashing, although it probably
won't show why you get the warning about the FontSet conversion.

Comment 10

[Joe Ogulin]

OK... for some reason, I don't have any incidents listed as being captured after
2/6/02...

But the latest capture ID is TB2567457K (2/6/02), and the one before that is
TB2542355Z (2/5/02).

Comment 11

[Joe Ogulin]

Aha!  I found them... disregard the last message....

The most recent capture (for which you have the file) has an ID of TB3805466M
(3/8/02).

I went into the wrong mozilla install location to get the previous ones.

Comment 12

[Shanjian Li]

TB3805466M seesm suggesting the crash is caused by something X font system. I 
need to reproduce the problem and see what's happening. Set TM to future for now 
before I have better understand of the problem. 

Comment 13

[Frank Tang]

shanjian is no longer working on mozilla for 2 years and these bugs are still
here. Mark them won't fix. If you want to reopen it, find a good owner first. 

Comment 14

[Travis Chase]

Mass Reassign Please excuse the spam

Comment 15

[Travis Chase]

Mass Re-opening Bugs Frank Tang Closed on Wensday March 02 for no reason, all
the spam is his fault feel free to tar and feather him

Comment 16

[Travis Chase]

Reassigning Franks old bugs to Jungshik Shin for triage - Sorry for spam