View Single Post
Old 11-07-2025, 11:05 AM   #6
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,983
Karma: 210162574
Join Date: Jan 2010
Device: Nexus 7, Kindle Fire HD
Just a follow-up here: you may try to quiet those warnings by unsetting the GTK_MODULES environment variable when launching Sigil. The easiest way might be to launch sigil from the terminal the following way:

Code:
GTK_MODULES="" sigil
I'm still not certain about the adwaita module warning (or why the adwaita theme changed for you after updating), but that may quiet things on the command line.

EDIT: also note that only when using the AppImage (with its bundled Python) will the plugin python interpreter process share Sigil's process environment. That means that when using an external python interpreter for plugins; env vars set via the env-vars.txt feature will not affect plugins. So Qt environment variables that Sigil is bound by will not affect a PySide6 plugin. For that, you would need to export the env var before launching Sigil. Much easier to just use the AppImage with its bundled python.

Last edited by DiapDealer; 11-07-2025 at 03:21 PM.
DiapDealer is offline   Reply With Quote