Application: partitionmanager (21.04.3) Qt Version: 5.15.2 Frameworks Version: 5.84.0 Operating System: Linux 5.13.2-1-MANJARO x86_64 Windowing System: X11 Drkonqi Version: 5.22.3 Distribution: Manjaro Linux -- Information about the crash: - What I was doing when the application crashed: I have set a bind mount for a music folder, which is mounted directly on the music folder in the home directory. I also have all external hard drives (including the bind mount) in the fstab via "noauto,x-systemd.automount". - Unusual behavior I noticed: After that, the KDE partition manager still starts, but hangs on "/dev/sda" in the scan. However, gparted works perfectly. - Custom settings of the application: The crash can be reproduced every time. -- Backtrace: Application: KDE-Partitionsverwaltung (partitionmanager), signal: Aborted [KCrash Handler] #4 0x00007f363604ed22 in raise () from /usr/lib/libc.so.6 #5 0x00007f3636038862 in abort () from /usr/lib/libc.so.6 #6 0x00007f3636484910 in QMessageLogger::fatal(char const*, ...) const () from /usr/lib/libQt5Core.so.5 #7 0x00007f36364851ae in ?? () from /usr/lib/libQt5Core.so.5 #8 0x00007f3637d8a388 in ?? () from /usr/lib/libkpmcore.so.11 #9 0x00007f36366d7b7e in QObjectPrivate::deleteChildren() () from /usr/lib/libQt5Core.so.5 #10 0x00007f36371c05ce in QWidget::~QWidget() () from /usr/lib/libQt5Widgets.so.5 #11 0x0000559316001b35 in ?? () #12 0x00007f36366da2a0 in QObject::event(QEvent*) () from /usr/lib/libQt5Core.so.5 #13 0x00007f3637d06228 in KXmlGuiWindow::event(QEvent*) () from /usr/lib/libKF5XmlGui.so.5 #14 0x00007f3637181d62 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQt5Widgets.so.5 #15 0x00007f36366ad3aa in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib/libQt5Core.so.5 #16 0x00007f36366b04a9 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib/libQt5Core.so.5 #17 0x00007f36367069a4 in ?? () from /usr/lib/libQt5Core.so.5 #18 0x00007f3634da610c in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #19 0x00007f3634df9b99 in ?? () from /usr/lib/libglib-2.0.so.0 #20 0x00007f3634da3871 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #21 0x00007f3636705fd6 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQt5Core.so.5 #22 0x00007f36366abd1c in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQt5Core.so.5 #23 0x00007f36366b4284 in QCoreApplication::exec() () from /usr/lib/libQt5Core.so.5 #24 0x0000559316000826 in main () [Inferior 1 (process 33578) detached] Possible duplicates by query: bug 432704, bug 430799, bug 430393, bug 424911, bug 423951. Reported using DrKonqi
Not sure what's happening but bugzilla suggests that 432704 has the same backtrace, so probably fixing that bug will fix your problem too.
Can you also run this from terminal and see if there is anything suspicious printed there?
Is this still happening? It was probably due to broken dummy backend which is now fixed.
*** This bug has been marked as a duplicate of bug 432704 ***