Bug 266156

Summary:	partitionmanager crash on scanning hfs+ partition
Product:	[Applications] partitionmanager	Reporter:	teak <logicpop+bugs.kde>
Component:	general	Assignee:	Volker Lanz <vl>
Status:	RESOLVED UPSTREAM
Severity:	crash
Priority:	NOR
Version First Reported In:	1.0.3
Target Milestone:	---
Platform:	Ubuntu
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description teak 2011-02-12 19:46:19 UTC

Application: partitionmanager-bin (1.0.3)
KDE Platform Version: 4.5.1 (KDE 4.5.1)
Qt Version: 4.7.0
Operating System: Linux 2.6.35-26-generic i686
Distribution: Ubuntu 10.10

-- Information about the crash:
- What I was doing when the application crashed:
opening partitionmanager. seems to crash only when my hfs+ usb drive is attached.
- Custom settings of the application:
hfs+ usb drive

The crash can be reproduced every time.

-- Backtrace:
Application: KDE Partition Manager (partitionmanager-bin), signal: Aborted
[Current thread is 1 (Thread 0xb7749a80 (LWP 11043))]

Thread 2 (Thread 0xb7495b70 (LWP 11046)):
#0  0x0021f416 in __kernel_vsyscall ()
#1  0x043ebdf6 in poll () from /lib/libc.so.6
#2  0x03a71a1b in g_poll () from /lib/libglib-2.0.so.0
#3  0x03a6443c in ?? () from /lib/libglib-2.0.so.0
#4  0x03a64ba7 in g_main_loop_run () from /lib/libglib-2.0.so.0
#5  0x0743c9c4 in ?? () from /usr/lib/libgio-2.0.so.0
#6  0x03a8b48f in ?? () from /lib/libglib-2.0.so.0
#7  0x00bc0cc9 in start_thread () from /lib/libpthread.so.0
#8  0x043fa69e in clone () from /lib/libc.so.6

Thread 1 (Thread 0xb7749a80 (LWP 11043)):
[KCrash Handler]
#7  0x0021f416 in __kernel_vsyscall ()
#8  0x04354941 in raise () from /lib/libc.so.6
#9  0x04357e42 in abort () from /lib/libc.so.6
#10 0x00b56968 in ped_assert () from /lib/libparted.so.0
#11 0x00b605e6 in ped_geometry_read () from /lib/libparted.so.0
#12 0x00b80831 in hfsplus_probe () from /lib/libparted.so.0
#13 0x00b583dc in ped_file_system_probe_specific () from /lib/libparted.so.0
#14 0x00b589d1 in ped_file_system_probe () from /lib/libparted.so.0
#15 0x00b91e7f in ?? () from /lib/libparted.so.0
#16 0x00b920af in ?? () from /lib/libparted.so.0
#17 0x00b5f7d5 in ped_disk_new () from /lib/libparted.so.0
#18 0x00c1f38c in LibParted::scanDevices (this=0x96f0428, ostack=...) at /build/buildd/partitionmanager-1.0.3/src/core/libparted.cpp:308
#19 0x00c6c31c in PartitionManagerWidget::scanDevices (this=0x96f0408) at /build/buildd/partitionmanager-1.0.3/src/gui/partitionmanagerwidget.cpp:292
#20 0x00c707b0 in PartitionManagerWidget::init (this=0x96f0408, coll=0x971fa58, config_name=...) at /build/buildd/partitionmanager-1.0.3/src/gui/partitionmanagerwidget.cpp:129
#21 0x00c811c1 in MainWindow::init (this=0x96afb70) at /build/buildd/partitionmanager-1.0.3/src/gui/mainwindow.cpp:66
#22 0x00c813bb in MainWindow::MainWindow (this=0x96afb70, parent=0x0, coll=0x0, __in_chrg=<value optimized out>, __vtt_parm=<value optimized out>) at /build/buildd/partitionmanager-1.0.3/src/gui/mainwindow.cpp:51
#23 0x08048e39 in main (argc=2, argv=0xbf8ffad4) at /build/buildd/partitionmanager-1.0.3/src/main.cpp:43

Reported using DrKonqi

Comment 1 Volker Lanz 2011-02-14 10:29:34 UTC

Thank you for the bug report.

It looks like this bug might in factz not be in KDE Partition Manager itself but in libparted. What happens when you run parted (the console application) while the drive is attached?

I would also suggest you install the debug package for libparted / parted.

Comment 2 teak 2011-02-14 13:54:14 UTC

(In reply to comment #1)
> Thank you for the bug report.
> 
> It looks like this bug might in factz not be in KDE Partition Manager itself
> but in libparted. What happens when you run parted (the console application)
> while the drive is attached?
> 
> I would also suggest you install the debug package for libparted / parted.

ah yes the same thing happens... the program crashes... here is the backtrace: 

Backtrace has 17 calls on stack:
  17: /lib/libparted.so.0(ped_assert+0x2a) [0x5f887a]
  16: /lib/libparted.so.0(ped_geometry_read+0x116) [0x6025e6]
  15: /lib/libparted.so.0(hfsplus_probe+0x3a1) [0x622831]
  14: /lib/libparted.so.0(ped_file_system_probe_specific+0x6c) [0x5fa3dc]
  13: /lib/libparted.so.0(ped_file_system_probe+0x81) [0x5fa9d1]
  12: /lib/libparted.so.0(+0x44e7f) [0x633e7f]
  11: /lib/libparted.so.0(+0x450af) [0x6340af]
  10: /lib/libparted.so.0(ped_disk_new+0x75) [0x6017d5]
  9: parted() [0x804db58]
  8: parted() [0x804ece3]
  7: parted() [0x804ddae]
  6: parted() [0x804ece3]
  5: parted() [0x804ddae]
  4: parted(interactive_mode+0x11a) [0x805582a]
  3: parted(main+0x9c) [0x80527ec]
  2: /lib/libc.so.6(__libc_start_main+0xe7) [0xd27ce7]
  1: parted() [0x804bbb1]
Aborted

Comment 3 Volker Lanz 2011-02-14 16:32:45 UTC

Thank you for taking the time to try this out. So the issue is definitely with libparted itself, not with KDE Partition Manager.

You might want to report the bug on the parted mailing list, bug-parted@gnu.org.

Comment 4 teak 2011-02-14 16:34:36 UTC

(In reply to comment #3)
> Thank you for taking the time to try this out. So the issue is definitely with
> libparted itself, not with KDE Partition Manager.
> 
> You might want to report the bug on the parted mailing list,
> bug-parted@gnu.org.

cheers thanks for your time...