Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Recursive import does not work anymore since 4.6.0 #16324

Closed
ungive opened this issue Feb 15, 2024 · 3 comments
Closed

Recursive import does not work anymore since 4.6.0 #16324

ungive opened this issue Feb 15, 2024 · 3 comments
Labels
duplicate Fixed in master Has already been fixed in current master branch

Comments

@ungive
Copy link
Contributor

ungive commented Feb 15, 2024

Describe the bug

I have tried using the recursive import feature in Darktable 4.6.0:

grafik

The highlighted folder on the left doesn't have any photos, but the folder "DC-S5" does, the files of which are shown in the list. Clicking import does nothing, except showing "146 photos imported" in the short popup.

This worked before in version 4.4.2 (I tested it with the release exe and a clean config dir on Windows).

Steps to reproduce

  1. Go to import
  2. Select a folder which has subfolders with photos
  3. Select include subdirectories
  4. Import all photos
  5. Observe that no photos were imported

grafik

Expected behavior

Darktable should import the photos

Logfile | Screenshot | Screencast

No response

Commit

No response

Where did you obtain darktable from?

downloaded from www.darktable.org

darktable version

4.6.0

What OS are you using?

Windows

What is the version of your OS?

Windows 10

Describe your system?

No response

Are you using OpenCL GPU in darktable?

None

If yes, what is the GPU card and driver?

No response

Please provide additional context if applicable. You can attach files too, but might need to rename to .txt or .zip

No response

@TurboGit
Copy link
Member

Already reported many times and already fixed.

@ralfbrown ralfbrown added duplicate Fixed in master Has already been fixed in current master branch labels Feb 15, 2024
@ungive
Copy link
Contributor Author

ungive commented Feb 16, 2024

Sorry about the duplicate. I know the workflow, I should have checked archived issues as well as open ones.

But I was surprised to see that a 2 month old release has (imo) somewhat substantial bugs/regressions (this one here and the other one I reported, #16325) that are fixed in master but don't get a follow-up release (like 3.6.1) for people who just download the installer. I can personally build master, but a stable (!) bug-fix release would be a nice thing in my opinion.

I just imagine hearing "fixed in master" doesn't help anyone who doesn't know how to compile darktable or doesn't want to rely on the unstable nightly release.

I apologise if that has been discussed and dismissed before, maybe my suggestion helps though!

@TurboGit

@kmilos
Copy link
Contributor

kmilos commented Feb 16, 2024

But I was surprised to see that a 2 month old release has (imo) somewhat substantial bugs/regressions (this one here and the other one I reported, #16325) that are fixed in master but don't get a follow-up release (like 3.6.1) for people who just download the installer. I can personally build master, but a stable (!) bug-fix release would be a nice thing in my opinion.

You also missed that 4.6.1 bugfix release is/was being prepared: https://github.com/darktable-org/darktable/milestone/32

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
duplicate Fixed in master Has already been fixed in current master branch
Projects
None yet
Development

No branches or pull requests

4 participants