I also ran into this problem. It was caused by bad permissions on /tmp, which somehow survived a reboot. chown root:root /tmp && chmod 777 /tmp fixed it. Ideally, the system shouldn't be throwing such an obscure error message, and the sanity check script shouldn't be silent (or return 0) when ran a second time.
-- There is a problem with the configuration server. (/usr/lib/libgconf2-4/gconf-sanity-check-2 exited with status 256) https://bugs.launchpad.net/bugs/269215 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
