https://bugs.kde.org/show_bug.cgi?id=376359
Bug ID: 376359 Summary: Sort by Image Quality (assign quality tags) ignores many images Product: digikam Version: 5.5.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Maintenance Assignee: [hidden email] Reporter: [hidden email] Target Milestone: --- When I choose to let my images be tagged according to image quality using Digikam's default settings, only very few images are actually tagged. I wonder if this is an expected behaviour? I would expect all images of all albums that I chose in the respective maintenance dialog to be tagged (with the colored flag, meaning "accepted", "pending" or "declined"). But most (>50%) images are not tagged at all. Thanks! -- You are receiving this mail because: You are the assignee for the bug. |
https://bugs.kde.org/show_bug.cgi?id=376359
Mario Frank <[hidden email]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[hidden email] --- Comment #1 from Mario Frank <[hidden email]> --- (In reply to Jens from comment #0) > When I choose to let my images be tagged according to image quality using > Digikam's default settings, only very few images are actually tagged. > > I wonder if this is an expected behaviour? I would expect all images of all > albums that I chose in the respective maintenance dialog to be tagged (with > the colored flag, meaning "accepted", "pending" or "declined"). But most > (>50%) images are not tagged at all. > > Thanks! Hey Jens, I just tested myself. I have 3454 images in my database and ran the maintenance. In fact, all my images are tagged now. I am working on a branch currently. It is possible that it works for me as a side effect due to changes I introduced in the branch. I will signal you when I have merged the branch in our master. Then, you can test again after we have new AppImage bundles or compile it yourself. Cheers, Mario -- You are receiving this mail because: You are the assignee for the bug. |
In reply to this post by bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=376359
--- Comment #2 from Jens <[hidden email]> --- great, thank you! -- You are receiving this mail because: You are the assignee for the bug. |
In reply to this post by bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=376359
--- Comment #3 from Mario Frank <[hidden email]> --- (In reply to Jens from comment #2) > great, thank you! Jens, I merged the branch into master. But we will have to wait for the AppImage. I remember Gilles writing somewhere that this will probably not be done before next week. So, you will have to wait for the AppImage or, if you can, compile the current master branch state on your system. Just to warn you, the exiv version used in most linux distros is 0.25 which has many bugs. 0.26 resolves over 200 bugs but is sadly not yet released. Some of the bugs in 0.25 lead to crashes. Thats one reason why we use AppImages. There we have a stable basis. -- You are receiving this mail because: You are the assignee for the bug. |
In reply to this post by bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=376359
[hidden email] changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[hidden email] --- Comment #4 from [hidden email] --- Yes, i come back at home this week end. I will start AppImage computation while the night. They will be available next Monday. Gilles -- You are receiving this mail because: You are the assignee for the bug. |
In reply to this post by bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=376359
--- Comment #5 from Mario Frank <[hidden email]> --- So, here are the AppImages: https://drive.google.com/drive/folders/0BzeiVr-byqt5Y0tIRWVWelRJenM -- You are receiving this mail because: You are the assignee for the bug. |
Free forum by Nabble | Edit this page |