You are not logged in.

#1 2022-08-30 23:19:47

FallenSnow
Member
Registered: 2014-04-07
Posts: 35

Pulseview linked to python 3.9 in official repos

Starting pulseview results in nothing happening. When starting it in a terminal, it reports an error about the python shared library being not available.

$ pulseview
pulseview: error while loading shared libraries: libpython3.9.so.1.0: cannot open shared object file: No such file or directory
$ ldd /usr/bin/pulseview | grep python
	libpython3.9.so.1.0 => not found
$ pacman -Q pulseview python
pulseview 0.4.2-7.1
python 3.10.6-1.
$ sudo pacman -Sy pulseview python
:: Synchronizing package databases...
 core-x86-64-v3 is up to date
 extra-x86-64-v3 is up to date
 community-x86-64-v3 is up to date
 core is up to date
 extra is up to date
 community is up to date
 multilib is up to date
 archzfs is up to date
warning: pulseview-0.4.2-7.1 is up to date -- reinstalling
warning: python-3.10.6-1.1 is up to date -- reinstalling
resolving dependencies...
looking for conflicting packages...

Packages (2) pulseview-0.4.2-7.1  python-3.10.6-1.1

Offline

#2 2022-08-30 23:23:57

V1del
Forum Moderator
Registered: 2012-10-16
Posts: 17,032

Re: Pulseview linked to python 3.9 in official repos

None of these three -v3 repos are official repositories how sure are you you didn't get an old pulseview from there? The current "normal" pulseview version is 0.4.2-7 and python 3.10.6-1 respectively, note the lack of a .1 at the end.

Offline

#3 2022-08-30 23:26:05

Scimmia
Fellow
Registered: 2012-09-01
Posts: 9,555

Re: Pulseview linked to python 3.9 in official repos

ldd is not all that useful here. Use lddtree from the pax-utils package. And don't grep it.

Last edited by Scimmia (2022-08-30 23:26:18)

Offline

#4 2022-08-31 00:31:06

FallenSnow
Member
Registered: 2014-04-07
Posts: 35

Re: Pulseview linked to python 3.9 in official repos

You're right, sorry these weren't from the offical repos. I switched to the official repositories and pulseview is now working.

$ lddtree /usr/bin/pulseview
...
libsigrokdecode.so.4 => /usr/lib/libsigrokdecode.so.4
        libpython3.9.so.1.0 => None
...

So I guess that means it's an issue with libsigrokdecode instead and it's in the non official alhp repos.

Thank you both!

Offline

Board footer

Powered by FluxBB