I use Digikam 14.4 from in Xubuntu 16.04 from Philip Johnsons PPA. Since some days, digikam crashes in album view when going from one image to the next, but only if the next image is in portrait format. Same crash occurs *sometimes* when selecting (double click) the first image in an album and this is a portrait format. Reproducible: Always Steps to Reproduce: 1. select album with mix of landscape and portrait images. Select a landscape image, click for the next one until you reach a portrait format image. Crash. gdb digikam GNU gdb (Ubuntu 7.11-0ubuntu1) 7.11 Copyright (C) 2016 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-linux-gnu". Type "show configuration" for configuration details. For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>. Find the GDB manual and other documentation resources online at: <http://www.gnu.org/software/gdb/documentation/>. For help, type "help". Type "apropos word" to search for commands related to "word"... Reading symbols from digikam...Reading symbols from /usr/lib/debug/.build-id/b5/06929a2606d2341c5a32f3dbdb52da5ed76321.debug...done. done. (gdb) RUN Starting program: /usr/bin/digikam [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [New Thread 0x7fffcbf61700 (LWP 4980)] [New Thread 0x7fffc7cc6700 (LWP 4982)] [New Thread 0x7fffc74c5700 (LWP 4983)] [New Thread 0x7fffc6cc4700 (LWP 4984)] [Thread 0x7fffc6cc4700 (LWP 4984) exited] [New Thread 0x7fffc6cc4700 (LWP 4987)] [Thread 0x7fffcbf61700 (LWP 4980) exited] [New Thread 0x7fffc4a96700 (LWP 4990)] Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString) QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave. QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave. kbuildsycoca4 running... [New Thread 0x7fffb628a700 (LWP 5000)] [Thread 0x7fffb628a700 (LWP 5000) exited] [New Thread 0x7fffb628a700 (LWP 5001)] [New Thread 0x7fffabffe700 (LWP 5002)] [Thread 0x7fffb628a700 (LWP 5001) exited] [Thread 0x7fffabffe700 (LWP 5002) exited] [New Thread 0x7fffabffe700 (LWP 5003)] [New Thread 0x7fffb628a700 (LWP 5004)] [New Thread 0x7fffab113700 (LWP 5005)] [New Thread 0x7fffaa912700 (LWP 5006)] [New Thread 0x7fffaa111700 (LWP 5007)] [New Thread 0x7fffa9910700 (LWP 5008)] [New Thread 0x7fffa910f700 (LWP 5009)] [New Thread 0x7fffa890e700 (LWP 5010)] [New Thread 0x7fff83fff700 (LWP 5011)] [New Thread 0x7fff8bfff700 (LWP 5012)] [New Thread 0x7fff8b7fe700 (LWP 5013)] [New Thread 0x7fff8affd700 (LWP 5014)] [New Thread 0x7fff8a7fc700 (LWP 5015)] [New Thread 0x7fff89ffb700 (LWP 5016)] [New Thread 0x7fff897fa700 (LWP 5017)] [New Thread 0x7fff88ff9700 (LWP 5018)] [New Thread 0x7fff837fe700 (LWP 5019)] [New Thread 0x7fff82ffd700 (LWP 5020)] [New Thread 0x7fff827fc700 (LWP 5021)] [New Thread 0x7fff81ffb700 (LWP 5022)] [New Thread 0x7fff817fa700 (LWP 5023)] [New Thread 0x7fff80ff9700 (LWP 5024)] [New Thread 0x7fff73fff700 (LWP 5025)] [New Thread 0x7fff737fe700 (LWP 5026)] [New Thread 0x7fff72ffd700 (LWP 5027)] [New Thread 0x7fff727fc700 (LWP 5028)] [New Thread 0x7fff71ffb700 (LWP 5029)] [New Thread 0x7fff717fa700 (LWP 5030)] [New Thread 0x7fff70ff9700 (LWP 5031)] [New Thread 0x7fff707f8700 (LWP 5032)] [New Thread 0x7fff6fff7700 (LWP 5033)] [New Thread 0x7fff6f7f6700 (LWP 5034)] [New Thread 0x7fff6eff5700 (LWP 5035)] [New Thread 0x7fff6e7f4700 (LWP 5036)] [New Thread 0x7fff6dff3700 (LWP 5037)] [New Thread 0x7fff6d7f2700 (LWP 5038)] [New Thread 0x7fff5d289700 (LWP 5063)] [New Thread 0x7fff5ca88700 (LWP 5064)] [New Thread 0x7fff62e17700 (LWP 5066)] [New Thread 0x7fff61f94700 (LWP 5068)] [New Thread 0x7fff61793700 (LWP 5069)] Thread 50 "Thread (pooled)" received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x7fff61f94700 (LWP 5068)] Digikam::ImageHistogram::calculate (this=0x40cb260) at /build/digikam-lwP2T0/digikam-4.14.0/core/libs/dimg/filters/levels/imagehistogram.cpp:237 237 /build/digikam-lwP2T0/digikam-4.14.0/core/libs/dimg/filters/levels/imagehistogram.cpp: Datei oder Verzeichnis nicht gefunden. (gdb) bt #0 Digikam::ImageHistogram::calculate (this=0x40cb260) at /build/digikam-lwP2T0/digikam-4.14.0/core/libs/dimg/filters/levels/imagehistogram.cpp:237 #1 0x00007ffff5a982ee in Digikam::DynamicThread::DynamicThreadPriv::run (this=0x417aff0) at /build/digikam-lwP2T0/digikam-4.14.0/core/libs/threads/dynamicthread.cpp:186 #2 0x00007ffff145ce0a in QThreadPoolThread::run (this=0x4161fe0) at concurrent/qthreadpool.cpp:108 #3 0x00007ffff1469e3c in QThreadPrivate::start (arg=0x4161fe0) at thread/qthread_unix.cpp:352 #4 0x00007fffed3866fa in start_thread (arg=0x7fff61f94700) at pthread_create.c:333 #5 0x00007ffff0911b5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 (gdb) quit A debugging session is active. Inferior 1 [process 4974] will be killed. Quit anyway? (y or n) y hph@hackbrett-PC:~/Programme$ QSocketNotifier: Invalid socket 16 and type 'Read', disabling... QSocketNotifier: Invalid socket 16 and type 'Read', disabling... QSocketNotifier: Invalid socket 15 and type 'Read', disabling... QSocketNotifier: Invalid socket 15 and type 'Read', disabling...
I can not reproduce this problem with digikam-5.0.0-beta7. Can you upload a test image in portrait format? Maik
I can provide a sample, but how? Just attach it here in the bugs.kde.org ? Additional info: it seems that it crashes only with portrait mode images from my new Sony A77ii, older images can be browsed without crash. I just de-installed exiv2 from Phillip Johnsons ppa and installed the older libgexif2-2 from Ubuntu repos instead, this seem to work stable. HP
bugzilla file storage is very limited in size. Use a cloud web service to share a file. But as you said previously, it sound like a bug in Exiv2. It's difficult to confirm, as the GDB backtrace is uncomplete. Gilles Caulier
Any fresh news ? Without sample images to test, we cannot hack this problem. Gilles Caulier
As you already said in the last reply, it seems to be an issue with libexiv2. I just updated again to libexiv2 from Phillip Johnsons ppa, and it does also work again. Strange :) So i can no longer reproduce the bug. Please close the issue. Thanks for looking into this. HP