Today I found some time and energy to investigate this further.
The details of how I got there don't seem worth going into, but the
short of it is that after
$ apt-get install libgdk-pixbuf2.0-{bin,common}/stable
libgdk-pixbuf-2.0-{dev,0{,:i386}}/stable
librsvg2-{2,bin,common,dev}/stable librsvg2-{2,common}:i386/stable
lutris now once again launches rather than presenting this error.
Without the librsvg2 downgrades, the error still manifested.
On the first launch after the downgrade, lutris seemed to be spamming
the console with
(net.lutris.Lutris:9818): Gtk-CRITICAL **: 09:10:57.396:
_gtk_css_image_get_concrete_size: assertion 'default_width > 0' failed
as the mouse moved over the window, although at first glance this
didn't seem to break anything else. After an exit and relaunch, these
messages don't seem to be persisting.
This isn't a real solution, but it does get me back into something
resembling operation, and it may point toward the cause and a potential
path toward a proper way to fix things.
I would like to find out whether upgrading libgdk-pixbuf2 again, but
leaving librsvg2 downgraded, makes the problem come back or not.
However, the current testing versions of the libgdk2-pixbuf packages
pull in the glycin transition, which adds enough new moving parts (and
has had enough icon-related issue reports elsewhere, some of them with
similar-seeming error messages) that I'm hesitant to risk installing it
without knowing what it's going to do and how I'd roll back if I needed
to.
If the test would be valuable enough, I can probably find the needed
libgdk-pixbuf2 package versions in my APT cache directory, although
there are enough of them that installing them that way would be a bit of
a pain.
--
Andrew J. Buehler
