I got the same error message on a virgin 10.04 AMD 64-bit quad core install, except I'm stuck in an apparently infinite can't login in loop when I click close on the error dialog.
I had added a seperate partition to mount as /tmp before the reboot from today's updates, so on a hunch I shutdown, removed its power, and let the system boot by dismissing the mount error dialog and gnome came up OK. Looks like some gconf state is being maintainted in /tmp across reboots. I thought this was bad practice as /tmp is supposed to be volitile. --wally. -- "gconf-sanity-check-2 exited with status 256" on log in https://bugs.launchpad.net/bugs/577545 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
