Bug 291671 - Program fails to start when a specific drive (invalid partition table) is connected.
Summary: Program fails to start when a specific drive (invalid partition table) is con...
Status: RESOLVED UPSTREAM
Alias: None
Product: partitionmanager
Classification: Applications
Component: general (show other bugs)
Version: 1.0.3
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Volker Lanz
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-01-16 16:52 UTC by brawaga
Modified: 2024-03-21 04:11 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description brawaga 2012-01-16 16:52:53 UTC
Version:           1.0.3
OS:                Linux

I have no idea how to fix partition table, gparted crashes too.

Reproducible: Always

Steps to Reproduce:
Just running from menu.

Actual Results:  
Program crushes and offers to contact developers.

Expected Results:  
It should show window where I could perform needed actions.

I attach stacktrace here. I was offered by the program to install some debug packages, but I couldn't install them, so, only stacktrace is available.
--8<----cut here----8<----8<----cut here----8<----8<----cut here----8<--
Application: Управление разделами KDE (partitionmanager-bin), signal: Aborted
[KCrash Handler]
#5  0xb77d7424 in __kernel_vsyscall ()
#6  0xb6124941 in raise () from /lib/libc.so.6
#7  0xb6127e42 in abort () from /lib/libc.so.6
#8  0xb5e1e968 in ped_assert () from /lib/libparted.so.0
#9  0xb5e56337 in ?? () from /lib/libparted.so.0
#10 0xb5e57157 in ?? () from /lib/libparted.so.0
#11 0xb5e5844c in ?? () from /lib/libparted.so.0
#12 0xb5e23161 in ?? () from /lib/libparted.so.0
#13 0xb5e269f2 in ped_disk_add_partition () from /lib/libparted.so.0
#14 0xb5e59ea5 in ?? () from /lib/libparted.so.0
#15 0xb5e5a0af in ?? () from /lib/libparted.so.0
#16 0xb5e277d5 in ped_disk_new () from /lib/libparted.so.0
#17 0xb772038c in ?? () from /usr/lib/libpartitionmanagerprivate.so
#18 0xb776d31c in PartitionManagerWidget::scanDevices() () from /usr/lib/libpartitionmanagerprivate.so
#19 0xb77717b0 in PartitionManagerWidget::init(KActionCollection*, QString const&) () from /usr/lib/libpartitionmanagerprivate.so
#20 0xb77821c1 in MainWindow::init() () from /usr/lib/libpartitionmanagerprivate.so
#21 0xb77823bb in MainWindow::MainWindow(QWidget*, KActionCollection*) () from /usr/lib/libpartitionmanagerprivate.so
#22 0x08048e39 in _start ()
--8<----cut here----8<----8<----cut here----8<----8<----cut here----8<--
Comment 1 Volker Lanz 2012-01-16 23:41:46 UTC
Not much we can do about it. Backup all data and kill the partition table with fdisk or dd.
Comment 2 brawaga 2012-02-06 07:45:04 UTC
Thank you. I have already done it. For my luck, partition was accessible to copy files from it, and I had sufficient storage space. Just shocked a little at first, cause I was asked to help, not to destroy =)