https://bugs.kde.org/show_bug.cgi?id=473430
--- Comment #7 from Vince Dugar <vince.du...@gmail.com> --- Thank you Maik, So I just learned something -- that I can't rely on 'apt install' to get the latest version of xyz! I'd think that would be administered... I'll make another attempt to install (8.2.0) and see what happens. That version running on my Windows PC seems to be working fine. PS -- I did do the export statement (and installed gdb -- with apt) -- just not sure if the backtrace needed to be "refreshed" by causing the error again. AND, I just figured out that I was probably in a different shell than where I ran the export! Retired but still learning, Vince On Wed, Aug 16, 2023 at 1:46 AM Maik Qualmann <bugzilla_nore...@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=473430 > > --- Comment #6 from Maik Qualmann <metzping...@gmail.com> --- > At the moment I just wanted to see the debug output in the terminal, which > is > activated with the command before you start digiKam: > > export QT_LOGGING_RULES="digikam*=true" > > But I can see from your GDB backtrace that it is not digiKam-7.10, but > digiKam-7.1.0. This version is 3 years old! > I think it doesn't make sense for us to debug such an old version, it would > also have to be related to Exiv2, since that library changes the files when > tagging. > > Try our latest digiKam-8.2.0 AppImage to see if the problem can be > reproduced. > > https://files.kde.org/digikam/ > > Maik > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
