Red Hat Bugzilla – Bug 103001
GConf1 needs to be updated to use local locks
Last modified: 2008-04-23 01:34:59 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20030225
Description of problem:
After an update to GConf2 and -devel from rawhide, I'm unable to start any GConf
dependent app. Running oaf-slay and bonobo-slay, then cleaning up the leftover
locks worked once, but since then, I'm unable to start, for example, evolution,
grcm, etc. I attempted to run some of these from a shell directly to get some
error output, but other than the app hanging, there isn't any. I've also tried
using the GCONF_LOCAL_LOCKS trick, as well as running various programs as a
local user. The result is the same each time. I'm running RH9 + various updates
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Update to GConf2-2.3.3-2 from rawhide
2. Try to start evolution
3. Observe hangs and stale lock files after killing app.
Actual Results: The app fails to start
Expected Results: The app starts.
When I first started, I got an error indicating an error regarding a socket was
seen, but I've been unable to reproduce this and failed to record it. I do,
however, see a number of gconfd-2 processes left over after anything is run that
I went digging through my logs, and found the error I referred to earlier:
gconfd (rob-5971): Failed to send buffer
Looks like it's having a problem with sockets or something.
Did you also update ORBit2 and bonobo?
Here are my versions:
I believe these are all the current versions from rawhide.
I went back, ripped out evolution, gconf, and all the bonobo stuff, removed
every trace of anything that looked like a pipe and reinstalled. Other than not
being able to exit evolution (I have to do a killev) and links failing to launch
the associated app, everything seems to be working.
Very strange. Its possible that GConf had problems with earlier versions of
ORBit, but I have no idea what caused persistant problems like this.
doesn't allow gconf _1_ apps to start, no?
gconf1 needs to default to local locks now...
I had updated both gconf1 and gconf2. The list of apps included evolution and
grcm. Are those both gconf1 apps? I though evolution used gconf2.
Depends on the version of evolution, 1.2 uses gconf1, 1.4 gconf2.
I know gconf 1 apps are broken, anyhow. If gconf 2 apps are broken it's some odd
orbit thing probably, gconf 1 is more complicated.
Okay, status seems to be:
GConf2 has been changed to keep its locks in /tmp rather than
in $HOME. GConf1 hasn't been updated to use local locks so
now if you have gconfd-2 running and you do
$> gconftool-1 -R /tmp
then gconfd-1 gets activated rather. Broken.
I don't think GConf 1 bugs are worth keeping open at this point.