Application: kdeconnectd (20.12.3) Qt Version: 5.15.2 Frameworks Version: 5.78.0 Operating System: Linux 5.10.0-11-amd64 x86_64 Windowing system: X11 Distribution: Debian GNU/Linux 11 (bullseye) -- Information about the crash: I was currently running dduper (to dedupe my files on my root drive) and had the system running in the background. The night before, I managed to corrupt my BTRFS root partition while updating the Kali distro that is in a separate subvolume to this Debian distro. So, I copied all files off and then recreated the BTRFS partition. The deduper is what I'm running now in order to dedupe the files again. I've never had kdeconnect crash on me before, so I believe this may be the reason why it crashed. This bug report may be hard to reproduce given the unique nature of how my system is setup, but I figured it may help if this problem occurs in the future to someone else incase it was a filesystem or permission bit issue. -- Backtrace: Application: KDE Connect Daemon (kdeconnectd), signal: Segmentation fault [KCrash Handler] #4 0x00007fc0fef811d9 in KNotification::id() () from /lib/x86_64-linux-gnu/libKF5Notifications.so.5 #5 0x00007fc0fef95635 in ?? () from /lib/x86_64-linux-gnu/libKF5Notifications.so.5 #6 0x00007fc0fef9598a in ?? () from /lib/x86_64-linux-gnu/libKF5Notifications.so.5 #7 0x00007fc0fdcc65a6 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x00007fc0fdf91b8f in QDBusPendingCallWatcher::finished(QDBusPendingCallWatcher*) () from /lib/x86_64-linux-gnu/libQt5DBus.so.5 #9 0x00007fc0fdcbbff1 in QObject::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x00007fc0fe7d915f in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #11 0x00007fc0fdc8ffca in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #12 0x00007fc0fdc92a01 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #13 0x00007fc0fdce7e93 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #14 0x00007fc0fc38fe6b in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #15 0x00007fc0fc390118 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #16 0x00007fc0fc3901cf in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #17 0x00007fc0fdce751f in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #18 0x00007fc0fdc8e98b in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #19 0x00007fc0fdc96c00 in QCoreApplication::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #20 0x000055d6842a29c5 in ?? () #21 0x00007fc0fd674d0a in __libc_start_main () from /lib/x86_64-linux-gnu/libc.so.6 #22 0x000055d6842a2c2a in _start () [Inferior 1 (process 1640) detached] Report to https://bugs.kde.org/
KDE Connect stores the icons of notifications as png images on a temporary folder. It's very likely that those got "deduped" since sometimes we create the same image more than once if they come from different notifications but with the same icon. This probably is what made it crash. Honestly, I don't think it's worth fixing since running dedupe on your whole disk can probably have lots of other nasty side effects like this and is not something we should support.