https://bugs.kde.org/show_bug.cgi?id=390580
Bug ID: 390580
Summary: First crashes when saving tiff file, then crashes when
starting.
Product: digikam
Version: 5.8.0
Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
Severity: grave
Priority: NOR
Component: Versioning
Assignee: digikam-bugs-n...@kde.org
Reporter: hamhen...@gmail.com
Target Milestone: ---
After upgrading from Fedora 25 to 27, all software, digikam has become totally
unstable. Crashes when saving tiff files, then crashes when starting. It is
probably an exiv2 thing. I have have verified that the very things happens if I
force to run on one cpu/thread. I have verified it is not due to a problem
with the digikam database, as an artificial new user with almost no images
have the same problems. It seems to be related to digikam having a problem
saving information to tiff images, and then again re-reading it. For many years
this worked perfectly..
I include an extract from gdb[New Thread 0x7ffe9a7fc700 (LWP 11015)]
[New Thread 0x7ffe9bfff700 (LWP 11016)]
[New Thread 0x7ffe997fa700 (LWP 11017)]
[New Thread 0x7ffe98ff9700 (LWP 11018)]
[New Thread 0x7ffe6bfff700 (LWP 11019)]
[New Thread 0x7ffe6b7fe700 (LWP 11020)]
Thread 26 "Thread (pooled)" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fff1affd700 (LWP 10984)]
0x00007ffff56f3e1b in Exiv2::IptcData::printStructure(std::ostream&, unsigned
char const*, unsigned long, unsigned int) ()
from /lib64/libexiv2.so.26
Missing separate debuginfos, use: dnf debuginfo-install
OpenEXR-libs-2.2.0-10.fc27.x86_64 SuperLU-5.2.0-4.fc27.x86_64
alsa-lib-1.1.5-1.fc27.x86_64 armadillo-7.900.1-3.fc27.x86_64
arpack-3.5.0-4.fc27.x86_64 atlas-3.10.3-1.fc27.x86_64 blas-3.8.0-4.fc27.x86_64
bzip2-libs-1.0.6-24.fc27.x86_64 cfitsio-3.370-10.fc27.x86_64
cyrus-sasl-lib-2.1.26-34.fc27.x86_64 dbus-libs-1.12.0-1.fc27.x86_64
dbusmenu-qt5-0.9.3-0.15.20150604.fc27.x86_64
elfutils-libelf-0.170-1.fc27.x86_64 exiv2-libs-0.26-6.fc27.x
--
You are receiving this mail because:
You are watching all bug changes.
