Issues with Sigil after updating Archlinux

[RbnJrg]

After updating my Arch, I receive the following messages from Sigil:

Gtk-Message: 11:11:17.151: Failed to load module "canberra-gtk-module"
Gtk-Message: 11:11:17.166: Failed to load module "canberra-gtk-module"

(sigil:21910): Gtk-WARNING **: 11:11:17.341: Imposible encontrar el motor de temas en la ruta al _modulo: «adwaita», (Unable to find the theme engine in the path to _module: «adwaita»)

And after updating the system, Sigil looks awfull with adwaita (I had to change it to another theme). By the way, I have installed the last versions of libcanberra, adwaita-icon-theme and gnome-themes-extra.

[DiapDealer]

AppImage?

I'm not sure why things have graphically changed for you. libcanberra is a sound theme.

I haven't updated my Arch in a week or so. I'll try it when I get home. But I don't use the Gnome desktop and/or Adwaita, so my mileage may vary.

I doubt the canberra module message is that relevant--certainly not to your theming issues. Pretty sure you can safely ignore it.

[DiapDealer]

I did a full update on my Arch machine and experienced no changes in Sigil's launch messages. AppImage or Repository version.

For the record: Gnome and Adwaita continue to make the theming of non-gtk apps more and more problematic with each new update in my opinion.

[RbnJrg]

Originally Posted by DiapDealer

I did a full update on my Arch machine and experienced no changes in Sigil's launch messages. AppImage or Repository version.

For the record: Gnome and Adwaita continue to make the theming of non-gtk apps more and more problematic with each new update in my opinion.

Thank you Diap! Do one more thing: run Sigil from CLI, from a console and you'll see the messages. And those messages also appear when I run a Sigil plugin in the Sigil console. Yes, they are harmless but also annoying.

[DiapDealer]

That's exactly what I did. That's what I meant by "no changes in Sigil's launch messages". I don't even get your messages when I fire up a Gnome desktop session on Arch (with the Adwaita theme) and launch Sigil (from a terminal). I understand they're annoying, but why launch from the command line in the first place? I'm fairly certain we're not going to be able to guarantee a warning-free console launch across all distros, let alone all DEs and all themes (and all configs) on those distros.

[DiapDealer]

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:

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.