Summary: | games-board/pychess-1.0.3 - (process:<snip>:WARNING : 07:13:20.979: Failed to load shared library libgtk-4.so.1 referenced by the | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Toralf Förster <toralf> |
Component: | Current packages | Assignee: | Gentoo Games <games> |
Status: | RESOLVED WORKSFORME | ||
Severity: | normal | CC: | ionen |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
emerge-info.txt
emerge-history.txt environment etc.portage.tar.bz2 games-board:pychess-1.0.3:20211227-061317.log temp.tar.bz2 |
Description
Toralf Förster
![]() Created attachment 760563 [details]
emerge-info.txt
Created attachment 760564 [details]
emerge-history.txt
Created attachment 760565 [details]
environment
Created attachment 760566 [details]
etc.portage.tar.bz2
Created attachment 760567 [details]
games-board:pychess-1.0.3:20211227-061317.log
Created attachment 760568 [details]
temp.tar.bz2
I don't have any experience with GTK 4, but that just sounds like your copy of it is broken. Ok, I stopped this image. Maybe completely unrelated but the process table for this image shows: 30570 /usr/bin/python3.9 -b /usr/lib/python-exec/python3.9/emerge --update app-misc/reptyr 32212 /usr/bin/coreutils --coreutils-prog-shebang=timeout /usr/bin/timeout --signal=15 --kill-after=5m 8h bash -c eval emerge --update media-fonts/mix-mplus-ipa whereas usually I see 905 timeout --signal=15 --kill-after=5m 8h bash -c eval emerge --update dev-ada/gtkada *** Bug 830684 has been marked as a duplicate of this bug. *** Can't reproduce so I'd like to think whatever happened with gtk4 is gone, albeit fwiw pychess shouldn't be trying to check GTK4: <string>:6: PyGIWarning: Gtk was imported without specifying a version first. Use gi.require_version('Gtk', '3.0') before import to ensure that the right version gets loaded. Not quite sure how that's happening given it does have a gi.require_version, but it only triggers at build-time (right version is used at runtime, maybe something to do with how the setup.py loads it), so is harmless as far as I can see (assuming gtk4 isn't broken anyway). Will see if this comes back again. |