View Single Post
Old 11-07-2020, 08:22 AM   #9
KevinH
Sigil Developer
KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.
 
Posts: 8,807
Karma: 6000000
Join Date: Nov 2009
Device: many
Did you try removing the sigil.ini file? Mixing Sigil 0.9.14 and Sigil 1.x or later could be an issue that could corrupt the sigil.ini file.

If that doesn't help, the issue does seem to be with related to the virtual video driver that QtWebEngineProcess sees. So it must be a related to a setting used by Virtual box?

Sigil 0.9.14 used the much older QtWebkit for Preview whereas all later builds use QtWebEngine (Chrome based).

You could try installing Chrome on your virtual box or The Falkon Browser (QtWebEngine based browser) to see if they have similar issues.

Many people run Windows and Sigil under Virtual Machines with no issues, so it is related to your set-up somehow.
KevinH is offline   Reply With Quote