View Single Post
Old 11-07-2025, 06:01 PM   #7
RbnJrg
Wizard
RbnJrg ought to be getting tired of karma fortunes by now.RbnJrg ought to be getting tired of karma fortunes by now.RbnJrg ought to be getting tired of karma fortunes by now.RbnJrg ought to be getting tired of karma fortunes by now.RbnJrg ought to be getting tired of karma fortunes by now.RbnJrg ought to be getting tired of karma fortunes by now.RbnJrg ought to be getting tired of karma fortunes by now.RbnJrg ought to be getting tired of karma fortunes by now.RbnJrg ought to be getting tired of karma fortunes by now.RbnJrg ought to be getting tired of karma fortunes by now.RbnJrg ought to be getting tired of karma fortunes by now.
 
Posts: 1,880
Karma: 8821117
Join Date: Mar 2013
Location: Rosario - Santa Fe - Argentina
Device: Kindle 4 NT
Quote:
Originally Posted by DiapDealer View Post
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.
Thank you very much Diap! Indeed, by running Sigil from CLI with GTK_MODULES="" sigil and also by adding env GTK_MODULES="" in the Sigil launcher stopped those annoying messages.
RbnJrg is offline   Reply With Quote