ابحث في الدعم

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Why since updating to Firefox 34 is Crash Reporter partly in Greek?

  • 12 ردًا
  • 6 have this problem
  • 1 view
  • آخر ردّ كتبه guigs

more options

Since I updated to the latest version of Firefox on my Mac running the final version of Mavericks I am having a few crashes and each time the Crash Reporter window is displayed partly in the Greek Language

Since I updated to the latest version of Firefox on my Mac running the final version of Mavericks I am having a few crashes and each time the Crash Reporter window is displayed partly in the Greek Language

All Replies (12)

more options

I have exactly the same problem. Never had anything greek on my computer before.

more options

poundsford said

I have exactly the same problem. Never had anything greek on my computer before.

I have downloaded the latest Firefox from their download page - strangely it is numbered as 34.0.5 and installed it over version 34. If it crashes I'll post again to let people know whether or not it solves the "greek" anomaly.

more options

Try to reinstall Firefox.

Download a new copy of the Firefox application and save the disk image file to the desktop

Your personal data is stored elsewhere in the Firefox profile folder, so you won't lose your bookmarks and other personal data when you uninstall and (re)install Firefox.

more options

Downloaded and installed as suggested, now on ,34.0.5 - same problem occurs.

more options

We're sorry to hear that Firefox is crashing. In order to assist you better, please follow the steps below to provide us crash IDs to help us learn more about your crash.

  1. Enter about:crashes in the Firefox address bar and press Enter. A Submitted Crash Reports list will appear, similar to the one shown below.
  2. Copy the 5 most recent Report IDs that start with bp- and then go back to your forum question and paste that into the "Post a Reply" box. (Please don't take a screenshot of your crashes, just copy and paste the ID's. The below image is just an example of what your Firefox screen should look like)
aboutcrashesFx29

Thank you for your help!

More information and further troubleshooting steps can be found in the Troubleshoot Firefox crashes (closing or quitting unexpectedly) article.

more options

The problem is not the occasional crash it is the fact that the window reporting the crash is in Greek and not in English!

I am in the UK and I have the correct english version installed. Nothing else displays in Greek.

I am only posting the last 2 reports as those are the only ones that have any relevance.

	Date Submitted

bp-4886259e-9a8a-445e-9478-052c32141231 31/12/2014 17:17 bp-1ba947d6-7806-43cd-9e70-199ab2141218 18/12/2014 14:53

more options

You can try to disable OMTC and leave hardware acceleration in Firefox enabled.

  • about:config page: layers.offmainthreadcomposition.enabled = false

You can open the about:config page via the location/address bar. You can accept the warning and click "I'll be careful" to continue.

You can check for corrupted and duplicate fonts and other font issues:

You can try to disable hardware acceleration in Firefox.

  • Firefox > Preferences > Advanced > General > Browsing: "Use hardware acceleration when available"

You need to close and restart Firefox after toggling this setting.

more options

it's not solved. Even the folks at Firefox are puzzled :D if the experts don't even know the solution, what chances do we normal folks have ... ??? Will wait for an Einstein to come along and give us a solution :)

Modified by orbyss

more options

thanks cor-el for the reply. will try and do that and update here if it works. I'll have to wait for Firefox to crash of course :) cheers

Modified by orbyss

more options

- - - - -

Modified by orbyss

more options

I've even had Firefox reset and problem still occurs

more options

HI orbyss, For bug https://bugzilla.mozilla.org/show_bug.cgi?id=1115892 it looks like it may be expecting in a .1 release of the current version. That bug should keep you posted on the fix for when/what.