grub-mount assert failure: *** glibc detected *** grub-mount: free(): invalid next size (fast): 0x084c39f0 ***
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| grub2 (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
Bug Description
I am sorry. I am poor at English. About a point, I installed mac os 10.7/Lion in my i mac computer. Mac os 10.6.8/snow leopard and ubuntu 11.04 has already been installed in that computer. A problem occurred after that was installed. It is indicated with "Unknown filesystem grub rescue" at the time of the start. Therefore it has just tried re-installation. It met this page,Launchpad.net. I am a real amateur. Please thank you for your cooperation though care is given. Incidentally as for bootloader. I am using rEfIt.
ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: grub-common 1.99~rc1-13ubuntu3
ProcVersionSign
Uname: Linux 2.6.38-8-generic i686
Architecture: i386
AssertionMessage: *** glibc detected *** grub-mount: free(): invalid next size (fast): 0x084c39f0 ***
Date: Sat Jul 30 12:50:05 2011
ExecutablePath: /usr/bin/grub-mount
LiveMediaBuild: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
ProcCmdline: grub-mount /dev/sda2 /var/lib/
ProcEnviron:
LANGUAGE=ja_JP:en
PATH=(custom, no user)
LANG=ja_JP.UTF-8
SHELL=/bin/bash
Signal: 6
SourcePackage: grub2
StacktraceTop:
__kernel_vsyscall ()
raise () from /lib/i386-
abort () from /lib/i386-
?? () from /lib/i386-
?? () from /lib/i386-
Title: grub-mount assert failure: *** glibc detected *** grub-mount: free(): invalid next size (fast): 0x084c39f0 ***
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
| Apport retracing service (apport) wrote This bug is a duplicate | #2 |
| visibility: | private → public |
| tags: | removed: need-i386-retrace |
Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #775377, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.