SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Hi friends, today I found that I have a strange error when I was try to update openshot...after this update with sbopkg, when I start openshot-qt in terminal I see this errors:
Code:
logger:ERROR Traceback (most recent call last):
logger:ERROR File "/usr/bin/openshot-qt", line 11, in <module>
logger:ERROR load_entry_point('openshot-qt==2.4.2', 'gui_scripts', 'openshot-qt')()
logger:ERROR File "/usr/lib64/python3.6/site-packages/pkg_resources/__init__.py", line 480, in load_entry_point
logger:ERROR return get_distribution(dist).load_entry_point(group, name)
logger:ERROR File "/usr/lib64/python3.6/site-packages/pkg_resources/__init__.py", line 2693, in load_entry_point
logger:ERROR return ep.load()
logger:ERROR File "/usr/lib64/python3.6/site-packages/pkg_resources/__init__.py", line 2324, in load
logger:ERROR return self.resolve()
logger:ERROR File "/usr/lib64/python3.6/site-packages/pkg_resources/__init__.py", line 2330, in resolve
logger:ERROR module = __import__(self.module_name, fromlist=['__name__'], level=0)
logger:ERROR File "/usr/lib64/python3.6/site-packages/openshot_qt/launch.py", line 53, in <module>
logger:ERROR from classes.app import OpenShotApp
logger:ERROR File "/usr/lib64/python3.6/site-packages/openshot_qt/classes/app.py", line 41, in <module>
logger:ERROR from classes import info, settings, project_data, updates, language, ui_util, logger_libopenshot
logger:ERROR File "/usr/lib64/python3.6/site-packages/openshot_qt/classes/logger_libopenshot.py", line 31, in <module>
logger:ERROR import openshot
logger:ERROR File "/usr/lib64/python3.6/site-packages/openshot.py", line 28, in <module>
logger:ERROR _openshot = swig_import_helper()
logger:ERROR File "/usr/lib64/python3.6/site-packages/openshot.py", line 24, in swig_import_helper
logger:ERROR _mod = imp.load_module('_openshot', fp, pathname, description)
logger:ERROR File "/usr/lib64/python3.6/imp.py", line 243, in load_module
logger:ERROR return load_dynamic(name, filename, file)
logger:ERROR File "/usr/lib64/python3.6/imp.py", line 343, in load_dynamic
logger:ERROR return _load(spec)
logger:ERROR ImportError
logger:ERROR :
logger:ERROR libx265.so.151: cannot open shared object file: No such file or directory
After ffmpeg:
Code:
ffmpeg: error while loading shared libraries: libx265.so.151: cannot open shared object file: No such file or directory
but I have libx265.so.160 in /usr/lib64 not 151 and I have all the .so files that I checked with yes when configure ffmpeg before few months and then everything was ok??
my OS is SLackware 14.2 64 bit current
Sorry for my english skills
In case of a slight version mismatch, you may try just to symlink an old version to a newer one. I did it for some proprietary software that was built against the certain versions of libraries, and it worked well. However, there always is a chance of segfaults or more extraordinary bugs if signatures of some exported functions changed in the new version.
I would strongly suggest that no one follows the above solution. Its a poor hack that has a lot of potential to cause issues, especially later when the hack has been forgotten about.
In this case recompiling ffmpeg will probably work. In the event where recompiling the program is not possible such as a proprietary program and the old library is really needed, then supplying it in a package like aaa_elflibs would be better.
Ok guys, I recompiled ffmpeg and now after ffmpeg:
Code:
~# ffmpeg
ffmpeg version 3.2.4 Copyright (c) 2000-2017 the FFmpeg developers
built with gcc 5.5.0 (GCC)
configuration: --prefix=/usr --libdir=/usr/lib64 --shlibdir=/usr/lib64 --docdir=/usr/doc/ffmpeg-3.2.4/html --mandir=/usr/man --disable-debug --enable-shared --disable-static --enable-gpl --enable-version3 --enable-avresample --arch=x86_64 --enable-libfontconfig --enable-libfreetype --enable-libfribidi --enable-gnutls --enable-libass --enable-libbluray --enable-libcaca --enable-libcdio --enable-openal --enable-libssh --enable-libtheora --enable-libv4l2 --enable-libvorbis --enable-libvpx --enable-libx264 --enable-libx265 --enable-libxvid --enable-libmp3lame --enable-opengl --enable-libopenjpeg --enable-libpulse --enable-libsmbclient --enable-libwavpack --enable-x11grab
libavutil 55. 34.101 / 55. 34.101
libavcodec 57. 64.101 / 57. 64.101
libavformat 57. 56.101 / 57. 56.101
libavdevice 57. 1.100 / 57. 1.100
libavfilter 6. 65.100 / 6. 65.100
libavresample 3. 1. 0 / 3. 1. 0
libswscale 4. 2.100 / 4. 2.100
libswresample 2. 3.100 / 2. 3.100
libpostproc 54. 1.100 / 54. 1.100
Hyper fast Audio and Video encoder
usage: ffmpeg [options] [[infile options] -i infile]... {[outfile options] outfile}...
Use -h to get full help or, even better, run 'man ffmpeg'
But new version of libopenshot can't compile and give this error:
Code:
[ 76%] Building CXX object src/CMakeFiles/openshot.dir/TextReader.cpp.o
[ 77%] Linking CXX shared library libopenshot.so
[ 77%] Built target openshot
Scanning dependencies of target openshot-player
[ 78%] Building CXX object src/CMakeFiles/openshot-player.dir/Qt/demo/main.cpp.o
[ 79%] Linking CXX executable openshot-player
/usr/lib64/gcc/x86_64-slackware-linux/5.5.0/../../../../x86_64-slackware-linux/bin/ld: warning: libx265.so.151, needed by /usr/local/lib64/libavcodec.so, not found (try using -rpath or -rpath-link)
/usr/local/lib64/libavcodec.so: undefined reference to `x265_api_get_151'
collect2: error: ld returned 1 exit status
src/CMakeFiles/openshot-player.dir/build.make:112: recipe for target 'src/openshot-player' failed
make[2]: *** [src/openshot-player] Error 1
CMakeFiles/Makefile2:155: recipe for target 'src/CMakeFiles/openshot-player.dir/all' failed
make[1]: *** [src/CMakeFiles/openshot-player.dir/all] Error 2
Makefile:149: recipe for target 'all' failed
make: *** [all] Error 2
libopenshot:
Would you like to continue processing the rest of the
queue or would you like to abort? If this failed
package is a dependency of another package in the queue
then it may not make sense to continue.
Seems like look for old version libx265.so but I don't have this .so file. I don't understand programming but I try find in make files in /tmp/Sbo/libopenshot something with "libx265.so.151" and hard replace with "libx265.so.160", but I can't find anything like this..
/usr/lib64/gcc/x86_64-slackware-linux/5.5.0/../../../../x86_64-slackware-linux/bin/ld: warning: libx265.so.151, needed by /usr/local/lib64/libavcodec.so, not found (try using -rpath or -rpath-link)
/usr/local/lib64/libavcodec.so: undefined reference to `x265_api_get_151'
you have installed manually ffmpeg in /usr/local and the build is finding that instead of the one you packaged.
Your error message indicates you still have the old ffmpeg installed. Did you happen to use installpkg instead of upgradepkg? If so I would suggest using removepkg on all installed ffmpeg packages and then reinstalling the correct one.
Alternatively there is still another program on your system that needs to be recompiled. This script is somewhat slow, but should help point out what those programs are as it will ldd your entire system and report missing libraries.
Aaah yes yes...I forgot that in some moments of madness I just cp some files from /usr/lib64 to /usr/local/lib64 trying to fix everything without rebuild..now I just remove them and everything is ok..
Thanks to all
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.