Bug 238732 - crash in 1TB external HDD
Summary: crash in 1TB external HDD
Status: RESOLVED WORKSFORME
Alias: None
Product: partitionmanager
Classification: Applications
Component: general (other bugs)
Version First Reported In: 1.0.1
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Volker Lanz
URL:
Keywords: investigated, triaged
Depends on:
Blocks:
 
Reported: 2010-05-24 21:16 UTC by lepro
Modified: 2018-10-27 03:58 UTC (History)
0 users

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 lepro 2010-05-24 21:16:55 UTC
Application: partitionmanager-bin (1.0.1)
KDE Platform Version: 4.4.2 (KDE 4.4.2)
Qt Version: 4.6.2
Operating System: Linux 2.6.32-22-generic i686
Distribution: Ubuntu 10.04 LTS

-- Information about the crash:
crashed when I try to make new partition in a 1TB external HDD

The crash can be reproduced every time.

 -- Backtrace:
Application: Gestionnaire de partitions de KDE (partitionmanager-bin), signal: Aborted
[KCrash Handler]
#6  0x009bc422 in __kernel_vsyscall ()
#7  0x00230651 in raise () from /lib/tls/i686/cmov/libc.so.6
#8  0x00233a82 in abort () from /lib/tls/i686/cmov/libc.so.6
#9  0x001cf52f in __gnu_cxx::__verbose_terminate_handler() () from /usr/lib/libstdc++.so.6
#10 0x001cd465 in ?? () from /usr/lib/libstdc++.so.6
#11 0x001cd4a2 in std::terminate() () from /usr/lib/libstdc++.so.6
#12 0x001cd55b in __cxa_rethrow () from /usr/lib/libstdc++.so.6
#13 0x0494d4ae in QObject::event (this=0x91ad6c0, e=0xb4f00598) at kernel/qobject.cpp:1251
#14 0x0313e4dc in QApplicationPrivate::notify_helper (this=0x8e82c68, receiver=0x91ad6c0, e=0xb4f00598) at kernel/qapplication.cpp:4300
#15 0x0314505e in QApplication::notify (this=0xbfbb6bc4, receiver=0x91ad6c0, e=0xb4f00598) at kernel/qapplication.cpp:3704
#16 0x00f1af2a in KApplication::notify (this=0xbfbb6bc4, receiver=0x91ad6c0, event=0xb4f00598) at ../../kdeui/kernel/kapplication.cpp:302
#17 0x0493ca3b in QCoreApplication::notifyInternal (this=0xbfbb6bc4, receiver=0x91ad6c0, event=0xb4f00598) at kernel/qcoreapplication.cpp:704
#18 0x0493f473 in QCoreApplication::sendEvent (receiver=0x0, event_type=0, data=0x8e6f108) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215
#19 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x8e6f108) at kernel/qcoreapplication.cpp:1345
#20 0x0493f5dd in QCoreApplication::sendPostedEvents (receiver=0x0, event_type=0) at kernel/qcoreapplication.cpp:1238
#21 0x04968adf in QCoreApplication::sendPostedEvents (s=0x8e859c0) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:220
#22 postEventSourceDispatch (s=0x8e859c0) at kernel/qeventdispatcher_glib.cpp:276
#23 0x024915e5 in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#24 0x024952d8 in ?? () from /lib/libglib-2.0.so.0
#25 0x024954b8 in g_main_context_iteration () from /lib/libglib-2.0.so.0
#26 0x049685d5 in QEventDispatcherGlib::processEvents (this=0x8e6eca0, flags=...) at kernel/qeventdispatcher_glib.cpp:412
#27 0x031fe135 in QGuiEventDispatcherGlib::processEvents (this=0x8e6eca0, flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#28 0x0493b059 in QEventLoop::processEvents (this=0xbfbb6b54, flags=) at kernel/qeventloop.cpp:149
#29 0x0493b4aa in QEventLoop::exec (this=0xbfbb6b54, flags=...) at kernel/qeventloop.cpp:201
#30 0x0493f69f in QCoreApplication::exec () at kernel/qcoreapplication.cpp:981
#31 0x0313e577 in QApplication::exec () at kernel/qapplication.cpp:3579
#32 0x08048f8e in _start ()

Possible duplicates by query: bug 238709, bug 238652, bug 238589, bug 238367, bug 238188.

Reported using DrKonqi
Comment 1 Volker Lanz 2011-08-28 10:44:32 UTC
Thank you for the bug report.

Can you please re-try with the latest stable version, 1.0.3?

And if it still crashes, can you please give detailed steps to reproduce the crash?
Comment 2 Andrew Crouthamel 2018-09-22 01:46:34 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 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!
Comment 3 Andrew Crouthamel 2018-10-27 03:58:47 UTC
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!