Images imported via command line disappear from lighttable

[dtorop]

Is there an existing issue for this?

• I checked and did not find my issue in the already reported ones

Describe the bug

On a clean install, images imported via command line parameters are not visible in lighttable view. If a folder of images is specified on the command line, the images initially appear, but opening an image in darkroom view makes it disappear on return the lightable view. If individual images files are specified on the command line, they are not visible in lighttable at all. In either case, resetting the "collection filters" module makes all the imported images visible.

Steps to reproduce

1. Start a clean install of darktable with a command line parameter of a folder of images
2. Verify that these images are imported and visible in lighttable view
3. Double-click on an image to bring it into darkroom view
4. Type l to return to lighttable view
5. Verify that the image is no longer visible
6. As you wish, repeat steps 3 and 4 with other images and note that they disappear
7. Click the reset button on the "collection filters" module
8. Verify that the image is now visible
9. Repeat steps 3 and 4 with images and note that they now no longer disappear

If one only performs steps 1-6 (and does not reset the "collection filters" module), one can produce further trouble by:

1. Quit then restart darktable
2. Note that no images are visible in the filemanager
3. Reset the "collection filters" module
4. Note that all imported images are now visible

Furthermore: If one specifies the image paths on the command line rather than an image folder, darktable will start with no images visible in lighttable. Again, resetting the "collection filters" module will make the imported images visible.

Expected behavior

Imported images should be visible in lighttable and not disappear when they are opened in the darkroom view.

Logfile | Screenshot | Screencast

No response

Commit

No response

Where did you obtain darktable from?

self compiled

darktable version

5.1.0+2073~g161c75be3e

What OS are you using?

Linux

What is the version of your OS?

Debian forky/sid

Describe your system

Wayland 1.47, Plasma/KWin 6.5.4, GTK 2.24.33, 32GB RAM, 1920x1080 display

Are you using OpenCL GPU in darktable?

Yes

If yes, what is the GPU card and driver?

GeForce RTX 3080 Mobile, 8GB, nvidia driver 550.163.01

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

I've noticed this behavior since at least last summer, but haven't been able to replicate until now. I also observed something similar in someone using darktable 5.2.1 on MacOS.

I've tested this using a range of raw images from Fujifilm, Canon, and Nikon cameras.

Starting a fresh install of darktable with no image names on the command line, then importing the images, does not result in this behavior.

[ralfbrown]

That's a known problem which has been around for a coupla versions (it's likely that the previous report has been auto-closed due to a year's inactivity).

There's an unitialized value somewhere in the collection filters, and you found the known workaround (doing a module reset forces initialization).

[dtorop]

That's a known problem which has been around for a coupla versions (it's likely that the previous report has been auto-closed due to a year's inactivity).

Thank you, good to know! I couldn't find it in the old bug reports.

There's an unitialized value somewhere in the collection filters, and you found the known workaround (doing a module reset forces initialization).

Makes sense. I think it's worth hunting down, as this could particularly lose new users to darktable. A typical workflow would be to open darktable for the first time by dragging images or a folder into its desktop icon, which could trigger this.

As time allows I'll look for this bug...

[dtorop]

After opening darktable with a clean config and exiting, darktablerc has these values set:

plugins/lighttable/filtering/sortorder0=
plugins/lighttable/filtering/string0=%
plugins/lighttable/filtering/string2=%%

After resetting the collection filters module and exiting darktable, these values change to:

plugins/lighttable/filtering/sortorder0=0
plugins/lighttable/filtering/string0=
plugins/lighttable/filtering/string2=

It appears that, in particular, no images appear when:

plugins/lighttable/filtering/string0=%

But images appear when:

plugins/lighttable/filtering/string0=

I'll look into this a bit more.