Bug 458449 - Ubuntu Studio crash due to corrupt SD card
Summary: Ubuntu Studio crash due to corrupt SD card
Status: REPORTED
Alias: None
Product: partitionmanager
Classification: Applications
Component: general (other bugs)
Version First Reported In: 21.12.3
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Andrius Štikonas
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2022-08-29 02:09 UTC by joelc1431
Modified: 2024-07-29 15:40 UTC (History)
1 user (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description joelc1431 2022-08-29 02:09:52 UTC
Application: partitionmanager (21.12.3)

Qt Version: 5.15.3
Frameworks Version: 5.92.0
Operating System: Linux 5.15.0-46-lowlatency x86_64
Windowing System: X11
Distribution: Ubuntu 22.04.1 LTS
DrKonqi: 5.24.4 [KCrashBackend]

-- Information about the crash:
- What I was doing when the application crashed: attempting to create new partition table and add a new partition. I believe table was created and app crashed during partion creation. 
Bear with me, i am new to Linux. Thanks.

The crash can be reproduced every time.

-- Backtrace:
Application: KDE Partition Manager (partitionmanager), signal: Aborted

[KCrash Handler]
#4  __pthread_kill_implementation (no_tid=0, signo=6, threadid=140011286686080) at ./nptl/pthread_kill.c:44
#5  __pthread_kill_internal (signo=6, threadid=140011286686080) at ./nptl/pthread_kill.c:78
#6  __GI___pthread_kill (threadid=140011286686080, signo=signo@entry=6) at ./nptl/pthread_kill.c:89
#7  0x00007f56ee8f5476 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26
#8  0x00007f56ee8db7f3 in __GI_abort () at ./stdlib/abort.c:79
#9  0x00007f56eed97ba3 in QMessageLogger::fatal(char const*, ...) const () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#10 0x00007f56eed9844b in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#11 0x00007f56f06b173b in ?? () from /lib/x86_64-linux-gnu/libkpmcore.so.11
#12 0x00007f56eefeba5e in QObjectPrivate::deleteChildren() () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#13 0x00007f56efaeebc6 in QWidget::~QWidget() () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#14 0x0000561a902db348 in ?? ()
#15 0x00007f56eefee1b3 in QObject::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#16 0x00007f56f06276fd in KXmlGuiWindow::event(QEvent*) () from /lib/x86_64-linux-gnu/libKF5XmlGui.so.5
#17 0x00007f56efab0713 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#18 0x00007f56eefc0e2a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#19 0x00007f56eefc3f17 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#20 0x00007f56ef01aa57 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#21 0x00007f56ed790d1b in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#22 0x00007f56ed7e56f8 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#23 0x00007f56ed78e3c3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#24 0x00007f56ef01a0a8 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#25 0x00007f56eefbf74b in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#26 0x00007f56eefc7ce4 in QCoreApplication::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#27 0x0000561a902d6e7a in ?? ()
#28 0x00007f56ee8dcd90 in __libc_start_call_main (main=main@entry=0x561a902d6440, argc=argc@entry=1, argv=argv@entry=0x7ffc7e270128) at ../sysdeps/nptl/libc_start_call_main.h:58
#29 0x00007f56ee8dce40 in __libc_start_main_impl (main=0x561a902d6440, argc=1, argv=0x7ffc7e270128, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7ffc7e270118) at ../csu/libc-start.c:392
#30 0x0000561a902da8f5 in ?? ()
[Inferior 1 (process 5140) detached]

Reported using DrKonqi
Comment 1 Andrius Štikonas 2022-09-03 00:31:50 UTC
If possible, could you try to install debugging symbols for kpmcore and partitionmanager and try to get backtrace again?
Comment 2 Natalie Marie 2024-07-29 15:40:37 UTC
*** Spam removed ***