If you "clone" your hard drive with something like rsync that tries to be smart about ownership of files, then you might be running into problems because of incorrect ownership of files on the cloned drive that snowball into problems with network manager. Eg, I cloned a hard drive with rsync via an install CD using "rsync -avH ...". Well, rsync looked at /etc/passwd and /etc/group of the install CD and setup the ownership of various things wrong, including /lib/dbus-1.0/dbus-daemon- launch-helper-- which prevented network-manager from starting correctly (this was seen in /var/log/syslog). After doing the initial rsync, you must chroot into the mounted disk and perform the rsync again, to get the proper permissions. Hope this helps for those people who cloned the drive and ran into this problem....
-- NM 0.7 sets hostname to localhost.localdomain instead of what is in /etc/hostname https://bugs.launchpad.net/bugs/276253 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
