I use Bluefish for my web programming and since the latest upgrade (yay -Syyu) it won’t start any more. At the console I get the following:
bluefish: error while loading shared libraries: libpython3.10.so.1.0: cannot open shared object file: No such file or directory
As far as I know, Bluefish isn’t programmed in Python but in C, which would make this even more peculiar.
I then tried to install libpython, which ended with this error:
ERROR Backend subprocess exited when trying to invoke get_requires_for_build_wheel
==> FEHLER: an error occured in build().
-> error when building: python-find_libpython-exit status 4
-> Failed to install the following packages. Manual intervention is required:
python-find_libpython - exit status 4
What kind of manual intervention would be required? Or am I on the wrong path anyway?
I don’t know where is exactly the problem, but it seems to me that it is something you did. The library mentioned in the error (libpython3.10.so.1.0) is part of basic python package that you should have installed.
Your profile says you use stable branch, but have you, for any reason, installed python 3.11, that it is now in testing and unstable branches?
That seems to be the last version on testing. That’s a bit odd. This package comes directly from Arch, but if you have it properly installed, it seems to depend on old Python and it needs a rebuild.
I did the test of installing the Bluefish Testing version in my Stable system and it starts fine. Bluefish executable doesn’t depend on Python directly, it seems to be only that “zencoding” library. I suspect that the user has some plugin or personalization that triggers this library use at program boot time.
I also confirm an issue with the latest. I am running Manjaro KDE on a Raspberry Pi. I use Bluefish daily, just ran updates, and Bluefish no longer works.
Version is 2.2.13-1
I just did a downgrade to the prior bluefish while the community figures this out. It works now on 2.2.12-3
To run the downgrade (better than messing with a bunch of things for me), I first checked my pacman cache:
ls -l /var/cache/pacman/pkg/bluefish*
Results:
-rw-r–r-- 1 root root 2860604 Dec 11 2020 /var/cache/pacman/pkg/bluefish-2.2.12-2-aarch64.pkg.tar.xz
-rw-r–r-- 1 root root 2860176 Dec 31 2021 /var/cache/pacman/pkg/bluefish-2.2.12-3-aarch64.pkg.tar.xz
-rw-r–r-- 1 root root 566 Dec 31 2021 /var/cache/pacman/pkg/bluefish-2.2.12-3-aarch64.pkg.tar.xz.sig
-rw-r–r-- 1 root root 2926680 Feb 27 17:13 /var/cache/pacman/pkg/bluefish-2.2.13-1-aarch64.pkg.tar.xz
-rw-r–r-- 1 root root 566 Feb 27 17:13 /var/cache/pacman/pkg/bluefish-2.2.13-1-aarch64.pkg.tar.xz.sig
Then I rolled back to 2.2.12-3 with:
sudo pacman -U /var/cache/pacman/pkg/bluefish-2.2.12-3-aarch64.pkg.tar.xz
The original problem is in OP’s system, so there is no general problem that needs to be solved.
Also the “problem” is with version 2.2.13-2. Version 2.2.13-1 is the one in community repo and should be fine. So that leads me to believe that your problem is different.
What branch are you using?
If you don’t have the same exact error as OP, open your own thread.