Changing boot flag with gparted destroys Win bootmgr and makes gparted crash on restart
Bug #727429 reported by
magelan
This bug report is a duplicate of:
Bug #617885: gparted crash at start: glibmm-ERROR **.
Edit
Remove
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| gparted (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
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
ProcVersionSign
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)
ProcEnviron:
LANG=de_DE.UTF-8
SHELL=/bin/bash
SourcePackage: gparted
Revision history for this message
| magelan (magelan) wrote | #1 |
Revision history for this message
| magelan (magelan) wrote | #2 |
To post a comment you must log in.
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:
aborting...
Aborted (core dumped)
"
2. Bootmgr could not be booted by the truecrypt loader (after changing the boot flag!), but it works after a decryption.