Bug 397302 - KDE Partition manager crashing after upgrade
Summary: KDE Partition manager crashing after upgrade
Status: RESOLVED WORKSFORME
Alias: None
Product: partitionmanager
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Andrius Štikonas
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2018-08-09 08:35 UTC by matscie2
Modified: 2019-06-16 04:33 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description matscie2 2018-08-09 08:35:08 UTC
Application: partitionmanager (3.3.1)

Qt Version: 5.9.5
Frameworks Version: 5.44.0
Operating System: Linux 4.15.0-29-generic x86_64
Distribution: Ubuntu 18.04.1 LTS

-- Information about the crash:
application hangs at 50%, clicked cancel then it crash, went to send report

The crash can be reproduced every time.

-- Backtrace:
Application: KDE Partition Manager (partitionmanager), signal: Aborted
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f9cd4998840 (LWP 8277))]

Thread 3 (Thread 0x7f9cac490700 (LWP 8396)):
#0  syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
#1  0x00007f9cd0f57765 in QBasicMutex::lockInternal() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#2  0x00007f9cd0f57ac3 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#3  0x00007f9cd0f585b7 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x00007f9cd0f58eb6 in QReadWriteLock::tryLockForWrite(int) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x00007f9cd455cc18 in OperationStack::addDevice(Device*) () from /usr/lib/x86_64-linux-gnu/libkpmcore.so.7
#6  0x00007f9cd4551b1c in DeviceScanner::scan() () from /usr/lib/x86_64-linux-gnu/libkpmcore.so.7
#7  0x00007f9cd0f6016d in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x00007f9ccc78a6db in start_thread (arg=0x7f9cac490700) at pthread_create.c:463
#9  0x00007f9cd085688f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 2 (Thread 0x7f9cb8d78700 (LWP 8279)):
#0  0x00007f9ccaed297c in g_main_context_prepare () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x00007f9ccaed336b in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007f9ccaed354c in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007f9cd119790b in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x00007f9cd113c9ea in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x00007f9cd0f5b22a in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x00007f9cd0066d45 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
#7  0x00007f9cd0f6016d in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x00007f9ccc78a6db in start_thread (arg=0x7f9cb8d78700) at pthread_create.c:463
#9  0x00007f9cd085688f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 1 (Thread 0x7f9cd4998840 (LWP 8277)):
[KCrash Handler]
#4  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51
#5  0x00007f9cd0775801 in __GI_abort () at abort.c:79
#6  0x00007f9cd0f4afa7 in QMessageLogger::fatal(char const*, ...) const () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x00007f9cd0f5a17d in QThread::~QThread() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x00007f9cd4597507 in ?? () from /usr/lib/x86_64-linux-gnu/libkpmcore.so.7
#9  0x00007f9cd116b19b in QObjectPrivate::deleteChildren() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#10 0x00007f9cd1ef6d4c in QWidget::~QWidget() () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#11 0x00007f9cd3d1273d in KMainWindow::~KMainWindow() () from /usr/lib/x86_64-linux-gnu/libKF5XmlGui.so.5
#12 0x0000559d70e72184 in ?? ()
#13 0x00007f9cd116e140 in QObject::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#14 0x00007f9cd1efb743 in QWidget::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#15 0x00007f9cd200ec4b in QMainWindow::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#16 0x00007f9cd3d14b87 in KMainWindow::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libKF5XmlGui.so.5
#17 0x00007f9cd3d599e5 in KXmlGuiWindow::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libKF5XmlGui.so.5
#18 0x00007f9cd1ebc82c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#19 0x00007f9cd1ec40f4 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#20 0x00007f9cd113e9a8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#21 0x00007f9cd114111d in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#22 0x00007f9cd11982c3 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#23 0x00007f9ccaed3287 in g_main_context_dispatch () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#24 0x00007f9ccaed34c0 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#25 0x00007f9ccaed354c in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#26 0x00007f9cd11978ef in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#27 0x00007f9cd113c9ea in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#28 0x00007f9cd1145a84 in QCoreApplication::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#29 0x0000559d70e18eef in main ()

Possible duplicates by query: bug 396860, bug 395743, bug 392092, bug 389875, bug 389801.

Reported using DrKonqi
Comment 1 Andrius Štikonas 2018-08-23 19:03:33 UTC
Can you get a full backtrace with debug symbols?

Without seeing line numbers where crash happens it's much harder to see what can go wrong...
Comment 2 Andrius Štikonas 2019-05-17 18:25:34 UTC
Could also be resolved in kpmcore 4 which uses different backend.
Comment 3 Bug Janitor Service 2019-06-01 04:33:07 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 4 Bug Janitor Service 2019-06-16 04:33:11 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!