You have been subscribed to a public bug:
I halted my system normally, but when I booted it again and logged in, a
window popped up saying that gconfd can't be contacted. This happened to
me a couple of times. In feisty and previous releases, this could happen
because of logging out by pressing ctrl+alt+backspace (there are bugs
opened) but I suspect this bug is different. Actually, in many cases,
gconfd deadlocks when pressing ctrl+alt+backspace, but the case I am
reporting is different since I just booted my system. It seems like
gconfd was just too slow to be reached on time for the start of the
session, but that might be just an impression.
In any case, I have a strangely looking gtk theme and all settings are
gnome defaults I suppose. However, compiz settings have been loaded
normally, even if I am using the gconf-backend, which seems to confirm
the "too slow to get session startup in time" thesis, since compiz is
really slow to start, and might be the last process in the session to
attempt to contact gconfd. This is all I can say by looking at the
problem "externally". I attach my .xsession-errors and syslog, if you
need more information tell me, when it happens again I will try to
provide that.
** Affects: gconf2 (Ubuntu)
Importance: Undecided
Status: New
--
[gutsy] gconfd starts with session, but apps say that gconfd can't be contacted
and user settings are not loaded
https://bugs.edge.launchpad.net/bugs/139368
You received this bug notification because you are a member of Ubuntu Desktop
Bugs, which is a bug contact for gconf2 in ubuntu.
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
