Bug 287400

Summary: PartitionManager crashed after trying to format a USB drive that was previously prepared as a LiveUSB by dd (of if)
Product: [Applications] partitionmanager Reporter: Mathieu Tarral <mathux>
Component: generalAssignee: Volker Lanz <vl>
Status: RESOLVED NOT A BUG    
Severity: crash    
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Chakra   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Mathieu Tarral 2011-11-23 20:48:11 UTC
Application: partitionmanager-bin (1.0.60)
KDE Platform Version: 4.7.3 (4.7.3)
Qt Version: 4.7.4
Operating System: Linux 3.1-CHAKRA i686
Distribution: "Chakra Linux"

-- Information about the crash:
- What I was doing when the application crashed:

I created a LiveUSB using dd if = / of = / dev / sdX, and I wanted to format the same USB drive. so I recreated the partition table, the operation was successful, then I did format it FAT32 and PartitionManager crash

- Custom settings of the application:

I noticed that to create a liveusb with dd if = / of = / was that if we subsequently reconnects the same LiveUSB on a Linux computer, there are two devices that are recognized, the first being the key space and the second is a weird thing in UDF format (CD-ROM). I think it's waste of a copy of dd that are poorly managed after.

I have to go through Windows to format it correctly.

The crash can be reproduced every time.

-- Backtrace:
Application: KDE Partition Manager (partitionmanager-bin), signal: Segmentation fault
[Current thread is 1 (Thread 0xb4dee710 (LWP 6534))]

Thread 2 (Thread 0xb3c07b70 (LWP 6536)):
#0  0xb548cd00 in clock_gettime () from /lib/librt.so.1
#1  0xb625db35 in ?? () from /usr/lib/libQtCore.so.4
#2  0xb63302d6 in ?? () from /usr/lib/libQtCore.so.4
#3  0xb633062a in ?? () from /usr/lib/libQtCore.so.4
#4  0xb632ee73 in ?? () from /usr/lib/libQtCore.so.4
#5  0xb632ef0d in ?? () from /usr/lib/libQtCore.so.4
#6  0xb55d7a3e in g_main_context_prepare () from /usr/lib/libglib-2.0.so.0
#7  0xb55d88f3 in ?? () from /usr/lib/libglib-2.0.so.0
#8  0xb55d8fc4 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#9  0xb632f957 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#10 0xb630073d in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#11 0xb6300981 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#12 0xb62042cb in QThread::exec() () from /usr/lib/libQtCore.so.4
#13 0xb62e139d in ?? () from /usr/lib/libQtCore.so.4
#14 0xb6207123 in ?? () from /usr/lib/libQtCore.so.4
#15 0xb5b38cf7 in start_thread () from /lib/libpthread.so.0
#16 0xb5ff086e in clone () from /lib/libc.so.6

Thread 1 (Thread 0xb4dee710 (LWP 6534)):
[KCrash Handler]
#7  0xb7616b8b in Partition::sectorsUsed() const () from /usr/lib/libtribepartitionmanager.so
#8  0xb7663cff in ?? () from /usr/lib/libtribepartitionmanager.so
#9  0xb65c363e in QWidget::event(QEvent*) () from /usr/lib/libQtGui.so.4
#10 0xb6569764 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4
#11 0xb656ebb8 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4
#12 0xb70aad51 in KApplication::notify(QObject*, QEvent*) () from /usr/lib/libkdeui.so.5
#13 0xb63016fe in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/libQtCore.so.4
#14 0xb65c04eb in QWidgetPrivate::drawWidget(QPaintDevice*, QRegion const&, QPoint const&, int, QPainter*, QWidgetBackingStore*) () from /usr/lib/libQtGui.so.4
#15 0xb65c11e4 in QWidgetPrivate::paintSiblingsRecursive(QPaintDevice*, QList<QObject*> const&, int, QRegion const&, QPoint const&, int, QPainter*, QWidgetBackingStore*) ()
   from /usr/lib/libQtGui.so.4
#16 0xb65c0248 in QWidgetPrivate::drawWidget(QPaintDevice*, QRegion const&, QPoint const&, int, QPainter*, QWidgetBackingStore*) () from /usr/lib/libQtGui.so.4
#17 0xb65c11e4 in QWidgetPrivate::paintSiblingsRecursive(QPaintDevice*, QList<QObject*> const&, int, QRegion const&, QPoint const&, int, QPainter*, QWidgetBackingStore*) ()
   from /usr/lib/libQtGui.so.4
#18 0xb65c10aa in QWidgetPrivate::paintSiblingsRecursive(QPaintDevice*, QList<QObject*> const&, int, QRegion const&, QPoint const&, int, QPainter*, QWidgetBackingStore*) ()
   from /usr/lib/libQtGui.so.4
#19 0xb65c0248 in QWidgetPrivate::drawWidget(QPaintDevice*, QRegion const&, QPoint const&, int, QPainter*, QWidgetBackingStore*) () from /usr/lib/libQtGui.so.4
#20 0xb65c11e4 in QWidgetPrivate::paintSiblingsRecursive(QPaintDevice*, QList<QObject*> const&, int, QRegion const&, QPoint const&, int, QPainter*, QWidgetBackingStore*) ()
   from /usr/lib/libQtGui.so.4
#21 0xb65c10aa in QWidgetPrivate::paintSiblingsRecursive(QPaintDevice*, QList<QObject*> const&, int, QRegion const&, QPoint const&, int, QPainter*, QWidgetBackingStore*) ()
   from /usr/lib/libQtGui.so.4
#22 0xb65c10aa in QWidgetPrivate::paintSiblingsRecursive(QPaintDevice*, QList<QObject*> const&, int, QRegion const&, QPoint const&, int, QPainter*, QWidgetBackingStore*) ()
   from /usr/lib/libQtGui.so.4
#23 0xb65c10aa in QWidgetPrivate::paintSiblingsRecursive(QPaintDevice*, QList<QObject*> const&, int, QRegion const&, QPoint const&, int, QPainter*, QWidgetBackingStore*) ()
   from /usr/lib/libQtGui.so.4
#24 0xb65c10aa in QWidgetPrivate::paintSiblingsRecursive(QPaintDevice*, QList<QObject*> const&, int, QRegion const&, QPoint const&, int, QPainter*, QWidgetBackingStore*) ()
   from /usr/lib/libQtGui.so.4
#25 0xb65c10aa in QWidgetPrivate::paintSiblingsRecursive(QPaintDevice*, QList<QObject*> const&, int, QRegion const&, QPoint const&, int, QPainter*, QWidgetBackingStore*) ()
   from /usr/lib/libQtGui.so.4
#26 0xb65c0248 in QWidgetPrivate::drawWidget(QPaintDevice*, QRegion const&, QPoint const&, int, QPainter*, QWidgetBackingStore*) () from /usr/lib/libQtGui.so.4
#27 0xb67a501d in ?? () from /usr/lib/libQtGui.so.4
#28 0xb65b5e3b in QWidgetPrivate::syncBackingStore() () from /usr/lib/libQtGui.so.4
#29 0xb65c3fcf in QWidget::event(QEvent*) () from /usr/lib/libQtGui.so.4
#30 0xb69bdd7c in QMainWindow::event(QEvent*) () from /usr/lib/libQtGui.so.4
#31 0xb7186fc4 in KMainWindow::event(QEvent*) () from /usr/lib/libkdeui.so.5
#32 0xb71cf192 in KXmlGuiWindow::event(QEvent*) () from /usr/lib/libkdeui.so.5
#33 0xb6569764 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4
#34 0xb656ebb8 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4
#35 0xb70aad51 in KApplication::notify(QObject*, QEvent*) () from /usr/lib/libkdeui.so.5
#36 0xb63016fe in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/libQtCore.so.4
#37 0xb6304ee3 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib/libQtCore.so.4
#38 0xb630503c in QCoreApplication::sendPostedEvents(QObject*, int) () from /usr/lib/libQtCore.so.4
#39 0xb632f4c4 in ?? () from /usr/lib/libQtCore.so.4
#40 0xb55d8532 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#41 0xb55d8d10 in ?? () from /usr/lib/libglib-2.0.so.0
#42 0xb55d8fc4 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#43 0xb632f8fa in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#44 0xb661ca7a in ?? () from /usr/lib/libQtGui.so.4
#45 0xb630073d in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#46 0xb6300981 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#47 0xb63050ed in QCoreApplication::exec() () from /usr/lib/libQtCore.so.4
#48 0xb65675d4 in QApplication::exec() () from /usr/lib/libQtGui.so.4
#49 0x08048faa in ?? ()
#50 0xb5f37243 in __libc_start_main () from /lib/libc.so.6
#51 0x080490c9 in _start ()

Possible duplicates by query: bug 281900.

Reported using DrKonqi
Comment 1 Volker Lanz 2011-12-16 18:53:03 UTC
Thanks for the bug report.

If you can indeed reproduce the crash, please install debug symbols (the KDE crash manager should guide you through this) and post a meaningful backtrace.
Comment 2 Mathieu Tarral 2011-12-16 20:33:51 UTC
Thanks for interesting to this bug.

I'm sorry, but there is no partitonmanager-dbg package on Kubuntu.
Furthermore, I think I already have installed debuguage symbols with Dr. Konqi

Nevertheless,  I will try to reproduce the bug again and check for debuging symbols with the Dr. Konqi assistant.
Comment 3 admin 2012-02-13 05:30:16 UTC
I have experienced this crash, just as it is described in the title. I had a Live USB drive that was previously created with a DD command. I opened up the KDE partition manager and selected my USB drive /dev/sde. At this point the screen showed that partitionmanager it did not recognise the partition file system type. I went ahead and deleted the unrecognised partition and applied the queued operation. Everything went fine, and now I had unallocated space on /dev/sde. Proceeding, I created a new EXT4 partition to take up all of the unallocated space on the drive. As soon as I hit Apply, the computer crashes. I see a black screen (http://i.imgur.com/YMU0l.jpg) and I am unable to get back into KDE desktop. I had to take a snapshot with my camera and poweroff.
I am running LinuxMint 12 KDE(4.7.4)
Comment 4 Volker Lanz 2012-02-13 07:24:54 UTC
Thank you for your comment, admin.

What you're seeing is a kernel bug. The screenshot you took shows a kernel backtrace. This is not related to the issue Mathieu is seeing and is not a problem with KDE Partition Manager itself.

You should probably report this as a kernel bug to your distribution or to the Linux kernel mailing list.
Comment 5 Volker Lanz 2012-02-13 07:32:17 UTC
Mathieu:

Are you on Kubuntu or Chakra? You've specified you're using Chakra in your original report (and the backtrace shows their patched KDE Partition Manager library names), but are referring to Kubuntu now in your comment.

If there are no debug symbols for KDE Partition Manager on your distribution, please speak to them about that.

Also, you said you could reproduce this crash every time in your original report. Is this not the case?
Comment 6 Mathieu Tarral 2012-02-22 02:35:16 UTC
Today, I cannot reproduce the bug anymore. It seems to have been solved since I posted here.

Thanks to you.
Comment 7 Volker Lanz 2012-02-22 08:34:07 UTC
Setting the entry to fixed suggests code has been changed. Chaning resolution to invalid.