why did upgrading to 44 break direct2d azure backends after upgrade??
i upgraded from 42 to 44, and now i can't get direct2d backends for azure canvas and content, Asynchronous Pan/Zoom, and i'm getting the following error message: "(#0) Error Attempting DWrite without D2D support".
everything was working perfectly before upgrade.
here's some info:
Adapter Description NVIDIA GeForce 8400 GS Adapter Drivers nvd3dumx,nvwgf2umx,nvwgf2umx nvd3dum,nvwgf2um,nvwgf2um
Asynchronous Pan/Zoom none
Device ID 0x06e4 DirectWrite Enabled true (6.1.7601.17514) Driver Date 2-3-2015 Driver Version 9.18.13.4144
AzureCanvasBackend skia AzureContentBackend cairo AzureFallbackCanvasBackend cairo AzureSkiaAccelerated 0 (#0) Error Attempting DWrite without D2D support
normally my fallback is cairo
and both my backends are direct2d. strangely enough i've never ever gotten skia to work as backend, and now it works for some reason, but i don't need it. i wanted both backends to revert to direct2d the way i had them, asynchronous pan/zoom enabled again, and directwrite to work properly.
normally directwrite works without a hitch, and this is the first time i've ever recieved an error message about direct write.
all i did was upgrade to 44, and it broke my backends, asynchronous pan/zoom, and my directwrite apparently. any idea what's going on, and or how to fix it??
i'm on a different computer right now, cuz firefox is acting screwy on the machine in question.
All Replies (1)
In 43 there was an issue with NVIDIA firewalls:https://bugzilla.mozilla.org/show_bug.cgi?id=1233237 there it was fixed however and based on connectivity. The work around in the past since it is not turned on by default was:
- gfx.font_rendering.directwrite.enabled set to true
- mozilla.widget.render-mode set to 6