I installed the Flatpak version of Darktable on my Linux Mint laptop and am trying to import raw and jpg files from an SSD drive. These are files I had in Darktable on a previous laptop. Nothing happens when I either add to library or copy and import. I thought it might be Flatpak but I opened up the file system in Flatseal but still nothing. It’s probably something real simple.
When I open Darktable I get a quick “No open CL devices found” at the bottom and then it goes away.
edit: I uninstalled the Flatpak version and installed the non-Flatpak version. I have access to my files now but the version is 3.8.1 rather than the 4.6.0 as a Flatpak. I’m not sure if I should keep it or look for another solution.
Compiling it yourself from source is not hard. The readme lists the required dependencies, and many, including me, have posted detailed instructions and build scripts. You’d get a build optimised for your machine.
Have you checked if OBS has a package for your distro?
Hi,
which version of Linux Mint are you using?
As this is based on Ubuntu, there should be a package readily availabe via the OB sources linked via the darktable website.
And select there the Ubuntu Repo that matches to the foundation of your specific Mint Version.
If found follow the respective steps documented to add repository and install …
Might be anyway a good idea to do some reading at the darktable side and in the manual
That’s a bug, which occurs if you use the recursive option when importing. Simply avoid that option for the time being.
OpenCL has nothing to do with that. If you want to use OpenCL for acceleration, you’ll have to install the OpenCL drivers into the Flatpak environment, too.
Is the SSD your root drive? If not how is it mounted?
The flatpak should be able to access all files by default, unless you’ve mounted the drive with your desktop emvornment’s file.manger, which sometimes either mounts things for the file manager only or mounts things in a strange, restricted location.
The SSD is a USB drive but is for photos only. The drive is probably mounted with the desktop environment’s file manger. I simply plugged it in and it was recognized so I thought all was well. Is there a “proper” way to mount it?
OK but if the SSD isn’t mounted correctly wouldn’t that also show up when I installed the down rev Darktable? When I installed 3.8.1 all the files loaded into the Darktable library.
The import seems broken in multiple ways, both in 4.6 and master. I filed a bug report here some weeks ago, another user chimed in. Even though their problem seems to be related to the recursive option. It might or might not be related - noone knows. There are some other reports, too.
For me, neither 4.6 nor master is usable this way. Every workflow starts with importing pictures and this very first step does not work with bug fixes apparently introducing new regressions.
On a side note and slightly off topic: I am not quite sure if the labels in the bugtracker have any meaning. There are “high priority” bugs which do not block you from getting anything done at all and, at times, are just a minor nuisance. And then there is stuff that is broken in both stable and master but seemingly lower priority than getting features in for 4.8 which is due in half a year.
Well, in that bug report you filed, you say in a reply
New input: The issue is not present in 4.6 so this is a regression.
While using development versions usually is fine, there is always a risk of regressions. So for serious work, better stick to stable versions (although those can of course also have bugs).
Such as?
Keep in mind that darktable is written and maintained by unpaid volunteers…
The flatpak should be able to access all files by default,
Sorry but no. I stopped using Gimp flatpak exactly for this. Flatpaks are sandboxed by default, and cannot access files outside of the user’s home directory hierarchy (and a few other irrelevant places), and can’t access the network.
From the page above and from flatpak’s man page, it seems you can now override this with
Well - the import is just broken in other ways for 4.6 than it is for master. Currently the recursive option doesn’t work and there is this weird glitch with removing places from the import dialogue. With a fix presumably introduced in the next bugfix-release, import may be broken in the way I originaly reported. And yes, I believe the recursive option worked at some point I think, so having it broken in a current stable release is unfortunate.
As for your last comment - let’s not go there. I tremendously respect the work that is being done and try to make contributions when and where I can, which limits it to the occasional bug report or forum post once in a blue moon. I just feel that very basic features would be worth keeping in good shape and rock stable or at least free from complete show stoppers. I just now feel reminded of the latest siril release notes (I use and love siril too). There it reads
“List of known bugs: None for the moment, fingers crossed.” Their bugtracker lists issue of course but there seem to be few serious problems - and if there are, they mostly get fixed quickly. And yes, I know, siril is more niche and probably has less users and this comparison is not entirely fair.
For darktable the bugtracker is full with stuff, sometimes breaking, sometimes very long standing. Activity is high but often focused on new stuff (color equalizer for example, which I am looking forward to of course) while I am sitting in front of my laptop with an unusable import or at least a severely crippled one. But yeah…it’s free and I could just learn to fix it myself instead of complaining.
Thank you for all your work. Sincerely. Still I am sad and I feel I (and probably others) have a point.
While darktable can’t access the network by default, it uses a more liberal setting for the local file system, host. There have been a few requests to change it but I always try and say “no.”
Its also unfortunate that nobody tested a caught it before release.
I just feel like if you have things that are that important to you, you should download a nightly before release and test and report bugs. Import is relatively new.
