search

ufo-kit / ufo-core

GLib-based framework for GPU-based data processing
GNU Lesser General Public License v3.0
24 stars 8 forks source link

ufo unable to read files #190

Closed NeutroTom closed 1 year ago

NeutroTom commented 1 year ago

I recently had to reinstall ufo-core ufo filters and tofu, and am now running into the problem that ufo is unable to read any files.

Running this test directly on the home directory (where the slice is located, autocomplete finds it there):
ufo-launch read path='slice00322.tif' ! blur size=20 sigma=5 ! write filename=testout.tif results in:
Error executing pipeline: read: `slice00322.tif' does not match any files

I get the same result if I instead use the full path or any other location.

Please tell me what kind of further information you need.
Best regards

tfarago commented 1 year ago

This is strange, I assume you have tried without the single quotes? What is your terminal, bash? I also need OS and glib version, thanks.

NeutroTom commented 1 year ago

Yes, I tried it without the quotes, same result.

The terminal is bash and I am now running ubuntu 18.04.06 LTS (before I had 20.04) running ldd --version shows (Ubuntu GLIBC 2.27-3ubuntu1.6), so I guess 2.27

I only recently learned that ubuntu 18.04 might be the problem.
If you dont have any other ideas I will try to get our IT people to either give me 20.04 again, or upgrade my machine to 22.04.

matze commented 1 year ago

If you built yourself make sure you have have libtiff-dev installed.

tfarago commented 1 year ago

Oh, yes, thanks @matze, that's most probably it. Just check what meson outputs (or cmake) and look for something like "tiff dependency found". Ubuntu 18.04 cannot be the problem, we still have some servers with that OS running it.

tfarago commented 1 year ago

There is a list of packages to install for Ubuntu 20.04 here.

NeutroTom commented 1 year ago

Looks like libtiff-dev was the main issue there, I reran the installation and now it is working. There were quite a few dependencies that did somehow not get installed correctly, so I had to build them manually. But I think the issue there was with our local filesystem and permissions, not on your side.

Thank you for the help!