https://bugs.documentfoundation.org/show_bug.cgi?id=166122
V Stuart Foote <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Ever confirmed|0 |1 Status|UNCONFIRMED |NEEDINFO CC| |[email protected], | |[email protected] --- Comment #5 from V Stuart Foote <[email protected]> --- @Mike, * Since the LO upgrade install launch defaults are GPU testing with HA set and skia/Vulkan rendering with fall back, might the issue be the skia testing? So both skia/Vulcan and the skia based raster framing failing (the skia fall back also fails). Then the default with a Safe mode (which I'd thought was to use skia raster framing, but maybe not) also fails but actually launches using GDI+ 'default; rendering? With or without the Hardware Acceleration check box, which I have always perceived as HA under os/DE control (i.e. more rendering of VCL by CPU, but less extensive than the skia paths). Also, still could be a GPU driver (which *can* get clobbered) with Windows build updates. And users rolling back to prior builds have profiles configured to skia/raster or GDI 'default' rendering, and they squeak by on 'default' rendering. Think we need to see systems specifics of iGPU/dGPU present, and the drivers for each, for folks having this issue with the KB5055523 (OS Build 26100.3775) or earlier KB5053656 (OS Build 26100.3624 )Windows builds applied. Users can run the Windows 'Device Manager' panel and from the Display adapters identify the GPU and drivers, alternatively the Components -> Display panel of a run of msinfo32.exe For Vulkan support, Intel, nVidia and AMD all include the 'vulkaninfo' command in their GPU driver bundles that Windows should access. From that long report details in the: Device Properties and Extensions: VkPhysicalDeviceProperties: for the active GPU would be useful. -- You are receiving this mail because: You are the assignee for the bug.
