ძიება მხარდაჭერაში

ნუ გაებმებით თაღლითების მახეში მხარდაჭერის საიტზე. აქ არასდროს მოგთხოვენ სატელეფონო ნომერზე დარეკვას, შეტყობინების გამოგზავნას ან პირადი მონაცემების გაზიარებას. გთხოვთ, გვაცნობოთ რამე საეჭვოს შემჩნევისას „დარღვევაზე მოხსენების“ მეშვეობით.

ვრცლად

Firefox unresponsive across USB to VGA or USB to DVI adapters?

  • 2 პასუხი
  • 14 მომხმარებელი წააწყდა მსგავს სიძნელეს
  • 3 ნახვა
  • ბოლოს გამოეხმაურა vmikayel

Firefox (and Thunderbird) are both completely unusable when you move their windows to the external display using either USB to VGA or USB to DVI adapters. The problem occurs using two different USB to VGA/DVI brands, and Mozilla software is the only software the problem occurs with. It's not always crashing, but instead like it can't render itself. You can't resize, maximize, or minimize the windows without them becoming responsive. All other applications work fine. Is there a bug? Are there rendering settings in about:config I can adjust? This is a major issue and I'll probably be forced to use IE or Chrome on these machines if this isn't fixable. I found one other post regarding this from Firefox version 4.0.2, but no solutions or responses to that. Any suggestions or solutions?

Firefox (and Thunderbird) are both completely unusable when you move their windows to the external display using either USB to VGA or USB to DVI adapters. The problem occurs using two different USB to VGA/DVI brands, and Mozilla software is the only software the problem occurs with. It's not always crashing, but instead like it can't render itself. You can't resize, maximize, or minimize the windows without them becoming responsive. All other applications work fine. Is there a bug? Are there rendering settings in about:config I can adjust? This is a major issue and I'll probably be forced to use IE or Chrome on these machines if this isn't fixable. I found one other post regarding this from Firefox version 4.0.2, but no solutions or responses to that. Any suggestions or solutions?

ყველა პასუხი (2)

A possibile workaround is setting layers.acceleration.disabled to true.

Workaround with layers.acceleration.disabled did not do it for me. What fixed it is simply disabling acceleration via menu "Tools->Options->Advanced->General->Use Hardware Acceleration when available". FF version is 12.0