Bug 383347 - KDE Partition Manager crashed after USB stick reformat
Summary: KDE Partition Manager crashed after USB stick reformat
Status: RESOLVED DUPLICATE of bug 380114
Alias: None
Product: frameworks-knotifications
Classification: Frameworks and Libraries
Component: general (show other bugs)
Version: 5.36.0
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: kdelibs bugs
Keywords: drkonqi
Depends on:
Reported: 2017-08-10 09:19 UTC by Xavier Besnard
Modified: 2017-09-05 16:15 UTC (History)
2 users (show)

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


Note You need to log in before you can comment on or make changes to this bug.
Description Xavier Besnard 2017-08-10 09:19:36 UTC
Application: partitionmanager (3.0.0)

Qt Version: 5.9.1
Frameworks Version: 5.36.0
Operating System: Linux 4.11.0-13-generic x86_64
Distribution: Ubuntu Artful Aardvark (development branch)

-- Information about the crash:
- What I was doing when the application crashed:
To  create a bootable USB stick, I used KDE partition Manager to create a 4Go/Fat 16 partition on a 8Go USB Stick.
After success completion of formatting, KDE partition Manager crashed.
Configuration: Kubuntu Artful dev 17.10 updated daily (just before the crash)

-- Backtrace:
Application: Gestionnaire de partitions de KDE (partitionmanager), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fc3d030b940 (LWP 13080))]

Thread 2 (Thread 0x7fc3b7730700 (LWP 13082)):
#0  0x00007fc3cbd28cdd in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x00007fc3c67a0df6 in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007fc3c67a0f0c in g_main_context_iteration () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007fc3cc65a41b in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x00007fc3cc5ffdba in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x00007fc3cc41f3ca in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x00007fc3cb5a5e45 in  () at /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
#7  0x00007fc3cc42429d in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x00007fc3c7ffd74a in start_thread (arg=0x7fc3b7730700) at pthread_create.c:456
#9  0x00007fc3cbd34caf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:97

Thread 1 (Thread 0x7fc3d030b940 (LWP 13080)):
[KCrash Handler]
#4  0x00000005edc5f800 in  ()
#5  0x00007fc3afbdeba6 in  () at /usr/lib/x86_64-linux-gnu/libKF5Notifications.so.5
#6  0x00007fc3afbdec39 in  () at /usr/lib/x86_64-linux-gnu/libKF5Notifications.so.5
#7  0x00007fc3cc62e44b in QObjectPrivate::deleteChildren() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x00007fc3cc637cdb in QObject::~QObject() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#9  0x00007fc3afbb9359 in  () at /usr/lib/x86_64-linux-gnu/libKF5Notifications.so.5
#10 0x00007fc3cbc662a0 in __run_exit_handlers (status=0, listp=0x7fc3cbfeb5d8 <__exit_funcs>, run_list_atexit=run_list_atexit@entry=true, run_dtors=run_dtors@entry=true) at exit.c:83
#11 0x00007fc3cbc662fa in __GI_exit (status=<optimized out>) at exit.c:105
#12 0x00007fc3cbc4c428 in __libc_start_main (main=0x5ecb90430 <main>, argc=1, argv=0x7ffe1f6cec48, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7ffe1f6cec38) at ../csu/libc-start.c:325
#13 0x00000005ecb90cea in _start ()

Reported using DrKonqi
Comment 1 Andrius Štikonas 2017-08-10 14:20:33 UTC
Doesn't look like a crash in partition manager or kpmcore.

Reassigning to knotifications.

You should also make a backtrace with a debug symbols if you can reproduce this bug. Otherwise it is not particularly useful.
Comment 2 Christoph Feck 2017-09-04 15:27:19 UTC

*** This bug has been marked as a duplicate of bug 380114 ***