Project

General

Profile

Bug #2011

[community/pulseview] probably needs to be recompiled

GNUtoo - about 4 years ago - . Updated over 3 years ago.

Status:
fixed
Priority:
broken
Assignee:
% Done:

0%


Description

Hi, when I run pulseview I have that:

$ pulseview 
pulseview: error while loading shared libraries: libpython3.6m.so.1.0: cannot open shared object file: No such file or directory

While I have sigrok-cli compiled aside, pulseview is from parabola packages and doesn't use any /usr/local libraries:

$ ldd /usr/bin/pulseview
    linux-gate.so.1 (0xb7f0d000)
    libboost_filesystem.so.1.67.0 => /usr/lib/libboost_filesystem.so.1.67.0 (0xb7cf7000)
    libboost_serialization.so.1.67.0 => /usr/lib/libboost_serialization.so.1.67.0 (0xb7cb8000)
    libboost_system.so.1.67.0 => /usr/lib/libboost_system.so.1.67.0 (0xb7cb1000)
    libpthread.so.0 => /usr/lib/libpthread.so.0 (0xb7c90000)
    libsigrokcxx.so.4 => /usr/lib/libsigrokcxx.so.4 (0xb7c45000)
    libsigrok.so.4 => /usr/lib/libsigrok.so.4 (0xb7b5c000)
    libglibmm-2.4.so.1 => /usr/lib/libglibmm-2.4.so.1 (0xb7ade000)
    libsigrokdecode.so.4 => /usr/lib/libsigrokdecode.so.4 (0xb7acb000)
    libglib-2.0.so.0 => /usr/lib/libglib-2.0.so.0 (0xb799c000)
    libQt5Widgets.so.5 => /usr/lib/libQt5Widgets.so.5 (0xb727b000)
    libQt5Gui.so.5 => /usr/lib/libQt5Gui.so.5 (0xb6c92000)
    libQt5Core.so.5 => /usr/lib/libQt5Core.so.5 (0xb678e000)
    libstdc++.so.6 => /usr/lib/libstdc++.so.6 (0xb6615000)
    libm.so.6 => /usr/lib/libm.so.6 (0xb650d000)
    libgcc_s.so.1 => /usr/lib/libgcc_s.so.1 (0xb64f0000)
    libc.so.6 => /usr/lib/libc.so.6 (0xb630e000)
    /lib/ld-linux.so.2 => /usr/lib/ld-linux.so.2 (0xb7f0f000)
    librt.so.1 => /usr/lib/librt.so.1 (0xb6303000)
    libieee1284.so.3 => /usr/lib/libieee1284.so.3 (0xb62f5000)
    libgobject-2.0.so.0 => /usr/lib/libgobject-2.0.so.0 (0xb6292000)
    libsigc-2.0.so.0 => /usr/lib/libsigc-2.0.so.0 (0xb628a000)
    libserialport.so.0 => /usr/lib/libserialport.so.0 (0xb6277000)
    libftdi1.so.2 => /usr/lib/libftdi1.so.2 (0xb6266000)
    libusb-1.0.so.0 => /usr/lib/libusb-1.0.so.0 (0xb6248000)
    libzip.so.5 => /usr/lib/libzip.so.5 (0xb6226000)
    libgmodule-2.0.so.0 => /usr/lib/libgmodule-2.0.so.0 (0xb6220000)
    libpython3.6m.so.1.0 => not found
    libpcre.so.1 => /usr/lib/libpcre.so.1 (0xb61a9000)
    libGL.so.1 => /usr/lib/libGL.so.1 (0xb6145000)
    libpng16.so.16 => /usr/lib/libpng16.so.16 (0xb6107000)
    libharfbuzz.so.0 => /usr/lib/libharfbuzz.so.0 (0xb6046000)
    libz.so.1 => /usr/lib/libz.so.1 (0xb602d000)
    libsystemd.so.0 => /usr/lib/libsystemd.so.0 (0xb5f96000)
    libicui18n.so.62 => /usr/lib/libicui18n.so.62 (0xb5cba000)
    libicuuc.so.62 => /usr/lib/libicuuc.so.62 (0xb5af3000)
    libpcre2-16.so.0 => /usr/lib/libpcre2-16.so.0 (0xb5a79000)
    libdouble-conversion.so.3.0.0 => /usr/lib/libdouble-conversion.so.3.0.0 (0xb5a60000)
    libdl.so.2 => /usr/lib/libdl.so.2 (0xb5a5a000)
    libffi.so.6 => /usr/lib/libffi.so.6 (0xb5a51000)
    libudev.so.1 => /usr/lib/libudev.so.1 (0xb5a2f000)
    libbz2.so.1.0 => /usr/lib/libbz2.so.1.0 (0xb5a1d000)
    libcrypto.so.1.1 => /usr/lib/libcrypto.so.1.1 (0xb57bd000)
    libGLX.so.0 => /usr/lib/libGLX.so.0 (0xb579a000)
    libX11.so.6 => /usr/lib/libX11.so.6 (0xb564b000)
    libXext.so.6 => /usr/lib/libXext.so.6 (0xb5636000)
    libGLdispatch.so.0 => /usr/lib/libGLdispatch.so.0 (0xb55d4000)
    libfreetype.so.6 => /usr/lib/libfreetype.so.6 (0xb5503000)
    libgraphite2.so.3 => /usr/lib/libgraphite2.so.3 (0xb54db000)
    liblzma.so.5 => /usr/lib/liblzma.so.5 (0xb54b0000)
    liblz4.so.1 => /usr/lib/liblz4.so.1 (0xb5491000)
    libgcrypt.so.20 => /usr/lib/libgcrypt.so.20 (0xb53b0000)
    libicudata.so.62 => /usr/lib/libicudata.so.62 (0xb3a15000)
    libxcb.so.1 => /usr/lib/libxcb.so.1 (0xb39ea000)
    libgpg-error.so.0 => /usr/lib/libgpg-error.so.0 (0xb39c6000)
    libXau.so.6 => /usr/lib/libXau.so.6 (0xb39c1000)
    libXdmcp.so.6 => /usr/lib/libXdmcp.so.6 (0xb39ba000)

History

#1

Updated by freemor about 4 years ago

Considering the python related breakage, and given the fact that pulseview runs fine on my X86_64 machine. I'm guessing you are coming from i686, yes?

#2

Updated by freemor about 4 years ago

  • Priority changed from bug to broken

Yes this is an issue for i686

As both python3 and pulseview are upstream I'm uessing someone just forgot the rebuild pulseview as it is a slightly more obsucre program

I'll set up an arch linux 32 VM tomorrow and test it there. If the problem lives there I'll push this upstream

#3

Updated by GNUtoo over 3 years ago

  • Assignee set to GNUtoo

It works now

#4

Updated by GNUtoo over 3 years ago

  • Status changed from open to fixed

Also available in: Atom PDF