https://bugs.kde.org/show_bug.cgi?id=389690
Bug ID: 389690
Summary: Updated image label and image is broken after metadata
is written to file
Product: digikam
Version: 5.8.0
Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
Severity: major
Priority: NOR
Component: Metadata-Engine
Assignee: digikam-bugs-n...@kde.org
Reporter: e...@coloursofdiscovery.com
Target Milestone: ---
I was adding metadata to a 7.2mb jpg file and after adding a label or star
rating in digikam, digikam recreated the image to add the metadata to the image
file. But the image was not saved properly and the new file was 1.5mb in size
and missing just under half the pixel content (the bottom half of the image was
just black with no data at all).
Steps to re create:
Change from thumbnail to preview.
Add label to image (I added the reject label).
Digikam save's the image and the image re-loads.
The bottom third of the image is missing and is gray or black depending on the
application used to open the image.
I opened the image in another application to check and found that just under
half the image was missing.
The same thing happen for 5 of my images before I found out. After I found out
that digikam was not creating the images properly after adding metadata I then
switched off this function in the settings so metadata is only written to
sidecar files and the db.
I'm running digikam in quite on old computer (only 4gb RAM), and I noticed that
most of the ram was in use when this happened, so maybe it just ran out of
memory so only wrote part of the file? If this is the case would they be a way
for digikam to just take longer and finish writing the data to file properly?
Environment
I'm running the latest 5.8.0 version using the diskimage from digikam.org on
ubuntu 16.04 Lts. The system is up to date. I setup Digikam to use mariadb10 as
backend and the images are accessed over smb from a nas, the network has jumbo
frames enabled on all devices.
--
You are receiving this mail because:
You are watching all bug changes.
