Bug 271900

Summary:	KDE Partition crashes on start up on mis-formated USB
Product:	[Applications] partitionmanager	Reporter:	OsamaK <osamak.wfm>
Component:	general	Assignee:	Volker Lanz <vl>
Status:	RESOLVED UPSTREAM
Severity:	crash
Priority:	NOR
Version First Reported In:	1.0.3
Target Milestone:	---
Platform:	Fedora RPMs
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description OsamaK 2011-04-28 07:11:02 UTC

Application: partitionmanager-bin (1.0.3)
KDE Platform Version: 4.6.2 (4.6.2)
Qt Version: 4.7.2
Operating System: Linux 2.6.35.12-libre.88.fc14.i686 i686
Distribution (Platform): Fedora RPMs

-- Information about the crash:
- What I was doing when the application crashed:
I followed several instructions on how to create a Live USB for Fedora from this how-to page:
https://fedoraproject.org/wiki/FedoraLiveCD/USBHowTo
I ended up with what seems to be a USB with two partitions on /dev/sdb and /dev/sdb1.
When I plug that USB, KDE Partition crashes.

The crash can be reproduced every time.

-- Backtrace:
Application: KDE Partition Manager (partitionmanager-bin), signal: Aborted
[KCrash Handler]
#5  0x004bc416 in __kernel_vsyscall ()
#6  0x002032f1 in raise (sig=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
#7  0x00204d5e in abort () at abort.c:92
#8  0x07856ca8 in ped_assert (cond_text=0x78ad986 "head_size <= 63", file=0x78ad93e "dos.c", line=661, function=0x78adcc9 "probe_partition_for_geom") at debug.c:112
#9  0x0788d91f in probe_partition_for_geom (part=0x8370d78, bios_geom=0xbfae0d54) at dos.c:661
#10 0x0788e607 in partition_probe_bios_geometry (part=<value optimized out>, bios_geom=0xbfae0d54) at dos.c:699
#11 0x07890fe7 in msdos_partition_align (part=0x8370d78, constraint=0x8371550) at dos.c:2079
#12 0x0785b2f2 in _partition_align (part=<value optimized out>, constraint=<value optimized out>) at disk.c:922
#13 0x0785e7cb in ped_disk_add_partition (disk=0x8383f28, part=0x8370d78, constraint=0x83836d8) at disk.c:2021
#14 0x0788ff31 in read_table (disk=0x8383f28, sector=0, is_extended_table=0) at dos.c:935
#15 0x07890540 in msdos_read (disk=0x8383f28) at dos.c:987
#16 0x0785ec95 in ped_disk_new (dev=0x837d248) at disk.c:200
#17 0x020b6a4a in LibParted::scanDevices (this=0x82a9fc8, ostack=...) at /usr/src/debug/partitionmanager-1.0.3/src/core/libparted.cpp:308
#18 0x0210c84f in PartitionManagerWidget::scanDevices (this=0x82a9fa8) at /usr/src/debug/partitionmanager-1.0.3/src/gui/partitionmanagerwidget.cpp:292
#19 0x0210cf61 in PartitionManagerWidget::init (this=0x82a9fa8, coll=0x835a1f0, config_name=...) at /usr/src/debug/partitionmanager-1.0.3/src/gui/partitionmanagerwidget.cpp:129
#20 0x02124fd2 in MainWindow::init (this=0x82a94d0) at /usr/src/debug/partitionmanager-1.0.3/src/gui/mainwindow.cpp:66
#21 0x021251ac in MainWindow::MainWindow (this=0x82a94d0, parent=0x0, coll=0x0, __in_chrg=<value optimized out>, __vtt_parm=<value optimized out>) at /usr/src/debug/partitionmanager-1.0.3/src/gui/mainwindow.cpp:51
#22 0x08048e77 in main (argc=) at /usr/src/debug/partitionmanager-1.0.3/src/main.cpp:43

Reported using DrKonqi

Comment 1 Volker Lanz 2011-04-30 13:52:07 UTC

Thank you for your bug report.

What happens is that libparted, the library KDE Partition Manager uses for many of its low level partitioning tasks, sees the device and finds it so far outside what it considers valid that it aborts the application with an internal error.

It is of course debatable if this should happen or not, but in any event it's something outside of KDE Partition Manager's control.

You will probably find that Parted (the command line frontend for libparted) will exhibit the same behaviour with the device in question.

You could file this bug report against libparted itself, which is here: http://www.gnu.org/software/parted/