If you are interested in fixing it - search https://bugzilla.opensuse.org, if nothing similar is found, create bug report there (same user/password).
As a workaround until it is fixed you can rollback to previous snapshot and lock affected package(s) so they are not updated.
I don’t see older versions available in YAST Software manager.
Tumbleweed repositories always contain the latest released versions. There are historical repositories for the last couple of dozens of snapshots, you can switch between them using tumbleweed command (provided by tumbleweed-cli package).
I’ve never used this snapshots feature before and before trying this I want to make sure it’s Sigil that got broken. After an update a few days ago I noticed that fonts in Dolphin got rendered visibly worse and after today’s update fonts in Gimp interface got absolutely atrocious. So I suspect something got wrong with my underlying libraries, something related to Qt, and this might cause problems to Sigil.
Right now I tried to get a screenshot of Gimp interface and discovered that Spectacle doesn’t start either.
The spectacle problem is/was related to a rebuild problem of libkImageAnnotator.so.0. Sigil does not depend on this library i think therefore i do not see a direct connection here.
I used a VM with installed systemd-coredump and started sigil from a shell. The core is saved in /var/lib/systemd/coredump/ and could be explored with
>coredumpctl debug /usr/lib64/sigil/sigil
This looks to me like a QT5 problem possibly related to the gcc12 switch. But i am not an expert on these topics.
After recent updates Spectacle is working, but not Sigil, and fonts in GIMP interface are still bad. Maybe it’s a GTK issue - I think both GIMP and Sigil rely on GTK.
Now with Spectacle I can take GIMP screenshot - in the window titles font is from Plasma settings but the rest is GTK, at least as far as I understand. There is no aliasing, shading, or whatever tricks they use to make fonts look smooth.
Sorry for not checking in on this thread. I was just going to post an update but last two messages from Rawar make it redundant.
Anyway, in case someone has a similar problem in the future - my workaround was to install Sigil via Flatpak, which is a container with its own set of dependencies that doesn’t rely on the rest of the system, and Sigil worked fine there.
It was only yesterday that I again tried Sigil from the repos and discovered that the problem has been fixed, apparently two weeks ago.