Om de ûnderfining foar jo te ferbetterjen is tydlik de funksjonaliteit dan dizze website troch ûnderhâldswurk beheind. Wannear in artikel jo probleem net oplost en jo in fraach stelle wolle, kin ús stipemienskip jo helpe yn @FirefoxSupport op Twitter en /r/firefox op Reddit.

Sykje yn Support

Mij stipescams. Wy sille jo nea freegje in telefoannûmer te beljen, der in sms nei ta te stjoeren of persoanlike gegevens te dielen. Meld fertochte aktiviteit mei de opsje ‘Misbrûk melde’.

Mear ynfo

Dizze konversaasje is argivearre. Stel in nije fraach as jo help nedich hawwe.

Ugly GUI after update from 6.0 to 6.0.1 - without GTK; 6.0 works fine

  • 2 antwurd
  • 1 hat dit probleem
  • 3 werjeftes
  • Lêste antwurd fan wdolek

more options

I have updated FF to 6.0.1 on Fedora 14, Gnome 2.6, and it looked very bad. Missing connection with GTK - so windows - especially menu bar - is really crappy, like 10 years old CDE GUI :)

Rolled back to 6.0 because it works with current sw installed.

This is error message after running FF from terminal: Unable to locate theme engine in module_path: "clearlooks"

In "Troubleshooting Information" sending info from 6.0 where it is OK. Hope it will help.

I have updated FF to 6.0.1 on Fedora 14, Gnome 2.6, and it looked very bad. Missing connection with GTK - so windows - especially menu bar - is really crappy, like 10 years old CDE GUI :) Rolled back to 6.0 because it works with current sw installed. This is error message after running FF from terminal: Unable to locate theme engine in module_path: "clearlooks" In "Troubleshooting Information" sending info from 6.0 where it is OK. Hope it will help.

Alle antwurden (2)

more options

Start Firefox in Diagnose Firefox issues using Troubleshoot Mode to check if one of the extensions is causing the problem (switch to the DEFAULT theme: Tools > Add-ons > Appearance/Themes).

Try to disable hardware acceleration.

  • Edit > Preferences > Advanced > General > Browsing: "Use hardware acceleration when available"
more options

Nope, it didn't help (as I though before anyway). I made another question, because 6.0.2 is still affected: https://support.mozilla.com/cs/questions/878907