Thread: Preview failure
View Single Post
Old 04-24-2025, 05:38 PM   #30
DiapDealer
Grand Sorcerer
DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.
 
DiapDealer's Avatar
 
Posts: 28,736
Karma: 206739468
Join Date: Jan 2010
Device: Nexus 7, Kindle Fire HD
Quote:
Originally Posted by JSWolf View Post
It's probably the graphics drivers used for the old computers. You culd try setting the following environment variable on the old computers and then try the latest Sigil.

Code:
QTWEBENGINE_CHROMIUM_FLAGS="--disable-gpu"
No need. Setting that precise variable before launch is EXACTLY what Sigil's "Disable GPU Acceleration in QtWebEngine/Preview" preference setting does.

https://github.com/Sigil-Ebook/Sigil.../main.cpp#L479

In this case, it's entirely possible that the embedded blocklist in Sigil 2.4's Qt6.8.3 has blocked the particular driver version(s) on the two oldest machines.

If setting QSG_RHI_BACKEND to opengl doesn't work, one could try setting QTWEBENGINE_CHROMIUM_FLAGS to --disable-gpu-blocklist, but there's a reason the block list exists.

Last edited by DiapDealer; 04-24-2025 at 05:43 PM.
DiapDealer is offline   Reply With Quote