Created attachment 119508 [details] a screenshot of the bug Edit Metadata dialog has 4 "Undefined" entries on the Light source dropdown list STEPS TO REPRODUCE 1. Choose Layer - Edit Metadata - Exif - Postprogressing 2. Click on "Light source" dropdown list. SOFTWARE/OS VERSIONS Krita Version: 4.2.0-pre-alpha Languages: en Hidpi: true Qt Version (compiled): 5.9.5 Version (loaded): 5.9.5 OS Information Build ABI: x86_64-little_endian-lp64 Build CPU: x86_64 CPU: x86_64 Kernel Type: linux Kernel Version: 4.15.0-48-lowlatency Pretty Productname: Ubuntu 18.04.2 LTS Product Type: ubuntu Product Version: 18.04 Hardware Information GPU Acceleration: auto Memory: 15923 Mb Number of Cores: 8 Swap Location: /tmp
Can you attach the image with which this happens? The entries are dependent on what's part of the metadata inside the image.
Created attachment 119616 [details] test file I have tested on this file. Even if you test on a new file, there are 4 "Undefined" entries on the Light Source drop-down list.
Thanks for your comment! Automatically switching the status of this bug to REPORTED so that the KDE team knows that the bug is ready to get confirmed. In the future you may also do this yourself when providing needed information.
Hm... Okay, so this is actually hard-coded in exif.ui. I don't know why, and the original author has long since left the project. It's always been this way, from the very beginning so I assume it's because the number of options has to conform to some kind of schema document. I'm not going to touch this, sorry. It'll have to wait until someone with lots of knowledge of and deep interest in metadata comes along.
Okay, it's actually correct... As I should have expected. https://www.awaresystems.be/imaging/tiff/tifftags/privateifd/exif/lightsource.html shows the exif light source values. As you can see, there are gaps in the numbering. A combobox cannot have those gaps, so Cyrille inserted Undefined entries where necessary. So this was certainly intentional and while weird, it's not a bug.
*** Bug 410343 has been marked as a duplicate of this bug. ***