Bug 497801 - Dolphin crash when launching gThumb.
Summary: Dolphin crash when launching gThumb.
Status: RESOLVED UNMAINTAINED
Alias: None
Product: dolphin
Classification: Applications
Component: general (show other bugs)
Version: 22.12.3
Platform: Debian stable Linux
: NOR crash
Target Milestone: ---
Assignee: Dolphin Bug Assignee
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2024-12-22 22:08 UTC by E. F. Keebler
Modified: 2025-01-02 03:31 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description E. F. Keebler 2024-12-22 22:08:04 UTC
Application: dolphin (22.12.3)

Qt Version: 5.15.8
Frameworks Version: 5.103.0
Operating System: Linux 6.1.0-28-amd64 x86_64
Windowing System: X11
Distribution: Debian GNU/Linux 12 (bookworm)
DrKonqi: 5.27.5 [KCrashBackend]

-- Information about the crash:
I've been having issues with my second monitor (attached to a Dell K20A docking station) shutting off when launching gThumb.  This time the KDE Crash Handler also opened and informed me that Dolphin had crashed.  I'm not sure about correlation vs. causation here, but am submitting the crash report in case anyone can figure out the issue.  Thanks!

The crash can be reproduced sometimes.

-- Backtrace:
Application: Dolphin (dolphin), signal: Segmentation fault

[KCrash Handler]
#4  0x00007fd7d66e4b2f in QObject::property(char const*) const () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x00007fd7d867d2a1 in KUiServerV2JobTracker::registerJob(KJob*) () from /lib/x86_64-linux-gnu/libKF5JobWidgets.so.5
#6  0x00007fd7d867c1f6 in ?? () from /lib/x86_64-linux-gnu/libKF5JobWidgets.so.5
#7  0x00007fd7d66e8f8f in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x00007fd7d66e8f8f in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#9  0x00007fd7d7b2fdaf in QDBusServiceWatcher::serviceOwnerChanged(QString const&, QString const&, QString const&) () from /lib/x86_64-linux-gnu/libQt5DBus.so.5
#10 0x00007fd7d7b306ca in ?? () from /lib/x86_64-linux-gnu/libQt5DBus.so.5
#11 0x00007fd7d7b30b73 in QDBusServiceWatcher::qt_metacall(QMetaObject::Call, int, void**) () from /lib/x86_64-linux-gnu/libQt5DBus.so.5
#12 0x00007fd7d7ae261b in ?? () from /lib/x86_64-linux-gnu/libQt5DBus.so.5
#13 0x00007fd7d66dd730 in QObject::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#14 0x00007fd7d7362fae in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#15 0x00007fd7d66b1738 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#16 0x00007fd7d66b46c1 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#17 0x00007fd7d670a193 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#18 0x00007fd7d44627a9 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#19 0x00007fd7d4462a38 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#20 0x00007fd7d4462acc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#21 0x00007fd7d6709876 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#22 0x00007fd7d66b01bb in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#23 0x00007fd7d66b8316 in QCoreApplication::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#24 0x000055a217c7d142 in ?? ()
#25 0x00007fd7d624624a in ?? () from /lib/x86_64-linux-gnu/libc.so.6
#26 0x00007fd7d6246305 in __libc_start_main () from /lib/x86_64-linux-gnu/libc.so.6
#27 0x000055a217c7d591 in ?? ()
[Inferior 1 (process 96331) detached]

Reported using DrKonqi
Comment 1 John Kizer 2025-01-02 03:31:50 UTC
Thank you for your bug report!

Debian advises users to not submit bugs upstream (https://www.debian.org/Bugs/Reporting), as this version of the KDE software is out of support from KDE, and so it's possible that the bug exists only in Debian at this point. Could you report the bug to Debian using the report bug utility (https://packages.debian.org/stable/utils/reportbug)? If necessary, the maintainer of the package will forward the bug upstream.

Thanks for understanding!