Bug 313410 - can't delete ntfs partition on usb flash 16GB
Summary: can't delete ntfs partition on usb flash 16GB
Status: RESOLVED WORKSFORME
Alias: None
Product: partitionmanager
Classification: Applications
Component: general (other bugs)
Version First Reported In: 1.0.3
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Volker Lanz
URL:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2013-01-17 15:48 UTC by adil21
Modified: 2018-10-27 03:36 UTC (History)
0 users

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description adil21 2013-01-17 15:48:05 UTC
Application: partitionmanager-bin (1.0.3)
KDE Platform Version: 4.7.4 (4.7.4)
Qt Version: 4.7.4
Operating System: Linux 3.0.0-17-generic i686
Distribution: Ubuntu 11.10

-- Information about the crash:
- What I was doing when the application crashed:
Just try to delete partition and create another fat32 partition. Have tried to do this under windows xp and it can't format usb flash with the message "Usb flash is read-only"

The crash can be reproduced every time.

-- Backtrace:
Application: Управление разделами KDE (partitionmanager-bin), signal: Segmentation fault
[Current thread is 1 (Thread 0xb77bb760 (LWP 2786))]

Thread 2 (Thread 0xb4f19b70 (LWP 2897)):
#0  0x00187416 in __kernel_vsyscall ()
#1  0x00f04bbe in poll () from /lib/i386-linux-gnu/libc.so.6
#2  0x060ef34b in g_poll () from /lib/i386-linux-gnu/libglib-2.0.so.0
#3  0x060e0896 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#4  0x060e0c2a in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0
#5  0x00d2fb37 in QEventDispatcherGlib::processEvents (this=0x86cb6f8, flags=...) at kernel/qeventdispatcher_glib.cpp:424
#6  0x00d001dd in QEventLoop::processEvents (this=0xb4f19260, flags=...) at kernel/qeventloop.cpp:149
#7  0x00d00421 in QEventLoop::exec (this=0xb4f19260, flags=...) at kernel/qeventloop.cpp:201
#8  0x00c0390b in QThread::exec (this=0x86b7720) at thread/qthread.cpp:498
#9  0x00ce0e2d in QInotifyFileSystemWatcherEngine::run (this=0x86b7720) at io/qfilesystemwatcher_inotify.cpp:248
#10 0x00c067b3 in QThreadPrivate::start (arg=0x86b7720) at thread/qthread_unix.cpp:331
#11 0x00a18d31 in start_thread () from /lib/i386-linux-gnu/libpthread.so.0
#12 0x00f1387e in clone () from /lib/i386-linux-gnu/libc.so.6
Backtrace stopped: Not enough registers or memory available to unwind further

Thread 1 (Thread 0xb77bb760 (LWP 2786)):
[KCrash Handler]
#7  0x00b50b4a in PartitionManagerWidget::selectedPartition() () from /usr/lib/libpartitionmanagerprivate.so
#8  0x00b51234 in PartitionManagerWidget::enableActions() () from /usr/lib/libpartitionmanagerprivate.so
#9  0x00b58d32 in PartitionManagerWidget::on_m_PartTableWidget_itemSelectionChanged(PartWidget*) () from /usr/lib/libpartitionmanagerprivate.so
#10 0x00af3c93 in PartitionManagerWidget::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/libpartitionmanagerprivate.so
#11 0x00d07b7d in metacall (argv=0xbfb0e6b8, idx=36, cl=QMetaObject::InvokeMetaMethod, object=0x8613d68) at kernel/qmetaobject.cpp:237
#12 QMetaObject::metacall (object=0x8613d68, cl=QMetaObject::InvokeMetaMethod, idx=36, argv=0xbfb0e6b8) at kernel/qmetaobject.cpp:232
#13 0x00d16a6a in QMetaObject::activate (sender=0x8645998, m=0xb983bc, local_signal_index=0, argv=0xbfb0e6b8) at kernel/qobject.cpp:3278
#14 0x00af35e5 in ?? () from /usr/lib/libpartitionmanagerprivate.so
#15 0x00b3da24 in ?? () from /usr/lib/libpartitionmanagerprivate.so
#16 0x00b3e248 in ?? () from /usr/lib/libpartitionmanagerprivate.so
#17 0x00b5095e in PartitionManagerWidget::on_m_TreePartitions_currentItemChanged(QTreeWidgetItem*, QTreeWidgetItem*) () from /usr/lib/libpartitionmanagerprivate.so
#18 0x00af3c16 in PartitionManagerWidget::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/libpartitionmanagerprivate.so
#19 0x00d07b7d in metacall (argv=0xbfb0e874, idx=32, cl=QMetaObject::InvokeMetaMethod, object=0x8613d68) at kernel/qmetaobject.cpp:237
#20 QMetaObject::metacall (object=0x8613d68, cl=QMetaObject::InvokeMetaMethod, idx=32, argv=0xbfb0e874) at kernel/qmetaobject.cpp:232
#21 0x00d16a6a in QMetaObject::activate (sender=0x86399c0, m=0x1a9c614, local_signal_index=8, argv=0xbfb0e874) at kernel/qobject.cpp:3278
#22 0x0175a5dd in QTreeWidget::currentItemChanged (this=0x86399c0, _t1=0x8942f08, _t2=0x0) at .moc/release-shared/moc_qtreewidget.cpp:256
#23 0x0175a6a2 in QTreeWidgetPrivate::_q_emitCurrentItemChanged (this=0x8674440, current=..., previous=...) at itemviews/qtreewidget.cpp:2287
#24 0x0176263c in QTreeWidget::qt_metacall (this=0x86399c0, _c=QMetaObject::InvokeMetaMethod, _id=23, _a=0xbfb0e9c4) at .moc/release-shared/moc_qtreewidget.cpp:157
#25 0x00d07b7d in metacall (argv=0xbfb0e9c4, idx=111, cl=QMetaObject::InvokeMetaMethod, object=0x86399c0) at kernel/qmetaobject.cpp:237
#26 QMetaObject::metacall (object=0x86399c0, cl=QMetaObject::InvokeMetaMethod, idx=111, argv=0xbfb0e9c4) at kernel/qmetaobject.cpp:232
#27 0x00d16a6a in QMetaObject::activate (sender=0x8672848, m=0x1a9bd68, local_signal_index=1, argv=0xbfb0e9c4) at kernel/qobject.cpp:3278
#28 0x01735b4d in QItemSelectionModel::currentChanged (this=0x8672848, _t1=..., _t2=...) at .moc/release-shared/moc_qitemselectionmodel.cpp:159
#29 0x01735ccc in QItemSelectionModel::setCurrentIndex (this=0x8672848, index=..., command=...) at itemviews/qitemselectionmodel.cpp:1169
#30 0x016d75fc in QAbstractItemView::focusInEvent (this=0x86399c0, event=0xbfb0f05c) at itemviews/qabstractitemview.cpp:2110
#31 0x011a0514 in QWidget::event (this=0x86399c0, event=0xbfb0f05c) at kernel/qwidget.cpp:8404
#32 0x015a5285 in QFrame::event (this=0x86399c0, e=0xbfb0f05c) at widgets/qframe.cpp:557
#33 0x01639354 in QAbstractScrollArea::event (this=0x86399c0, e=0xbfb0f05c) at widgets/qabstractscrollarea.cpp:996
#34 0x016dc19c in QAbstractItemView::event (this=0x86399c0, event=0xbfb0f05c) at itemviews/qabstractitemview.cpp:1564
#35 0x017587ac in QTreeWidget::event (this=0x86399c0, e=0xbfb0f05c) at itemviews/qtreewidget.cpp:3453
#36 0x01145d84 in notify_helper (e=0xbfb0f05c, receiver=0x86399c0, this=0x8548c38) at kernel/qapplication.cpp:4486
#37 QApplicationPrivate::notify_helper (this=0x8548c38, receiver=0x86399c0, e=0xbfb0f05c) at kernel/qapplication.cpp:4458
#38 0x0114b1d8 in QApplication::notify (this=0x8548c38, receiver=0x86399c0, e=0xbfb0f05c) at kernel/qapplication.cpp:4451
#39 0x00638971 in KApplication::notify (this=0xbfb0f7e4, receiver=0x86399c0, event=0xbfb0f05c) at ../../kdeui/kernel/kapplication.cpp:311
#40 0x00d0119e in QCoreApplication::notifyInternal (this=0xbfb0f7e4, receiver=0x86399c0, event=0xbfb0f05c) at kernel/qcoreapplication.cpp:787
#41 0x011444af in sendEvent (event=0xbfb0f05c, receiver=0x86399c0) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215
#42 QApplicationPrivate::setFocusWidget (focus=0x86399c0, reason=Qt::ActiveWindowFocusReason) at kernel/qapplication.cpp:2261
#43 0x01192b41 in QWidget::setFocus (this=0x86399c0, reason=Qt::ActiveWindowFocusReason) at kernel/qwidget.cpp:6391
#44 0x01149e30 in QApplication::setActiveWindow (act=0x91f82a0) at kernel/qapplication.cpp:2659
#45 0x011d2459 in QApplication::x11ProcessEvent (this=0xbfb0f7e4, event=0xbfb0f46c) at kernel/qapplication_x11.cpp:3612
#46 0x011fe28c in x11EventSourceDispatch (s=0x854c900, callback=0, user_data=0x0) at kernel/qguieventdispatcher_glib.cpp:146
#47 0x060e025f in g_main_context_dispatch () from /lib/i386-linux-gnu/libglib-2.0.so.0
#48 0x060e0990 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#49 0x060e0c2a in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0
#50 0x00d2fada in QEventDispatcherGlib::processEvents (this=0x8531be0, flags=...) at kernel/qeventdispatcher_glib.cpp:422
#51 0x011fde7a in QGuiEventDispatcherGlib::processEvents (this=0x8531be0, flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#52 0x00d001dd in QEventLoop::processEvents (this=0xbfb0f774, flags=...) at kernel/qeventloop.cpp:149
#53 0x00d00421 in QEventLoop::exec (this=0xbfb0f774, flags=...) at kernel/qeventloop.cpp:201
#54 0x00d0519d in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1064
#55 0x01143924 in QApplication::exec () at kernel/qapplication.cpp:3760
#56 0x08048d30 in ?? ()
#57 0x00e55113 in __libc_start_main () from /lib/i386-linux-gnu/libc.so.6
#58 0x08048df9 in _start ()

Possible duplicates by query: bug 255021.

Reported using DrKonqi
Comment 1 Volker Lanz 2013-01-18 07:40:58 UTC
Thank you for taking the time and making the effort to report this issue.

Can you install debug symbols and post a backtrace with those installed? The backtrace as it is now doesn't really tell us where the crash occurs.

What's the exact point where it crashes? I imagine (and deduce from you bug title) there's already an NTFS partition on the stick when you start working with it, so it must go something like this:

1. Run KDE Partition Manager.
2. Click on the device
3. Click on the exisiting partition
4. Select "delete" action
5. Click on the unallocated space.
6. Select "create new" action
7. Pick FAT32 from the dialog's drop down menu of file systems.
8. Close the dialog with "ok"
9. Apply operations

Now, where exacty does the crash occur? 

If you're able to fill me in on these small missing details I might have a chane of diagnosing what's going on.

Thank you.
Comment 2 adil21 2013-01-18 08:29:25 UTC
Hi, Lanz. Later I'll install debug symbols, now I hava no time on it. Yes, you are right, there's already an NTFS partition on the stick. I tried just select 'delete ntfs partition' action, then apply operation. And the error 'usb flash is read-only' (in russian) occurs.

18.01.2013, 11:41, "Volker Lanz" <vl@fidra.de>:
> https://bugs.kde.org/show_bug.cgi?id=313410
>
> --- Comment #1 from Volker Lanz <vl@fidra.de> ---
> Thank you for taking the time and making the effort to report this issue.
>
> Can you install debug symbols and post a backtrace with those installed? The
> backtrace as it is now doesn't really tell us where the crash occurs.
>
> What's the exact point where it crashes? I imagine (and deduce from you bug
> title) there's already an NTFS partition on the stick when you start working
> with it, so it must go something like this:
>
> 1. Run KDE Partition Manager.
> 2. Click on the device
> 3. Click on the exisiting partition
> 4. Select "delete" action
> 5. Click on the unallocated space.
> 6. Select "create new" action
> 7. Pick FAT32 from the dialog's drop down menu of file systems.
> 8. Close the dialog with "ok"
> 9. Apply operations
>
> Now, where exacty does the crash occur?
>
> If you're able to fill me in on these small missing details I might have a
> chane of diagnosing what's going on.
>
> Thank you.
>
> --
> You are receiving this mail because:
> You reported the bug.
Comment 3 Volker Lanz 2013-01-18 10:09:08 UTC
Can you also provide a screenshot of that error, please? Ideally with the language set to English? (See Help Menu)
Comment 4 Andrew Crouthamel 2018-09-24 02:16:37 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 5 Andrew Crouthamel 2018-10-27 03:36:59 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!