I had issue also
gconf-sanity-check-2 exited with status 256
problem was wrong /tmp directory permissions (for some reason wasn't
drwxrwxrwxt and owner wasn't root.root)
--
gconf-sanity-check-2 exits with code 256 on Xorg start
https://bugs.launchpad.net/bugs/383461
You received this bug
I also still have this issue. here's my setup:
m...@hobbes:~$ ls -l /etc/gconf/
total 20
drwxr-xr-x 2 root root 4096 2009-07-19 14:38 2
drwxr-xr-x 2 root root 4096 2009-04-23 18:15 gconf.xml.defaults
drwxr-xr-x 2 root root 4096 2006-10-25 15:31 gconf.xml.mandatory
drwxr-xr-x 2 root root 4096
Able to reproduce the in Karmic Alpha 2
(gconftool-2:6270): GConf-WARNING **: Failed to load source
xml:readonly:/etc/gconf/gconf.xml.system: Failed: Could not make
directory `/etc/gconf/gconf.xml.system': Permission denied
--
gconf-sanity-check-2 exits with code 256 on Xorg start
This bug was fixed in the package gconf - 2.26.2-0ubuntu2
---
gconf (2.26.2-0ubuntu2) karmic; urgency=low
* Fix LP: #383461 by correcting references to gconf.xml.system:
* debian/gconf2-common.dirs:
- Add /etc/gconf/gconf.xml.system. Since we reference it in
This is because a line in gconfd still references that directory.
Whenever it receives a org.gnome.GConf.Default.SystemSet signal, it
notifies listeners of that directory that it changed. But when it does
so, if the directory is missing, it creates it with 0700 permissions
(i.e. drwx--).
So
Here's a patch that does 3 things:
1) Fixes the directory permissions for anyone upgrading from the broken version
2) Creates the directory if it doesn't exist
3) Fix the reference in code from xml.system to xml.defaults
** Branch linked: lp:~mterry/gconf/fix-xml-system-383461
** Attachment
Oh, and there's also a bzr branch for the fix.
** Changed in: gconf (Ubuntu)
Status: In Progress = Confirmed
** Changed in: gconf (Ubuntu)
Assignee: Michael Terry (mterry) = (unassigned)
--
gconf-sanity-check-2 exits with code 256 on Xorg start
Thank you for your work there
** Changed in: gconf (Ubuntu)
Importance: Undecided = Low
** Changed in: gconf (Ubuntu)
Assignee: (unassigned) = Ubuntu Desktop Bugs (desktop-bugs)
--
gconf-sanity-check-2 exits with code 256 on Xorg start
https://bugs.launchpad.net/bugs/383461
You
** Description changed:
Binary package hint: libgconf2-4
This is against Karmic Alpha 1.
After upgrading and rebooting, when Xorg started (via gdm), I got an
error dialog /usr/lib/libgconf2-4/gconf-sanity-check-2 exited with code
256 to which I clicked the Close button. Display
I get the same error dialog during start. But when I run gconf-sanity-
check-2 from a terminal I get no output and it exits with code 0.
--
gconf-sanity-check-2 exits with code 256 on Xorg start
https://bugs.launchpad.net/bugs/383461
You received this bug notification because you are a member of
@Michael: I got the same when trying that after I was logged in. Try it when
you're on the gdm screen and change into a tty (Ctrl+Alt+F1 for example) and
rund the sanity check there.
My guess for the exit code 0 is that the sanity check doesn't work anymore
after gconf is loaded on login.
--
I had the same problem after upgrading from jaunty to karmic alpha 1 and
added a comment on bug 380234 for this. But I'm not sure if the issues
described there are exactly the same as the issue described here so I
won't mark it as a duplicate. Instead I marked bug 383434 as a duplicate
of this bug
12 matches
Mail list logo
