Bug 517624 - Filtering on rating (stars 0-5) not working correct
Summary: Filtering on rating (stars 0-5) not working correct
Status: RESOLVED FIXED
Alias: None
Product: digikam
Classification: Applications
Component: Albums-Filters (other bugs)
Version First Reported In: 9.0.0
Platform: Other Other
: NOR normal
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2026-03-15 20:35 UTC by verweis-buergerin-0o
Modified: 2026-03-15 20:36 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed/Implemented In: 9.1.0
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description verweis-buergerin-0o 2026-03-15 20:35:04 UTC
Hi,
I understand the filter function was reworked a bit in 9.0.0. But for me it seems that filtering in an album for images having a rating is not working correctly anymore.
I noticed this behaviour in 9.0.0 in a windows and linux environment.

I have an album with image mixed with no rating, 4 star and 5 star rating. For example I want to see only images that acutally have a rating, I open the filter sidebar and in properties I click on a star. The filter condition is set to "greater or equal". The expected behaviour should be to display all images that have a rating so my 4-star and 5-star images. Thats how it works before 9.0.0.
But now acutally nothing is happening. I can change the filter to two, three, four, five stars - nothing happens.
I still see all images, even the ones without rating at all. When I change the condition now to "equal", the filter is working and no image is displayed just as expected. 
When I now change back to "greater or equal", suddenly I see only the images having a rating. So now the filter is working... 

I hope this was somehow understandable. For me I can reproduce the behaviour on different systems regardless if the images had a rating or if gave them a new rating. The filter is not working.

Thanks for looking into this.
Comment 1 Maik Qualmann 2026-03-15 20:36:58 UTC
Fixed with Bug 517420

Maik