*** If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** SUMMARY After installing the pre-relase built on 20-05-2024 07:25, face tagging crashes digiKam. The name seems to be applied to the metadata before crashing. STEPS TO REPRODUCE 1. Start digikam 2. Open an image with a face recognized 3. Click "Who is this" and start typing the initial letter 4. Select the name in the dropdown list 5. Wait a couple of seconds, and digiKam crashes. OBSERVED RESULT digiKam crashesm EXPECTED RESULT Apply the selected name and do not crash SOFTWARE/OS VERSIONS Windows: 11 macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION See attached video
Yes, I can reproduce. Maik
Git commit 55f1a5e36bd450388b1b172f136057b83b53ee9b by Maik Qualmann. Committed on 22/05/2024 at 19:50. Pushed by mqualmann into branch 'master'. use QStandardItemModel without parent M +5 -22 core/libs/tags/engine/tagscompleter.cpp https://invent.kde.org/graphics/digikam/-/commit/55f1a5e36bd450388b1b172f136057b83b53ee9b
This is the backtrace from the crash. I'm surprised that line 390 differs from the current code by 2 lines, even if I take the change from a week ago into account. By the way, it doesn't crash in Linux. Gilles, can you create a new Windows bundle? Qt6Widgets.dll!00007ffa2fde306a() Unbekannt digikamgui.dll!Digikam::AbstractAlbumTreeView::setCurrentAlbums(const QList<Digikam::Album *> & albums, bool selectInAlbumManager) Zeile 390 C++ digikamgui.dll!Digikam::AddTagsComboBox::setCurrentTag(Digikam::TAlbum * const album) Zeile 118 C++ digikamgui.dll!Digikam::AssignNameWidget::Private::setAddTagsWidgetContents<Digikam::AddTagsComboBox>(Digikam::AddTagsComboBox * const widget) Zeile 515 C++ digikamgui.dll!Digikam::AssignNameWidget::Private::updateContents() Zeile 535 C++ digikamgui.dll!Digikam::AssignNameWidget::setCurrentTag(Digikam::TAlbum * album) Zeile 245 C++ digikamgui.dll!Digikam::FaceItem::setFace(const Digikam::FaceTagsIface & face) Zeile 39 C++ digikamgui.dll!Digikam::FaceGroup::slotAssigned(const Digikam::TaggingAction & action, const Digikam::ItemInfo & __formal, const QVariant & faceIdentifier) Zeile 485 C++ Maik
Ok, mistake, the line fits, it would be the QTreeView::model() call that leads to a crash. Maik
yes, i will build the Windows installer in few hours. Gilles
Git commit db243911435c1230e0e1b9432358bcdbedf2c708 by Maik Qualmann. Committed on 23/05/2024 at 20:38. Pushed by mqualmann into branch 'master'. try to fix crash in the AbstractAlbumTreeView M +1 -1 core/utilities/facemanagement/items/facegroup.cpp M +30 -12 core/utilities/facemanagement/widgets/assignnamewidget_p.cpp https://invent.kde.org/graphics/digikam/-/commit/db243911435c1230e0e1b9432358bcdbedf2c708
*** Bug 487668 has been marked as a duplicate of this bug. ***
I'm working on the crash, but it only affects the Windows version and is strange. It crashes in the TagTreeView of the Face Name ComboBox. What is strange is that, unlike Linux, the TagTreeView does not have a root tag and no child tags are displayed. The backtraces shows that it crashes at different points in the function AbstractAlbumTreeView::setCurrentAlbums(), while the TagTreeView is in destruction. When I debug Linux the order is fine and the TagTreeView is definitely not in decustruction during this. Gilles, would it be possible to check out a digiKam version from the beginning of May with the current Qt-6.7.0 build system of Windows? To check if the problem is related to Qt-6.7.0 or if code that was changed is causing this problem? Maik
>Gilles, would it be possible to check out a digiKam version from the beginning of May with the current Qt-6.7.0 build system of Windows? >To check if the problem is related to Qt-6.7.0 or if code that was changed is causing this problem? yes sure. I can use a git revision on the script. Let's me her the right revision to checkout. This can be customized here: https://invent.kde.org/graphics/digikam/-/blob/master/project/bundles/vcpkg/config.sh?ref_type=heads#L72 Gillles
This can be also a side effect of my C++17 commits. Typicality my change uses the pre-init in declaration, instead the contructors init. Possible side effect of my changes is the equality operator init used instead the constructor. for ex the ThumbnailSize class need the constructor to be initialized with an integer value. I also dropped the class init with empty argument constructor, as it used by default (normally). Gilles
Can we git revision 7d64840905ba968de186a9f30bc3ccff64c89224 use this with Qt-6.6.1 from May 12th has a TagTreeView that is ok and doesn't crash. The first version from May 19th with Qt-6.7.0 has the problem. I patch the config.sh Maik
Git commit 7502fc251e20b56b614056def8d3c787e6ad690b by Maik Qualmann. Committed on 28/05/2024 at 10:35. Pushed by mqualmann into branch 'master'. use older git version for test the Windows bundle M +1 -1 project/bundles/vcpkg/config.sh https://invent.kde.org/graphics/digikam/-/commit/7502fc251e20b56b614056def8d3c787e6ad690b
Ok i will start the build this evening at home... Gilles
Git commit 2db9b452ae638478b6f0932f53f05bce257f3d86 by Maik Qualmann. Committed on 28/05/2024 at 21:08. Pushed by mqualmann into branch 'master'. add two directly called but non-existent functions M +10 -0 core/libs/album/treeview/abstractcheckablealbumtreeview.cpp M +3 -0 core/libs/album/treeview/abstractcheckablealbumtreeview.h M +1 -1 project/bundles/vcpkg/config.sh https://invent.kde.org/graphics/digikam/-/commit/2db9b452ae638478b6f0932f53f05bce257f3d86
Gilles, can you please create a new master bundle? Because of C++20 and boost, the version from May 12th would not have been compilable. Maik
Hi Maik, Note : The build with an older revision and Qt 6.7.0 under Windows pass, this is not a problem. The build with your last commits is under progress. I hope that upload will work as expected (i'm not at home today). Many times, rsync from MSYS2 close the connection socket, and i don't know why. I write a "try again" loop in the script in this case, but it's do not improve well the situation. I think the rsync Windows port is not perfect. Using a native CLI alternative to rsync under Windows is the hell... Gilles
Hi Maik, The Windows installer is now up-to-date... Gilles
Git commit b2c31840d3dfecb60b44f319b1761bf2c4611a3b by Maik Qualmann. Committed on 29/05/2024 at 18:57. Pushed by mqualmann into branch 'master'. for testing revert the only change in the period in May M +4 -0 core/libs/album/treeview/albumtreeview.cpp M +1 -1 core/libs/album/treeview/albumtreeview.h M +4 -0 core/libs/album/treeview/searchtreeview.cpp M +1 -1 core/libs/album/treeview/searchtreeview.h M +4 -0 core/libs/album/treeview/tagtreeview.cpp M +1 -1 core/libs/album/treeview/tagtreeview.h https://invent.kde.org/graphics/digikam/-/commit/b2c31840d3dfecb60b44f319b1761bf2c4611a3b
Git commit 07441133cd1e6ab04357772f4af07248e59c0bbd by Maik Qualmann. Committed on 30/05/2024 at 06:22. Pushed by mqualmann into branch 'master'. Revert "for testing revert the only change in the period in May" M +0 -4 core/libs/album/treeview/albumtreeview.cpp M +1 -1 core/libs/album/treeview/albumtreeview.h M +0 -4 core/libs/album/treeview/searchtreeview.cpp M +1 -1 core/libs/album/treeview/searchtreeview.h M +0 -4 core/libs/album/treeview/tagtreeview.cpp M +1 -1 core/libs/album/treeview/tagtreeview.h https://invent.kde.org/graphics/digikam/-/commit/07441133cd1e6ab04357772f4af07248e59c0bbd
Git commit ef24babde204def0435bbdba7e3c5db9eb4c2972 by Maik Qualmann. Committed on 30/05/2024 at 06:27. Pushed by mqualmann into branch 'master'. this is the last relevant change in the period May M +2 -1 core/libs/album/widgets/albumselectcombobox.cpp M +1 -1 core/libs/album/widgets/albumselectcombobox.h https://invent.kde.org/graphics/digikam/-/commit/ef24babde204def0435bbdba7e3c5db9eb4c2972
Hi, Ok next build will arrive this evening. Gilles
Git commit 1f801a41503c916b5f8b50847ef15ccc00167924 by Maik Qualmann. Committed on 30/05/2024 at 18:44. Pushed by mqualmann into branch 'master'. Revert "this is the last relevant change in the period May" M +1 -2 core/libs/album/widgets/albumselectcombobox.cpp M +1 -1 core/libs/album/widgets/albumselectcombobox.h https://invent.kde.org/graphics/digikam/-/commit/1f801a41503c916b5f8b50847ef15ccc00167924
Hi Maik, This Windows build is restarted just now including your last changes... Gilles
Hi Gilles, this was a revert. I'm lost at the moment, can we build the corresponding commit number that still worked with Qt-6.6.1 to really rule out code changes in digiKam? Maik
yes sure...
Git commit 2888c174b8b66f4a6091e9eb7487fe63ebd1b8e7 by Gilles Caulier. Committed on 30/05/2024 at 19:44. Pushed by cgilles into branch 'master'. switch Windows build to rev 7d64840905ba968de186a9f30bc3ccff64c89224 M +2 -2 project/bundles/vcpkg/config.sh https://invent.kde.org/graphics/digikam/-/commit/2888c174b8b66f4a6091e9eb7487fe63ebd1b8e7
Gilles, I think this could be the Qt bug, only Qt-6.7.0 is affected and with style changes. We change the style of the ComboBox. https://bugreports.qt.io/browse/QTBUG-124191 Maik
Hum very possible. In all case, you have right and i'm wrong. the anterior git rev do not compile with Qt 6.7 with boost based classes : E:\b\dktemp\digikam-master\core\libs\database\history\itemhistorygraphmodel.cpp(508,17): error C2666: 'Digikam::Graph<Digikam::HistoryVertexProperties,Digikam::HistoryEdgeProperties>::Vertex::operator ==': overloaded functions have similar conversions [E:\b\dktemp\digikam-master\build\core\libs\database\digikamdatabase_obj.vcxproj] E:\b\dktemp\digikam-master\core\libs\database\history\itemhistorygraph_boost.h(201,14): could be 'bool Digikam::Graph<Digikam::HistoryVertexProperties,Digikam::HistoryEdgeProperties>::Vertex::operator ==(const unsigned __int64 &) const' [rewritten expression '!(x == y)'] E:\b\dktemp\digikam-master\core\libs\database\history\itemhistorygraph_boost.h(201,14): or 'bool Digikam::Graph<Digikam::HistoryVertexProperties,Digikam::HistoryEdgeProperties>::Vertex::operator ==(const unsigned __int64 &) const' [synthesized expression '!(y == x)'] E:\b\dktemp\digikam-master\core\libs\database\history\itemhistorygraphmodel.cpp(508,17): or 'built-in C++ operator!=(unsigned __int64, unsigned __int64)' E:\b\dktemp\digikam-master\core\libs\database\history\itemhistorygraphmodel.cpp(508,17): while trying to match the argument list '(const Digikam::Graph<Digikam::HistoryVertexProperties,Digikam::HistoryEdgeProperties>::Vertex, Digikam::Graph<Digikam::HistoryVertexProperties,Digikam::HistoryEdgeProperties>::Vertex)' E:\b\dktemp\digikam-master\core\libs\database\history\itemhistorygraphmodel.cpp(547,14): error C2666: 'Digikam::Graph<Digikam::HistoryVertexProperties,Digikam::HistoryEdgeProperties>::Vertex::operator ==': overloaded functions have similar conversions [E:\b\dktemp\digikam-master\build\core\libs\database\digikamdatabase_obj.vcxproj] E:\b\dktemp\digikam-master\core\libs\database\history\itemhistorygraph_boost.h(201,14): could be 'bool Digikam::Graph<Digikam::HistoryVertexProperties,Digikam::HistoryEdgeProperties>::Vertex::operator ==(const unsigned __int64 &) const' E:\b\dktemp\digikam-master\core\libs\database\history\itemhistorygraph_boost.h(201,14): or 'bool Digikam::Graph<Digikam::HistoryVertexProperties,Digikam::HistoryEdgeProperties>::Vertex::operator ==(const unsigned __int64 &) const' [synthesized expression 'y == x'] E:\b\dktemp\digikam-master\core\libs\database\history\itemhistorygraphmodel.cpp(547,14): or 'built-in C++ operator==(unsigned __int64, unsigned __int64)' E:\b\dktemp\digikam-master\core\libs\database\history\itemhistorygraphmodel.cpp(547,14): while trying to match the argument list '(const Digikam::Graph<Digikam::HistoryVertexProperties,Digikam::HistoryEdgeProperties>::Vertex, const Digikam::Graph<Digikam::HistoryVertexProperties,Digikam::HistoryEdgeProperties>::Vertex)' Gilles
Ok, back to master. I'm thinking of a workaround up to Qt-6.7.1. Maik
Git commit 476c2591229145431e1f374dd3e353eff552df17 by Maik Qualmann. Committed on 30/05/2024 at 20:57. Pushed by mqualmann into branch 'master'. not apply style changes to QComboBox on Windows and Qt-6.7.0 M +6 -0 core/utilities/facemanagement/widgets/assignnamewidget_p.cpp M +1 -0 core/utilities/facemanagement/widgets/assignnamewidget_p.h https://invent.kde.org/graphics/digikam/-/commit/476c2591229145431e1f374dd3e353eff552df17
Git commit 55103429ef282047ca89b016a283f7b149df339c by Maik Qualmann. Committed on 30/05/2024 at 20:59. Pushed by mqualmann into branch 'master'. Revert "switch Windows build to rev 7d64840905ba968de186a9f30bc3ccff64c89224" M +2 -2 project/bundles/vcpkg/config.sh https://invent.kde.org/graphics/digikam/-/commit/55103429ef282047ca89b016a283f7b149df339c
The ComboBox with tree view works again and there are no more crashes. I will do another test where we only suppress the style of the ComboBox. Maik
Git commit 1ecb551c1ab64379afb287485a200557f38a634a by Maik Qualmann. Committed on 31/05/2024 at 06:01. Pushed by mqualmann into branch 'master'. no style changes only to the ComboBox M +4 -6 core/utilities/facemanagement/widgets/assignnamewidget_p.cpp https://invent.kde.org/graphics/digikam/-/commit/1ecb551c1ab64379afb287485a200557f38a634a
ok, and next build will done later 5PM Paris time
With this bug, the developers of Qt really didn't think until the end. Deleting the QComboBox at style changes and re-create would not work with a standard QComboBox, since signal/slots connections are lost. Now it is also clear to me why our connections to the QComboBox were dead. Maik
Git commit 0d7796db2e28940523533cb507e318247916f069 by Maik Qualmann. Committed on 31/05/2024 at 18:43. Pushed by mqualmann into branch 'master'. Revert "no style changes only to the ComboBox" We are not allowed to make any style changes to the widget, this will cause an error in the QComboBox. Until Qt-6.7.1 we have to live with face name labels without a background color. Related: bug 487668 FIXED-IN: 8.4.0 M +6 -4 core/utilities/facemanagement/widgets/assignnamewidget_p.cpp https://invent.kde.org/graphics/digikam/-/commit/0d7796db2e28940523533cb507e318247916f069
Bonjour, Sur mon pc, le bug n'est pas corriger. Même symptôme sur les deux dernières mise a jour ... Le 31/05/2024 à 20:44, Maik Qualmann a écrit : > https://bugs.kde.org/show_bug.cgi?id=487370 > > Maik Qualmann <metzpinguin@gmail.com> changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > Resolution|--- |FIXED > Latest Commit| |https://invent.kde.org/grap > | |hics/digikam/-/commit/0d779 > | |6db2e28940523533cb507e31824 > | |7916f069 > Version Fixed In| |8.4.0 > Status|CONFIRMED |RESOLVED > > --- Comment #36 from Maik Qualmann <metzpinguin@gmail.com> --- > Git commit 0d7796db2e28940523533cb507e318247916f069 by Maik Qualmann. > Committed on 31/05/2024 at 18:43. > Pushed by mqualmann into branch 'master'. > > Revert "no style changes only to the ComboBox" > We are not allowed to make any style changes to the widget, this > will cause an error in the QComboBox. Until Qt-6.7.1 we have to > live with face name labels without a background color. > Related: bug 487668 > FIXED-IN: 8.4.0 > > M +6 -4 core/utilities/facemanagement/widgets/assignnamewidget_p.cpp > > https://invent.kde.org/graphics/digikam/-/commit/0d7796db2e28940523533cb507e318247916f069 >
The problem will be fixed with the next test version. Maik
Created attachment 170114 [details] image.png I can confirm that it now works again without problems. Build date 03.06.2024 09:30, revision 91733345c80b9ce768646bb29eaee8fbcfca38f7 However a change has been made that makes it very hard/ almost impossible to read the names in the images - seems like both the text color and transparency has been changed. Shall I report this as a new issue? Here's a screenshot: [image: image.png] As you can see, hard to read daughters name Hanne Hoem Olsen (on the left), almost impossible to read my fathers name Rolf Tore Hoem (on the right). Thank you, Bjørn Tore fre. 31. mai 2024 kl. 23:34 skrev Maik Qualmann <bugzilla_noreply@kde.org>: > https://bugs.kde.org/show_bug.cgi?id=487370 > > --- Comment #38 from Maik Qualmann <metzpinguin@gmail.com> --- > The problem will be fixed with the next test version. > > Maik > > -- > You are receiving this mail because: > You reported the bug.
I just made a change so that at least the face names are shown with a background again, it should be in the next build for tomorrow. We can't really do much here, it's a bug in Qt-6.7.0. It will be fixed with the next version Qt-6.7.1, when it is available to us in VCPKG it will be back to normal. Maik
Created attachment 170128 [details] attachment-2989090-0.html Effectuer un nouveau signalement pour ce bug. MErci à vous Le 03/06/2024 à 20:49, Bjørn Tore Hoem a écrit : > I can confirm that it now works again without problems. Build date > 03.06.2024 09:30, revision 91733345c80b9ce768646bb29eaee8fbcfca38f7 > However a change has been made that makes it very hard/ almost impossible > to read the names in the images - seems like both the text color and > transparency has been changed. > > Shall I report this as a new issue? > > Here's a screenshot: > [image: image.png] > > As you can see, hard to read daughters name Hanne Hoem Olsen (on the left), > almost impossible to read my fathers name Rolf Tore Hoem (on the right). > > Thank you, > > Bjørn Tore
Nommer les visage fonctionne mais un soucis persiste est que digikam se ferme automatiquement et devant etre redémarrer à chaque fois après avoir nommer un visage. Les noms sont correctement enregistrés après avoir redémarrer. Dans la version 8.3 fonctionne. Pourquoi avoir changé dans 8.4 ? Avez vous fait la part des choses ? Es ce un bon choix ? Depuis ce changement depuis maintenant une quinzaine de jours sans parvenir à résoudre le bug. Je comprends un logiciel n'est jamais parfait. J'ai l'impression que vous tourner en rond ... Vous avez probablement fait ce choix actuel es ce le meilleur ? Je vous dit franchement, cela commence à me gavé. Digikam est bien mais il est très complexe et de ce fait, cela demande des connaissances très importantes pour le développement et pour l'utilisateur. Pour résoudre un bug cela pourrai devenir fastidieux voir impossible. C'est comme tout, il y a des limites en évitant de les franchir sous peine de payer le prix. Toutefois, je tiens à vous féliciter pour le travail effectué. Bravo! J'espère que je vous ai pas froissé et si non je suis désolé. Denis. Envoyé depuis l'application Mail Orange ---------------- De : Maik Qualmann <bugzilla_noreply@kde.org> Envoyé : lundi 03 juin 2024 21:05 À : colmar68.denis60@orange.fr Objet : [digikam] [Bug 487370] Face Recognition crashes - pre-release built on 20-05-2024 07:25 https://bugs.kde.org/show_bug.cgi?id=487370 --- Comment #40 from Maik Qualmann <metzpinguin@gmail.com> --- I just made a change so that at least the face names are shown with a background again, it should be in the next build for tomorrow. We can't really do much here, it's a bug in Qt-6.7.0. It will be fixed with the next version Qt-6.7.1, when it is available to us in VCPKG it will be back to normal. Maik
Hi Denis, As your message is in French i continue in this language to be clear. Ce n'est pas un changement dans notre code mais un changement dans le framework Qt. Sous Windows nous sommes passé de la 6.6.1 à la 6.7.0 pour intégrer un grande quantité de correction de bogues. Le bogue qui nous concerne est dans Qt et uniquement sous Windows avec Qt6. Donc la complexité et de trouver le bon palliatif dans le code de digiKam tout en tenant compte des différentes versions de Qt et des autres architectures. C'est que qu'essaye de faire Maik actuellement. Ca prend du temps, du repackaging, des tests. Il faut être patient et tolérant, ou alors payer un logiciel propriétaire et se taire.... Cordialement Gilles Caulier
I would also like to point out that the latest digiKam-8.4.0 version does not crash when entering a name. Please test it from here: https://files.kde.org/digikam/ Maik
Je vais avec grand plaisir me taire éternellement ! 🙂 J'ai pas besoin de logiciel remplis de bogues, des développeurs incompétent. Attendre, attendre et toujours attendre dans l’hypothèse d'une éventuelle correction .... 😂😂 Aucune écoute. Vos soucis de framework, de qt6 etc c'est pas mon problème. je m'en contre fiche totalement. 😕 Pourquoi faire simple, lorsqu'on peut faire compliquer. Pourquoi changer quelque qui fonctionne pour quelque qui ne fonctionne pas, c'est plus rigolos. Il faut changer pour quelque chose qui fonctionne mieux et non l'inverse. ,C'est chose faite, je vous laisse dans votre mascarade😛. Aillant effectuer plusieurs test sur différents logiciels et j'ai fais mon choix. Pour moi, le prix n'est absolument pas un problème et toutes manières cela n'ira jamais en améliorant ici, je préfère payer pour avoir un logiciel qui bug pas ou peu et d'un meilleur service de mise à jour (qui corrige vraiment ...). 😬. Je vous rassure, vous m'entendrez plus😂. Bon débarras. Je sais pas pourquoi et comment pour avoir choisit d'un telle logiciel, je m'en mords les doigts! 😂 Vous avez réussi a répondre en français ... quelle événement. C'est bien la première fois. Comme quoi en disant la vérité sa blesse.🙂 Maintenant, prenez la chose comme vous vous voulez, je m'en fou, je quitte le navire avec une extrême jouissance.🤐 J'ai hâte de la réponse ... s'il y a ? 😛😛😛 😂😂😂 L.e 05/06/2024 à 08:27, bugzilla_noreply@kde.org a écrit : > https://bugs.kde.org/show_bug.cgi?id=487370 > > --- Comment #43 from caulier.gilles@gmail.com --- > Hi Denis, > > As your message is in French i continue in this language to be clear. > > Ce n'est pas un changement dans notre code mais un changement dans le framework > Qt. Sous Windows nous sommes passé de la 6.6.1 à la 6.7.0 pour intégrer un > grande quantité de correction de bogues. Le bogue qui nous concerne est dans Qt > et uniquement sous Windows avec Qt6. Donc la complexité et de trouver le bon > palliatif dans le code de digiKam tout en tenant compte des différentes > versions de Qt et des autres architectures. C'est que qu'essaye de faire Maik > actuellement. Ca prend du temps, du repackaging, des tests. Il faut être > patient et tolérant, ou alors payer un logiciel propriétaire et se taire.... > > Cordialement > > Gilles Caulier >
Created attachment 170159 [details] attachment-3112200-0.html j'ai installer la toute dernière version 8.4 en date du 4 juin Le 05/06/2024 à 08:41, Maik Qualmann a écrit : > I would also like to point out that the latest digiKam-8.4.0 version does not > crash when entering a name. Please test it from here:
Under Windows 11, the problem will probably only be fixed with the next Qt version... We will have to wait until Qt-6.7.1 is available, until then digiKam-8.3.0 is the stable release. Maik
Created attachment 170160 [details] attachment-3114864-0.html Hi Maik - I have tested the new build and can confirm that facenames are shown with background again. However, this build introduces a new problem. If you remove an existing name tag with a name, it crashes. See this video: https://photos.app.goo.gl/UZnrRDJtK97aN9oK7 Thank you for looking into this:-) Bjørn Tore man. 3. juni 2024 kl. 21:05 skrev Maik Qualmann <bugzilla_noreply@kde.org>: > https://bugs.kde.org/show_bug.cgi?id=487370 > > --- Comment #40 from Maik Qualmann <metzpinguin@gmail.com> --- > I just made a change so that at least the face names are shown with a > background again, it should be in the next build for tomorrow. > > We can't really do much here, it's a bug in Qt-6.7.0. It will be fixed > with the > next version Qt-6.7.1, when it is available to us in VCPKG it will be back > to > normal. > > Maik > > -- > You are receiving this mail because: > You reported the bug.
Git commit f0d3008d4d6360e00c3fdd0385259fb61effa55b by Maik Qualmann. Committed on 05/06/2024 at 10:19. Pushed by mqualmann into branch 'master'. Revert "try to apply style only to face name label" M +2 -5 core/utilities/facemanagement/widgets/assignnamewidget_p.cpp https://invent.kde.org/graphics/digikam/-/commit/f0d3008d4d6360e00c3fdd0385259fb61effa55b
Git commit d295b9095d3885e4e7190e07cf9d95925beb3da2 by Maik Qualmann. Committed on 21/06/2024 at 19:08. Pushed by mqualmann into branch 'master'. no workaround needed anymore with Qt-6.7.2 Related: bug 487668 FIXED-IN: 8.4.0 M +2 -2 NEWS M +0 -6 core/utilities/facemanagement/widgets/assignnamewidget_p.cpp M +0 -1 core/utilities/facemanagement/widgets/assignnamewidget_p.h https://invent.kde.org/graphics/digikam/-/commit/d295b9095d3885e4e7190e07cf9d95925beb3da2