I, too, am getting these errors. Both in Karmic Beta, and I also got
them in Alpha (Daily)
The best solution (temporary work-around) I can give you for the moment,
is to
sudo killall gconfd-2
and then try to do whatever you were doing again. That will
automatically open a fresh instance of gco
** Attachment added: "CoreDump.gz"
http://launchpadlibrarian.net/32585230/CoreDump.gz
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/32585231/Dependencies.txt
** Attachment added: "Disassembly.txt"
http://launchpadlibrarian.net/32585233/Disassembly.txt
** Attachm
I am having this same exact problem with Karmic Alpha 6 (daily, actually). I
have my install on an LVM2, so the desktop live cd is not an option. My boot
partition is not on the LVM, however.
I can try to install it on any partition, and I still get the same, identical
error. It also fails whe
got this while upgrading to Karmic Beta from a working Jaunty install
--
hald-addon-ipw-killswitch crashed with SIGSEGV in __libc_start_main()
https://bugs.launchpad.net/bugs/433186
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubu
Got this while upgrading from a perfectly working Jaunty install (in-
place, update-manager -d) to Karmic Beta
--
package memtest86+ 2.11-3ubuntu4 failed to install/upgrade: subprocess new
post-removal script returned error exit status 2
https://bugs.launchpad.net/bugs/447810
You received this b
** Changed in: grub-installer (Ubuntu)
Status: Fix Released => Fix Committed
--
grub-installer breaks on disks with dmraid metadata but only one disk
https://bugs.launchpad.net/bugs/444583
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ub
Public bug reported:
Binary package hint: grub2
This is a segfault caused by update-grub due to lvm / dev mapper errors
I've had it before when my dm-raid was degraded and I was using lvm2 on top of
it.
Fixing the drive / lvm errors corrected the problem before.
Now it's breaking a 9.10 mail se
** Attachment added: "AptOrdering.txt"
http://launchpadlibrarian.net/36955039/AptOrdering.txt
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/36955040/Dependencies.txt
** Attachment added: "Dmesg.txt"
http://launchpadlibrarian.net/36955041/Dmesg.txt
** Attachment
That definitely isn't solving mine.
The only thing that has worked for me is to boot into an older OS (or chroot
into it) where I had an older version of grub2 (grub-pc) installed.
That version recognizes my mdadm raid devices and lvm2 devices just fine, and
will actually work.
The only way I c
I hope I'm not out of line posting this here... but here's some more
information on this:
Hopefully it will help those who are still having similar issues...
Here are some similar issues (or some may be duplicates?) :
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=550682
http://www.mail-archiv
Mine ended up being the RAID-0 mdadm device that was a physical volume in my
LVM2 Volume Group.
again see
When I got everything migrated off of it, the Ubuntu Karmic Alternate CD (Beta)
installed grub2 with no segfaults.
I'm guessing the problem was how grub-probe detected the /dev/md0 segment
11 matches
Mail list logo
