Changing boot flag with gparted destroys Win bootmgr and makes gparted crash on restart

Bug #727429 reported by magelan on 2011-03-01
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gparted (Ubuntu)

Bug Description

Binary package hint: gparted

1. I changed the boot flag using gparted, possibly another version than the one of the live disc.
2. On trying to execute gparted with the live disc again, it crashes after scanning the partitions for 5 seconds automatically.
3. On changing the boot flag to as it was before (using fdisk), the Windows 7 bootmgr (within a Truecrypt partition) is broken.

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: gparted 0.6.2-1ubuntu1
ProcVersionSignature: Ubuntu 2.6.35-22.33-generic
Uname: Linux 2.6.35-22-generic i686
Architecture: i386
Date: Tue Mar 1 21:21:49 2011
LiveMediaBuild: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
SourcePackage: gparted

magelan (magelan) wrote :
magelan (magelan) wrote :

1.I cannot report using Apport after this "Assertion" with the error, but the terminal says:

"sudo gparted
libparted : 2.3

glibmm-ERROR **:
unhandled exception (type std::exception) in signal handler:
what: basic_string::_S_create

Aborted (core dumped)

2. Bootmgr could not be booted by the truecrypt loader (after changing the boot flag!), but it works after a decryption.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers