https://bugs.kde.org/show_bug.cgi?id=473430
--- Comment #13 from Vince Dugar <vince.du...@gmail.com> --- Looking better now. After making the ExifTool changes below (running on my chromebook), I can write tags to images without causing file corruption. Thank you for the advice! As a side note, I know the image file was updated (confirmed by examining the file on a Windows machine) -- but the instance of digiKam on that machine is not seeing the image update -- it is viewable but without the updated tag. I even restarted that instance of digiKam but it's not seeing the changes. Maybe it's a setting -- like "Monitor the albums for external changes (requires restart)". - Vince D [image: image.png] On Wed, Aug 16, 2023 at 3:33 PM Maik Qualmann <bugzilla_nore...@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=473430 > > --- Comment #12 from Maik Qualmann <metzping...@gmail.com> --- > The problem will surely be related to the virtual machine in Chrome OS. > Please activate writing with ExifTool with the digiKam-8.2.0 version in the > digiKam settings under Metadata. Please test whether the problem can be > reproduced. Otherwise please the debug log from the terminal. It's very > simple > you type in the "export" command in the terminal and then type in the > "digikam" > command in the same terminal. Copy the output in the terminal and post it > here. > > export QT_LOGGING_RULES="digikam*=true" > digiKam-8.2.0-xxxxx-x86-64.appimage > > Maik > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
