Bug 103001
Summary: | GConf1 needs to be updated to use local locks | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Rob Hughes <rob> |
Component: | GConf | Assignee: | Ray Strode [halfline] <rstrode> |
Status: | CLOSED WONTFIX | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | rawhide | Keywords: | Triaged |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2008-04-23 05:34:59 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 100643 |
Description
Rob Hughes
2003-08-25 02:08:47 UTC
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: bonobo-1.0.22-7 bonobo-devel-1.0.22-7 libbonobo-devel-2.3.6-2 libbonoboui-2.3.6-2 libbonoboui-devel-2.3.6-2 bonobo-conf-0.16-5 bonobo-conf-devel-0.16-5 libbonobo-2.3.6-2 ORBit-0.5.17-10.3 ORBit-devel-0.5.17-10.3 ORBit2-2.7.5-5 ORBit2-devel-2.7.5-5 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. |