Trying to install and run on Ubuntu 21.10

[gsargent70]

Any help with this error once UVtools installed and trying to run on Ubuntu 21.10?

System.DllNotFoundException: Unable to load shared library 'dl' or one of its dependencies

I have installed all dependencies per instructions. I have not compiled a new version of libcvextern. One thing to note is I used packages libdc1394-25 and libopenexr25 as these were the only versions available for 21.10. All other dependencies installed without issue.

Thanks!

[sn4k3]

You need to find out what is missing.
On UVtools directory run a terminal and run the command: ldd libcvextern.so |grep not

Post the output here

[gsargent70]

Also found this in the output of the compile for emgucv and opencv.

-- Checking for modules 'libavcodec;libavformat;libavutil;libswscale'
-- No package 'libavcodec' found
-- No package 'libavformat' found
-- No package 'libavutil' found
-- No package 'libswscale' found
-- FFMPEG is disabled. Required libraries: libavcodec;libavformat;libavutil;libswscale. Missing libraries: libavcodec;libavformat;libavutil;libswscale

I assume this means it won't compile the .so file I listed above but I checked and those libraries are installed in my system so don't know why it can't find them.

[gsargent70]

do you have the ffmpeg and ffmpeg-dev installed?

I do not. Just installed ffmpeg but I have no ffmpeg-dev package

[sn4k3]

Ok so now with ffmpeg try to recompile and repeat the copy of .so

[gsargent70]

nope same results with the same errors so that appears not to be it

[sn4k3]

Since this is related to opencv you can try to post your problem here: https://github.com/emgucv/emgucv/discussions

[tslater2006]

Those aren't hard-coded paths the application is looking for. They are part of debug/ stack information for error reporting only. Pretty common for those paths to match the machine where they were compiled.

…

On Mon, Nov 15, 2021, 9:16 PM gsargent70 ***@***.***> wrote: So was able to compile but I had to follow these instructions first so I had the dotnet SDK and runtimes on my machine https://docs.microsoft.com/en-us/dotnet/core/install/linux-ubuntu This did allow me to create a new libcvextern.so and copy it to the UVtools folder but this did change anything. Still the same error messages as above. I am a little confused by this error message UVtools.WPF.App.OnFrameworkInitializationCompleted() in D:\Tiago\Dropbox\Programming\C#\UVtools\UVtools.WPF\App.axaml.cs:line 70 Why is this trying to reference a file that is a hard coded path to I assume the development machine you are using? It references that path again later on in another error. And the main error says libdl: cannot open shared object file: No such file or directory as in it can't find it. Is it trying to look at the hard coded path referenced above? — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#342 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AANGZASW5PXJ76QW44V64D3UMHEHRANCNFSM5H7DTZQQ> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.

[gsargent70]

After many hours I have found the solution. It appears that if you do not have libdl named exactly as libdl.so it can not find it when booting UVtools. On Ubuntu 21.10 you must create a symlink from your existing libdl to one named as above. Here is an example command to do this.

sudo ln -s /lib/x86_64-linux-gnu/libdl.so.2 /lib/x86_64-linux-gnu/libdl.so

Once I did this UVtools booted right up from a fresh install. I did not need to do any recompile of emgucv. I hope this helps others with their issues.

[Daoenti]

This is less a UVTools thing and more a Linux general thing but look into the ldconfig command on your system, it is responsible for maintaining those symlinks in the library directories and should be ran any time a library is installed. Package installs of libraries do this automatically, it’s really only when you have to compile or install a library outside of packages.

[gsargent70]

Very strange then as all the libraries and dependencies were installed through the apt package manager so sounds like it should have triggered ldconfig during installs.