A lot of skulls in lighttable after using today's source code

Software darktable
1

I run Fedora 40 XFCE and build DT from source code, master branch. Today after getting latest, rebuilding and installing I started to get a lot of skulls in lighttable for recently edited images.

I tried to reimport images - did not help.

I ran darktable-generate-cache - did not help

Removed all cached thumbnails: rm ~/.cache/darktable/mipmaps-a9c71d470aa428794c88847aee59ad52bdc8f4ab.d/* - did not help

Removed build directory, recreated it, rebuilt and installed - did not help.

Renamed ~/.config/darktable and started anew - did not help.

It looks the skulls are created for processed images only. The ones without processing done on them are displayed normally.

BTW if I switch to branch darktable-4.8.x then no more skulls, so it looks like recent code changes in the master branch.

What else can I do? Is it just me or the issue happened to somebody else too?

2

I was expecting rowboats of some kind (https://en.wikipedia.org/wiki/Sculling) … but on realising you meant skulls, sorry, no insight for you :frowning:

3

I run nightlies but do not build them myself. The last build available on GitHub is 3 days old. Nightly autobuilds normally happen every 24 hours like clockwork. My guess is their CI/CD pipeline is failing regression testing and you built broken code

4

If you run into an issue with master, you should first look at GitHub issues. If you can reproduce, you should report it.

This one is already reported: Git master : darktable action gives death skull icon in lighttable : import of tiff gives death skull in lighttable : two issues · Issue #17536 · darktable-org/darktable · GitHub

2 Likes
5

The CI is running and it is successful for linux and windows. It is failing during the DMG creation for mac.

1 Like
6

Thanks, learned a new word today :slight_smile:

1 Like
7

@g-man I pinpointed the problem to this commit:

7dc0faf4652f8ed856702634634b90f4807dd6ec

Should I create a new issue on GitHub or add my comments to the one you linked above?

Steps to reproduce:

Remove a particular collection.
Add it back using “add to library”.
Previously processed images will be displayed as skulls in lighttable.

No skulls if I build with commits before the one above.

1 Like
8

If you’re sure it’s the same issue, add the comments to the existing thread. That makes it easier for the devs to keep track of the issue, with all info in one place.

1 Like
9

This was my fault. A pull request is ready to fix this.

10

The offending commit was reverted by @Pascal_Obry , after rebuilt no more skulls.

1 Like