Application: partitionmanager-bin (1.0.3) KDE Platform Version: 4.8.3 (4.8.3) (Compiled from sources) Qt Version: 4.8.1 Operating System: Linux 3.2.0-24-generic x86_64 Distribution: Ubuntu 12.04 LTS -- Information about the crash: - What I was doing when the application crashed: Trying to check a NTFS partition (because I could change its size before) - Custom settings of the application: none (but the NTFS file system is on a logical partition) The crash can be reproduced every time. -- Backtrace: Application: Gestionnaire de partitions de KDE (partitionmanager-bin), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7ff68faaf840 (LWP 4123))] Thread 3 (Thread 0x7ff67d163700 (LWP 4213)): #0 0x00007ff68982130a in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x00007ff689821589 in g_mutex_unlock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x00007ff6897e5713 in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x00007ff6897e5f1b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x00007ff6897e6124 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x00007ff68e793426 in QEventDispatcherGlib::processEvents (this=0x7ff6700008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #6 0x00007ff68e762c82 in QEventLoop::processEvents (this=<optimized out>, flags=...) at kernel/qeventloop.cpp:149 #7 0x00007ff68e762ed7 in QEventLoop::exec (this=0x7ff67d162d10, flags=...) at kernel/qeventloop.cpp:204 #8 0x00007ff68e661fa7 in QThread::exec (this=<optimized out>) at thread/qthread.cpp:501 #9 0x00007ff68e7429ff in QInotifyFileSystemWatcherEngine::run (this=0x2119c20) at io/qfilesystemwatcher_inotify.cpp:248 #10 0x00007ff68e664fcb in QThreadPrivate::start (arg=0x2119c20) at thread/qthread_unix.cpp:298 #11 0x00007ff68b3c7e9a in start_thread (arg=0x7ff67d163700) at pthread_create.c:308 #12 0x00007ff68d13a4bd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #13 0x0000000000000000 in ?? () Thread 2 (Thread 0x7ff67c8c5700 (LWP 4221)): [KCrash Handler] #6 0x00007ff68d07e445 in __GI_raise (sig=<optimized out>) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64 #7 0x00007ff68d081bab in __GI_abort () at abort.c:91 #8 0x00007ff68d6d269d in __gnu_cxx::__verbose_terminate_handler() () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 #9 0x00007ff68d6d0846 in ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 #10 0x00007ff68d6d0873 in std::terminate() () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 #11 0x00007ff68d6d09b6 in __cxa_rethrow () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 #12 0x00007ff68e778b6c in QMetaObject::activate (sender=0x7ff67c8c4b70, m=<optimized out>, local_signal_index=<optimized out>, argv=0x0) at kernel/qobject.cpp:3576 #13 0x00007ff68e6ffffb in QProcessPrivate::_q_canReadStandardOutput (this=0x7ff674005030) at io/qprocess.cpp:915 #14 0x00007ff68e73f076 in QProcessPrivate::waitForFinished (this=0x7ff674005030, msecs=-1) at io/qprocess_unix.cpp:1245 #15 0x00007ff68e6f948e in QProcess::waitForFinished (this=0x7ff67c8c4b70, msecs=-1) at io/qprocess.cpp:1759 #16 0x00007ff68f62fe9a in ?? () from /usr/lib/libpartitionmanagerprivate.so #17 0x00007ff68f6300ba in ?? () from /usr/lib/libpartitionmanagerprivate.so #18 0x00007ff68f64f099 in ?? () from /usr/lib/libpartitionmanagerprivate.so #19 0x00007ff68f645174 in ?? () from /usr/lib/libpartitionmanagerprivate.so #20 0x00007ff68f6345ec in ?? () from /usr/lib/libpartitionmanagerprivate.so #21 0x00007ff68f622d2a in ?? () from /usr/lib/libpartitionmanagerprivate.so #22 0x00007ff68e664fcb in QThreadPrivate::start (arg=0x1ea1828) at thread/qthread_unix.cpp:298 #23 0x00007ff68b3c7e9a in start_thread (arg=0x7ff67c8c5700) at pthread_create.c:308 #24 0x00007ff68d13a4bd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #25 0x0000000000000000 in ?? () Thread 1 (Thread 0x7ff68faaf840 (LWP 4123)): #0 0x00007ff68d12d0bd in read () at ../sysdeps/unix/syscall-template.S:82 #1 0x00007ff68982088f in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x00007ff6897e5abd in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x00007ff6897e5f96 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x00007ff6897e6124 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x00007ff68e7933bf in QEventDispatcherGlib::processEvents (this=0x1d314b0, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #6 0x00007ff68db8ed5e in QGuiEventDispatcherGlib::processEvents (this=<optimized out>, flags=...) at kernel/qguieventdispatcher_glib.cpp:204 #7 0x00007ff68e762c82 in QEventLoop::processEvents (this=<optimized out>, flags=...) at kernel/qeventloop.cpp:149 #8 0x00007ff68e762ed7 in QEventLoop::exec (this=0x7fff271959a0, flags=...) at kernel/qeventloop.cpp:204 #9 0x00007ff68e767f67 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1148 #10 0x000000000040109a in ?? () #11 0x00007ff68d06976d in __libc_start_main (main=0x400f10, argc=1, ubp_av=0x7fff27195b88, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fff27195b78) at libc-start.c:226 #12 0x0000000000401185 in _start () Reported using DrKonqi
Thanks for reporting this crash. Can you please install debug symbols and post a new backtrace with those?
Le 06/06/2012 19:43, Volker Lanz a écrit : > https://bugs.kde.org/show_bug.cgi?id=301285 > > --- Comment #1 from Volker Lanz<vl@fidra.de> --- > Thanks for reporting this crash. > > Can you please install debug symbols and post a new backtrace with those? > I tried to install those proposed by the crash assistant but it told me that there wasn't any. I'll try again tomorow and post a new backtrace. Thanks
Le 06/06/2012 19:43, Volker Lanz a écrit : > https://bugs.kde.org/show_bug.cgi?id=301285 > > --- Comment #1 from Volker Lanz<vl@fidra.de> --- > Thanks for reporting this crash. > > Can you please install debug symbols and post a new backtrace with those? > I just made another test. Same pb. Debuging symb are unavailable. What should I do?
Please contact your distro's support channels and check with them how debug symbols are installed in this case. Without those, unfortunately, the backtrace is meaningless and I can't even start to investigate the problem.
Set report status based upon comment #4
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 set the bug status 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!
Dear Bug Submitter, 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!