Gnubg no longer working after update

$ gnubg
gnubg: error while loading shared libraries: libpython3.12.so.1.0: cannot open shared object file: No such file or directory

Please read the announcements before updating:

I uninstalled gnubg and then installed it. Shouldn’t that be enough?

But ok, now I did pamac build gnubg, as written in the announcement and… I get the same error.


$ pacman -Qoq /usr/lib/python3.12
error: No package owns /usr/lib/python3.12

I can’t install it here, so can’t check if it works for me at least. Sorry.

Now I did. And still no difference.

I did get it installed just now, and it opened perfectly:

$ gnubg
gnubg
GNU Backgammon 1.08.003 20250206

Copyright (C) 1999-2004 Gary Wong.
Copyright (C) 2004-2024 the AUTHORS; for details type `show version'.

This program comes with ABSOLUTELY NO WARRANTY; for details type `show warranty'.
This is free software, and you are welcome to redistribute it under certain conditions; type `show copying' for details.

(No game) set gui showids on
(No game) save settings

So it would seem to be some kind of AUR package, possibly, that also need to be rebuilt. Have you tried rebuilding them all with:

pamac build $(pacman -Qoq /usr/lib/python3.12)

I did:

$ pamac build $(pacman -Qoq /usr/lib/python3.12)
error: No package owns /usr/lib/python3.12
No PKGBUILD file found in current directory

gnubg depends on another AUR package, gtkglext. I don’t see the connection to Python there, but you may want to try rebuilding gtkglext as well.

I’ve now run pamac build gtkglext, and after that pamac build gnubg once again, and I still get the same error message as reported above.

This seems sufficiently complicated that maybe @Mirdarthos or another moderator can split this to its own thread.

I would like to see the actual output from

type -a python
python --version
pamac clean --build-files
pamac build gnubg

Ai ai captn’!

1 Like

Did you clean your cache as recommended?

Edit: this was originally post #5 in this thread.

1 Like

You need to update every AUR package

Otherwise some dependencies may be not updated!

I found a solution.

It seems that something was using my miniconda python (which was at 3.12), and not /usr/bin/python.
I removed miniconda (since I don’t use it anymore), and I’ve re-run the commands proposed above.

Now gnubg successfully runs.


Thank you all for the help!!

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.