All the above issues involve 10.04 but I'm running 10.10 from a 2G SDHC
card (Kingston, if it matters) it began showing the posted msg after I
used GParted to try to re-partition my 2 SSDs AFTER I had already
installed Natty that installation began giving me errors abt my /root
partition running
Hi Jessie
Firstly, this bug does not seem to affect anything that I (as an end
user, like yourself) could detect. Clearing the message seemed enough
to be able to proceed with booting using the PC.
I have now moved on to 11.10. This bug went away by 11.04. I don't
know how 11.10 would go in
the recent comments suggest local issues rather than a gconf bug then
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gconf in Ubuntu.
https://bugs.launchpad.net/bugs/577545
Title:
gconf-sanity-check-2 exited with status 256 on log
making /tmp as readwrite solved my issue
there is a problem with config server
usr/lib/libcon2-4/gconf-sanity-check-2 exited with status 256
Thanks Am Freitag
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gconf in Ubuntu.
This occurred to me after
1 dist upgrade from 8.04 to 10.04
2 apt-get clean
3 apt-get autoclean
4 some other cleanup involving booting up with a rescue CD, (and, critically,
cleaning the /tmp directory) in order to tar up the image for future deployment
in the field (20 laptops).
unable to log
affected me too, but chmod 777 /tmp resolve it. btw it resolve problem
with notification applet missing.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gconf in Ubuntu.
https://bugs.launchpad.net/bugs/577545
Title:
** Changed in: gconf (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gconf in Ubuntu.
https://bugs.launchpad.net/bugs/577545
Title:
gconf-sanity-check-2 exited with status 256 on log in
To
My experience with this bug has been after a clean install of 10.04.
(Much of my preferences and previous files came from a 10.10 system
though).
My /tmp directory has the appropriate permissions and I tried creating a
directory as per post of this thread:
got the same issue with our ltsp upgrade to natty after customizing
entries of gconf entried of the user gdm. Got it fixed by wiping
/var/lib/gdm/* + restarting gdm service. Hope that helps.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
The previous message describes my situation exactly. We are trying to
launch a 100+ seat ltsp upgrade, We have tried every suggested solution
for this problem with no positive result. This bug was opened nearly 1
year ago and no successful solution has been found. A complete show
stopper for us.
Nice People,
I have had this problem for a month or so, so please forgive my
frustration n exasperation if it shows up in my posts:
System: Ubuntu 10.04.1 Server, on Dell Optiplex330. Webmin+Squid+ an
apt-mirror.
I have tried the following and still failed:
1. chmod 1777 /tmp (and its variants)
those who workaround it with a local dir probably have a local build or
configuration
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gconf in Ubuntu.
https://bugs.launchpad.net/bugs/577545
Title:
gconf-sanity-check-2 exited with
** Tags added: iso-testing
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gconf in Ubuntu.
https://bugs.launchpad.net/bugs/577545
Title:
gconf-sanity-check-2 exited with status 256 on log in
--
desktop-bugs mailing list
This also occurs on Natty when installing in expert mode.
Follow the test case described here to repeat this from the 'alternate'
installer :
http://testcases.qa.ubuntu.com/Install/AlternateExpert
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
Sorry, I forgot to include in my comment #25:
On subsequent boots, I still get status 256. It's only on the FIRST
boot after booting from the memory stick, that it doesn't appear.
Regards, Garry.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
I had this problem with only the status 256 error being displayed. After
trying everything suggested in every forum I just ended up reinstalling Ubuntu
10.04 and now it works fine.
I think the best first step is to try and reinstall Linux and maybe do
something different during setup. (For
I had this problem in 10.04 (see post #13, plus a locked-PC problem).
I did a fresh install to 10.10 in November. I no longer have the
locked-PC problem, but I still get status 256. It's not a serious
problem, just irritating.
However, just recently, I made a USB-stick copy of 10.10, just so
as newbee in Linux, a friend explained me how to reload and now it's
running
sorry for the disturb
Regards to all contributors (armel)
--
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
and how can I launch a command with chmod /tmp ?
I am a new user (first week-end) because I bought (to see) a Asus
netbook with Ubuntu but without CD reader or manual or anthing... it was
well running but now after the message there is a problem of
configuration server-
I do now a clean installation with Ubuntu 10.04.1 64 bit version.
The problem is present my machine, but chmod /tmp command is
resolving my problem.
Attila
--
gconf-sanity-check-2 exited with status 256 on log in
https://bugs.launchpad.net/bugs/577545
You received this bug notification
I'm having the same error message. I just installed 10.04 on my netbook.
I sort of understand what I need to do to fix this, but could someone
tell me EXACTLY what it is I need to do to change the /tmp file? I have
no idea how to even access it. I think that the answer in post #16 would
solve my
I have a friend that just installed Ubuntu 10.04.1 for the first time on
his machine and this error came up. I will post details once I get a
hold of his machine specs.
--
gconf-sanity-check-2 exited with status 256 on log in
https://bugs.launchpad.net/bugs/577545
You received this bug
I added the line as proposed in #16, but it hasn't made any difference.
By the way, is gconf.xml.defaults supposed to be a folder?
Going back to Sebastien Bacher's comment in #3. I have run the live CD
on 2 other PCs (currently with Myth 9.10 installed) they didn't
exhibit any issues. Perhaps
Had the same problem after upgrading to Ubuntu 10.04. w/o any error when
running /usr/lib/libconf-2-4/gconf-sanity-check-2 in a terminal. Tried
many things w/o success. Finally, #16 solved the problem for me too.
--
gconf-sanity-check-2 exited with status 256 on log in
sudo mkdir -p /usr/local/etc/gconf/gconf.xml.defaults
[note plural defaults rather than default]
fixed the problem for me too.
I got the same errors [apart from his typo] as Andy Pascall in tty running
/usr/lib/libconf-2-4/gconf-sanity-check-2 .
[Note running this in a GUI terminal
Hi sebbo,
Thank you for you sugestion! I have tried many methods. They all didn't
work . But when I changed the permission of /tmp as you said , the
problem had resloved .
Best regards,
Snow
--
gconf-sanity-check-2 exited with status 256 on log in
https://bugs.launchpad.net/bugs/577545
You
Hi Gerry,
try to change the permission of /tmp to 777.
( e.g. put tmpfs /tmp tmpfs mode=1777 0 0 or somethinge like that to
your fstab. mode=1777 sets the permission.)
i have solved the problem on this way for my ubuntu 10.04.
good luck!
Am Freitag, den 25.06.2010, 00:16 + schrieb Garry
I also get this message since I moved to 10.04, 6 weeks ago.
I did mention it in another bug (#580755: login screen locks up), which
covers problems of more concern to me. However, I am the only
subscriber, so I am not getting much (any?) attention.
Since I am able to boot up (although by a
do you get the issue in a guest session? did you install something which
could have changed the gconf path on your box?
--
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
Desktop
Maybe chromium/chrom beta is he source of the problem.
That's the only exotic software I had on both computers.
--
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
Desktop Bugs,
ຄຳ -
I don't have chrome installed.
Sebastien-
I'll check out the guest session thing in a bit. As for the software, it turns
out I have 2 affected computers and one that is not.
I ran dpkg --get-selections on all three. Then, I found which
packages the 2 affected computers had in common and
Switching to the guest account after logging into a normal user account
does not trigger the error.
--
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
Desktop Bugs, which is
not really no, .xsession-errors could have errors
--
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
Desktop Bugs, which is subscribed to gconf in ubuntu.
--
desktop-bugs mailing
Comparing the .xsession-errors between computers that have the problem
and those that don't didn't yield anything. All seem to have a few
errors in common, but there is no error that only shows up in the
affected computers.
Does anyone know what exit status 256 of gconf-sanity-check-2 indicates?
Switching to tty2 and running /usr/lib/libconf-2-4/gconf-sanity-
check-2 produced a bunch of errors. One of which was that
/usr/local/etc/gconf/gconf.xml.default could not be created.
Running: sudo mkdir -p /usr/local/etc/gconf/gconf.xml.default solved
the issue for me.
The strange thing is that
Thank you for you bug report, most users don't get that issue, if you
get it every time on every box you are using it's likely triggered by
something you configure differently from the default installation on
those
** Changed in: gconf (Ubuntu)
Importance: Undecided = Low
--
I have the same bug.
BUT I can't log in at all. The screen is black after login.
This happened on two completely different systems now.
My TWO computers are not useable anymore.
More details:
Siemens Amilo Pro v2035:
=
Before login:
Es gibt ein Problem mit dem
Sebastien,
That seems logical. Any idea on where to look for an error message on
what might be causing this?
Also, this only appeared on upgrade to lucid. I used the alternate CD
and pulled in updated packages from the Internet during install.
--
gconf-sanity-check-2 exited with status 256 on
** Attachment added: .xsession-errors
http://launchpadlibrarian.net/48077628/xsession-errors.txt
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/48077056/Dependencies.txt
--
gconf-sanity-check-2 exited with status 256 on log in
https://bugs.launchpad.net/bugs/577545
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,
40 matches
Mail list logo
