"gconf-sanity-check-2 exited with status 256" on log in
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gconf (Ubuntu) |
Confirmed
|
Low
|
Unassigned |
Bug Description
Binary package hint: gconf
I get the error message: "There is a problem with the configuration server. (/usr/lib/
This has been happening on all three of my computers since I upgraded to 10.04 LTS (using boht amd64 and i386 versions).
This is not caused by the permissions issues mentioned in bug #269215 as /etc/gconf/
Running "/usr/lib/
Attached is my .xsession-errors.
ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: libgconf2-4 2.28.1-0ubuntu1
ProcVersionSign
Uname: Linux 2.6.32-22-generic x86_64
NonfreeKernelMo
Architecture: amd64
Date: Sat May 8 11:18:30 2010
ProcEnviron:
PATH=(custom, user)
LANG=en_US.utf8
SHELL=/bin/bash
SourcePackage: gconf
tags: | added: iso-testing |
Changed in gconf (Ubuntu): | |
status: | New → Confirmed |
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.