Bug 452323

Summary:	digiKam crash after importing photos
Product:	[Applications] digikam	Reporter:	David <kitt997>
Component:	Import-History	Assignee:	Digikam Developers <digikam-bugs-null>
Status:	RESOLVED FIXED
Severity:	crash	CC:	caulier.gilles, metzpinguin
Priority:	NOR	Keywords:	drkonqi
Version:	7.6.0
Target Milestone:	---
Platform:	Fedora RPMs
OS:	Linux
Latest Commit:		Version Fixed In:	7.7.0
Sentry Crash Report:

Description David 2022-04-06 11:49:14 UTC

Application: digikam (7.6.0)

Qt Version: 5.15.2
Frameworks Version: 5.91.0
Operating System: Linux 5.15.17-200.fc35.x86_64 x86_64
Windowing System: X11
Distribution: Fedora Linux 35 (Thirty Five)
DrKonqi: 5.24.3 [KCrashBackend]

-- Information about the crash:
- What I was doing when the application crashed:
I was importing some photos, it started responding slowly and then, when import wizard closed, it crashed

The reporter is unsure if this crash is reproducible.

-- Backtrace:
Application: digiKam (digikam), signal: Segmentation fault

[KCrash Handler]
#4  0x00007f6ffda0f5fc in QMetaObject::cast(QObject const*) const () at /lib64/libQt5Core.so.5
#5  0x00007f6ffe7d73a0 in QTreeWidget::setCurrentItem(QTreeWidgetItem*, int) () at /lib64/libQt5Widgets.so.5
#6  0x00007f6ffff47792 in Digikam::ImportUI::slotLogMsg(QString const&, Digikam::DHistoryView::EntryType, QString const&, QString const&) () at /lib64/libdigikamgui.so.7.6.0
#7  0x00007f6ffda30f49 in QObject::event(QEvent*) () at /lib64/libQt5Core.so.5
#8  0x00007f6ffd24857d in KXmlGuiWindow::event(QEvent*) () at /lib64/libKF5XmlGui.so.5
#9  0x00007f6ffe4db443 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /lib64/libQt5Widgets.so.5
#10 0x00007f6ffda067d8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /lib64/libQt5Core.so.5
#11 0x00007f6ffda09d46 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /lib64/libQt5Core.so.5
#12 0x00007f6ffda58117 in postEventSourceDispatch(_GSource*, int (*)(void*), void*) () at /lib64/libQt5Core.so.5
#13 0x00007f6ffb87a0af in g_main_context_dispatch () at /lib64/libglib-2.0.so.0
#14 0x00007f6ffb8cf308 in g_main_context_iterate.constprop () at /lib64/libglib-2.0.so.0
#15 0x00007f6ffb8778a3 in g_main_context_iteration () at /lib64/libglib-2.0.so.0
#16 0x00007f6ffda57bb8 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /lib64/libQt5Core.so.5
#17 0x00007f6ffda051e2 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /lib64/libQt5Core.so.5
#18 0x00007f6ffda0d724 in QCoreApplication::exec() () at /lib64/libQt5Core.so.5
#19 0x0000559e9d0f9296 in main ()
[Inferior 1 (process 15544) detached]

Possible duplicates by query: bug 447593, bug 443729, bug 440587, bug 440296, bug 438840.

Reported using DrKonqi

Comment 1 caulier.gilles 2022-04-06 11:51:11 UTC

Why it crash in history log view... ?

Comment 2 Maik Qualmann 2022-04-06 11:58:26 UTC

The crash report is not complete, the thread that crashed is missing. Please use GDB and try to create a backtrace. As described here:

https://www.digikam.org/contribute/

Maik

Comment 3 Maik Qualmann 2022-04-06 12:00:08 UTC

@Gilles, do you think the crash report is complete and it's crashing in the message log?

Maik

Comment 4 caulier.gilles 2022-04-06 12:00:17 UTC

Git commit ef1cc0b5f9da83edef611c1d007d8df8bd311987 by Gilles Caulier.
Committed on 06/04/2022 at 11:57.
Pushed by cgilles into branch 'master'.

prevent crash if item is null

M  +19   -1    core/libs/progressmanager/dhistoryview.cpp

https://invent.kde.org/graphics/digikam/commit/ef1cc0b5f9da83edef611c1d007d8df8bd311987