Bob Arendt wrote:
Christopher Blizzard wrote:
Clint wrote:
Thanks for the heads-up on strace. Both sites result in segmentation errors, it seems because of True Type fonts:
open("/usr/share/fonts/zh_CN/TrueType/zysong.ttf", O_RDONLY) = -1 ENOENT (No such file or directory)
--- SIGSEGV (Segmentation fault) @ 0 (0) ---
and a different font withthe google search for emacs.
I couldn't tell that there was a dependable fix at the bugzilla page, and it seems that an attempt to fix it could result in not being able to get logged in via Gnome -- and I definitely don't want to risk that!
If anyone has ideas that I could try, please post!
Please try the rpms that I posted recently for testing to see if it solves this problem. The rpms that you want are all the Mozilla rpms listed here:
http://download.fedora.redhat.com/pub/fedora/linux/core/updates/testing/1/i386/
The bug that you are seeing is exactly the bug that update tries to solve.
--Chris
Chris - which RPM's are they? I had assumed that the ttfont rpm's would
be rebuilt so they would upgrade properly. Or is this an updated
Mozilla that traps the font error? If the latter, is there a message
output somewhere so the user knows that the fonts aren't all that they can
be? Or would Mozilla silently work-around the corrupted font file?
It just catches the error. No, there's no message about catching it. The fact is that the error is common enough outside of our busted packages that it needed to be fixed.
--Chris
-- ------------ Christopher Blizzard http://people.redhat.com/blizzard/ ------------
