Red Hat Bugzilla – Bug 966740
Firefox segfaults in nsFontMetrics::GetMetrics() on PPC64
Last modified: 2015-02-17 10:19:28 EST
Created attachment 752372 [details]
Description of problem:
Firefox segfaults at startup on ppc64:
Program received signal SIGSEGV, Segmentation fault.
0x00003fffb58152c0 in nsFontMetrics::GetMetrics (this=this@entry=0x3fffa1857420)
129 return mFontGroup->GetFontAt(0)->GetMetrics();
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Launch firefox
Segmentation fault. Backtrace attached
Hm, are you sure you have fonts installed (like X11 and dependencies).
How can I verify that?
I'm using firefox under VNC.
It looks like I needed a dependency.
I had done a minimal f19 install and then installed firefox and VNC. This used to work for me in the past, but apparently it no longer works.
Doing a full graphical install makes firefox work much better. Firefox crashed the first time I launched it, but worked fine subsequently.
Shouldn't these required fonts (or whatever other deps Firefox needs) be installed as a result of yum install firefox ? Or the minimal install + firefox and VNC is just a non-supported setup?
No, we can't depend on any font - it has to be a part of minimal usable X environment. I'm sure other X apps will crash there too.
OTOH firefox may throw some decent error message instead of the crash...but unfortunately if we fix this one it may crash in cairo as well.
We should consider to give a hint to user, for instance from firefox sh launch script or so. BTW. which font files have you installed?
This message is a notice that Fedora 19 is now at end of life. Fedora
has stopped maintaining and issuing updates for Fedora 19. It is
Fedora's policy to close all bug reports from releases that are no
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.
Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 19 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
Thank you for reporting this bug and we are sorry it could not be fixed.