We're calling on all EU-based Mozillians with iOS or iPadOS devices to help us monitor Apple’s new browser choice screens. Join the effort to hold Big Tech to account!

Avatar for Username

Etsi tuesta

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.

Lue lisää

Ketju on arkistoitu. Esitä kysymys, jos tarvitset apua.

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

  • 2 vastausta
  • 1 henkilöllä on sama ongelma
  • 3 näyttöä
  • Viimeisin kirjoittaja wdolek

wdolek
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.

Kaikki vastaukset (2)

cor-el
cor-el
  • Moderator
  • Top 10 Contributor
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"
wdolek
wdolek Kysymyksen kysyjä
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