Where did you install Firefox from? Help Mozilla uncover 3rd party websites that offer problematic Firefox installation by taking part in our campaign. There will be swag, and you'll be featured in our blog if you manage to report at least 10 valid reports!

Pesquisar no site de suporte

Evite golpes de suporte. Nunca pedimos que você ligue ou envie uma mensagem de texto para um número de telefone, ou compartilhe informações pessoais. Denuncie atividades suspeitas usando a opção “Denunciar abuso”.

Learn More

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

  • 2 respostas
  • 1 tem este problema
  • 3 visualizações
  • Última resposta de 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.

Todas as respostas (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