[Bug 244591] Re: Cannot connect to ICQ ("The client version you are using is too old.")

** Changed in: pidgin (Ubuntu) Assignee: (unassigned) => Pidgin Developers (pidgin-developers) -- Cannot connect to ICQ ("The client version you are using is too old.") https://bugs.launchpad.net/bugs/244591 You received this bug notification because you are a member of Ubuntu Bugs, which is

[Bug 244591] Re: Cannot connect to ICQ ("The client version you are using is too old.")

patch makes libpurple mimic the exact version numbers sent by the official ICQ6 client ** Attachment added: "patch makes libpurple mimic the exact version numbers sent by the official ICQ6 client" http://launchpadlibrarian.net/15742714/pidgin-2.4.2-icq.patch ** Attachment removed: "patch make

[Bug 141435] Re: Cannot start from dmraid device anymore

dmraid works fine for me then no dublicate UUID (except swaps) takes place. -- 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 for Ubuntu. -- ubuntu-bugs mailing l

[Bug 141435] Re: Cannot start from dmraid device anymore

use tune2fs for ext3 e.g. $sudo tune2fs -U random /dev/sda1 -- 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 for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs

[Bug 141435] Re: Cannot start from dmraid device anymore

oops, mystype (xfs_admin for xfs partition, of course) $sudo xfs_admin -U 546ea841-093b-42ea-964a- /dev/sda3 you don't need to touch swaps -- Cannot start from dmraid device anymore https://bugs.launchpad.net/bugs/141435 You received this bug notification because you are a member of

[Bug 141435] Re: Cannot start from dmraid device anymore

try 'blkid' command to find out UUID use 'tune2fs' for ext3 filesystem, 'reiserfstune' for reiserfs filesystem, and 'xfs_admin' for xfs filesystem my sample looks like: $ blkid /dev/sda1: UUID="546ea841-093b-42ea-964a-3c2e5ff3a2f3" TYPE="swap" /dev/sda2: UUID="df8eb64d-41d3-4fa6-88b2-5d8163fe4db

[Bug 141435] Re: Cannot start from dmraid device anymore

my solution was to edit UUIDs of every filesystem partition included in dmraid/fakeraid devices, so i can boot livecd and /dev/mapper appears after dmraid install -- Cannot start from dmraid device anymore https://bugs.launchpad.net/bugs/141435 You received this bug notification because you are a

[Bug 140748] Re: Unable to boot after linux-image-2.6.22-11.33 rt or generic after upgrade

*** This bug is a duplicate of bug 141435 *** https://bugs.launchpad.net/bugs/141435 i solved this problem manuall by hand to change every dmraid filesystem UUID manually (this is not desync my fakeraid raid1 array), this issue caused udedv device-mapper error because it can't work with dublic

[Bug 141435] Re: Cannot start from dmraid device anymore

you need check with 'blkid' to find out you have duplicate UUID (!) of any in your fakeraid partitions, this is one you can't map your raid device with udevd, this is not EVMS, this is UDEV issue only with dublicated UUID included in your raid array devices -- Cannot start from dmraid device anym

[Bug 141435] Re: Cannot start from dmraid device anymore

i solved this problem manuall by hand to change every fakeraid filesystem UUID manually (this is not desync my fakeraid raid1 array), this issue caused udedv device-mapper error because it can't work with dublicated UUID of every your drive in raid array -- Cannot start from dmraid device anymore