Bug 103001 - GConf1 needs to be updated to use local locks
GConf1 needs to be updated to use local locks
Product: Fedora
Classification: Fedora
Component: GConf (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Ray Strode [halfline]
: Triaged
Depends On:
Blocks: CambridgeBlocker
  Show dependency treegraph
Reported: 2003-08-24 22:08 EDT by Rob Hughes
Modified: 2008-04-23 01:34 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2008-04-23 01:34:59 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Rob Hughes 2003-08-24 22:08:47 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
from rawhide.

Version-Release number of selected component (if applicable):

How reproducible:

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.

Additional info:

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
uses gcond2/CORBA.
Comment 1 Rob Hughes 2003-08-24 23:37:32 EDT
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.
Comment 2 Alexander Larsson 2003-08-27 06:08:39 EDT
Did you also update ORBit2 and bonobo?
Comment 3 Rob Hughes 2003-08-27 07:31:05 EDT
Here are my versions:

I believe these are all the current versions from rawhide.
Comment 4 Rob Hughes 2003-09-08 23:28:10 EDT
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.
Comment 5 Alexander Larsson 2003-09-10 09:01:06 EDT
Very strange. Its possible that GConf had problems with earlier versions of
ORBit, but I have no idea what caused persistant problems like this.
Comment 6 Havoc Pennington 2003-10-04 01:45:45 EDT
doesn't allow gconf _1_ apps to start, no?

gconf1 needs to default to local locks now...
Comment 7 Rob Hughes 2003-10-04 08:12:41 EDT
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.
Comment 8 Havoc Pennington 2003-10-04 12:41:27 EDT
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.
Comment 9 Mark McLoughlin 2004-07-28 02:37:26 EDT
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.
Comment 10 Matthias Clasen 2008-03-26 12:10:52 EDT
I don't think GConf 1 bugs are worth keeping open at this point.

Note You need to log in before you can comment on or make changes to this bug.