https://bugs.documentfoundation.org/show_bug.cgi?id=150111
V Stuart Foote <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |WORKSFORME Status|NEW |RESOLVED --- Comment #17 from V Stuart Foote <[email protected]> --- (In reply to Telesto from comment #16) > @Stuart > Stumbling across this bug. Any change this being related to bug 166122 Only remotely in that Win11 24H2 has moved to WDDM 3.2, these older GPUs are probably only WDDM 1.3 or possibly WDDM 2.7 capable. The issue with the 25.2 release was LO moving from skia m116 to m130 build--major jump. Suspect changes in how the vulkan rendering surface instance is spun up for testing. And it is simply not working/not supported on the older GPU/driver pairings. The crash/no-start was with the Vulkan rendering test itself, panic before the fall back, and the deny list process not preventing that testing. Fortunately the generic skia Raster framed rendering remains reliable, so fix for bug 166122 is a more robust fall back and recovery using skia software rendering. Don't have to completely roll back to GDI+ rendering paths, though they are still an option when system HW/driver are severely challenged. This issue can probably be closed out => WFM as it really is no longer relevant, project is doing a better job of detecting Vulkan rendering failure at 25.2.4 onward. -- You are receiving this mail because: You are the assignee for the bug.
