I'm getting exactly the same behavior following todays update.
As of yesterday, I was hitting bug
https://bugs.launchpad.net/network-manager/+bug/256054, but on reboot this
morning, my manually defined IP settings where correctly remembered.
Unfortunately though, the networking isn't working and
I tried ensuring that there are no duplicate UUID's (even on the softraid
devices). The problem remains though.
Thanks for your assistance though.
--
Cannot start from dmraid device anymore
https://bugs.launchpad.net/bugs/141435
You received this bug notification because you are a member of Ubu
Here's the file for the new kernel.
** Attachment added: "2.6.22-14.dmraid.lst"
http://launchpadlibrarian.net/10110418/2.6.22-14.dmraid.lst
--
Cannot start from dmraid device anymore
https://bugs.launchpad.net/bugs/141435
You received this bug notification because you are a member of Ubuntu
B
I've just ran: "dmraid -tay - - -f nvidia" on both kernels.
Interestingly, it looks like the devices are getting discovered
incorrectly in the 2.6.22 kernel as /sde and /sdf - instead of /sda and
/sdb !
** Attachment added: "2.6.20-16.dmraid.lst"
http://launchpadlibrarian.net/10110417
AHh - think I've fixed it. I'd appreciate it if someone could check
that what I've done makes sense though !!
I noticed on reboot, that the "blkid" command was showing the problem devices
as TYPE-mdraid, but with the same UUID's
Looking at the mdadm utility, I noticed that you could use the Asse
*** This bug is a duplicate of bug 141435 ***
https://bugs.launchpad.net/bugs/141435
I'm having the same problem with a Nvidia Fakeraid configuration. Under
Feisty (with kernel 2.6.20-16) during boot, two devices are discovered
under /dev/mapper :
/dev/mapper/nvidia_blah
/dev/mapper/nvidia_b
I'm having a similar problem with a Nvidia Fakeraid configuration. Under
Feisty (with kernel 2.6.20-16) during boot, two devices are discovered
under /dev/mapper :
/dev/mapper/nvidia_blah
/dev/mapper/nvidia_blah1
However, after upgrading to Gutsy, these are missing. Normally, these are
coupled t
Could you detail step-by-step how you determined which UUID related to
which device, and how you altered them ?
--
Cannot start from dmraid device anymore
https://bugs.launchpad.net/bugs/141435
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact fo
Thanks - I can see the duplicates now:
/dev/sda1: UUID="32507eee-9883-4143-bae3-58762e4d4ae0" SEC_TYPE="ext2"
TYPE="ext3"
/dev/sda2: UUID="06e176bf-1b0a-4616-baf0-f6f9f4965639" SEC_TYPE="ext2"
TYPE="ext3"
/dev/sdb1: UUID="32507eee-9883-4143-bae3-58762e4d4ae0" SEC_TYPE="ext2"
TYPE="ext3"
/dev
Ok, I ran in the "tune2fs -U random /dev/sda1", and the two partitions
now look like:
/dev/sda1: UUID="b34efba6-b725-4343-8808-0c4fd1b670e4" SEC_TYPE="ext2"
TYPE="ext3"
/dev/sdb1: UUID="32507eee-9883-4143-bae3-58762e4d4ae0" SEC_TYPE="ext2"
TYPE="ext3"
Separate UUID's. However, (on reboot) the
Yep - I've just been hit with the same problem ...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/847664
Title:
dependency problem with virtual package compiz-core-
abiversion-20110703
To manage n
I'm also getting this error when running software-center from a terminal
window. (I was trying to use a terminal window because software-center
won't launch for me at all from Unity!). I've discovered that it will
run sucessfully from a terminal as sudo though, so must be a permission
error somew
Fixed for me also - I guess we all updated "too quickly" :-)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/847664
Title:
dependency problem with virtual package compiz-core-
abiversion-20110703
I also see this problem with 11.04 and Nvidia 8600GTS on dual-screen config.
Nvidia driver version: 275.09.07
I also notice that the screen corruption appears to affect the indicator
applets - corrupting some of them (i.e. hp-systray)
This is intermittent however.
--
You received this bug notif
14 matches
Mail list logo
