Arch Linux

Related forum thread: http://bbs.archlinux.org/viewtopic.php?pid=437329

Confirmed. Downgrading the package did work.

Moving gnome 2.24 won't solve your issue. Gconf is backwards compatible and should even work with GNOME 2.20. The reason why things are failing here is because GConf 2.24 switched to dbus instead of orbit. Looking in the forum thread, the dbus session bus isn't running or got killed, causing gconf to fail. Try logging out from GNOME, making sure you don't have any GNOME-related processes running and launch GNOME again.

No, relogin does not solve the problem. In the forum dbus is really running but strangely "not found" by gnome. Is there any way to debug this problem further, at the moment, just downgrading gconf solved the described problem in the forum.

The same, relogin didn't help.

The dbus session bus is something completely different than the system bus you put in /etc/rc.conf.
I think this is related to the fact that gnome-session starts dbus, but probably after gconf is started. I pushed a new dbus into extra that contains a scriptlet that autolaunches dbus when starting gnome from GDM.

I confirm this issue

I confirm the issue too

Updating dbus didn't fix the issue

> Updating dbus didn't fix the issue

dbus 1.2.3-1
LastUpdated: 2008-09-13

http://www.archlinux.org/packages/extra/i686/dbus/

Where did you get this update?

http://repos.archlinux.org/viewvc.cgi/dbus/repos/extra-i686/
http://repos.archlinux.org/viewvc.cgi/dbus-core/repos/core-i686/

> Where did you get this update?
This is my question, too. Hopefully Gnome 2.24 will solve all these issues anyway :)

JGC wrote:
> The dbus session bus is something completely different than the system bus you put in /etc/rc.conf.

Okay, that seems reasonable.?


> I think this is related to the fact that gnome-session starts dbus,
> but probably after gconf is started.

And this too, since this explains why running gnome-settings-daemon manually solves the problem while running gnome, but...

> I pushed a new dbus into extra that contains a scriptlet that autolaunches dbus when starting gnome from GDM.

This sounds like a ugly workaround. Shouldn't be gnome-session fixed so that the order of launching gnome-stuff is correct? Please excuse me dumb questions, but I'm just interested in the internal structure of gnome...

Now it's reaching some mirrors. However, as I've already said, it *doesn't* fix the issue. Downgrading to gconf-2.22.0 fixed the issue.

Yes, if all mirrors do have the "wrong" gconf, you can download it here if you trust me:

http://student.physik.uni-mainz.de/~aneiser/gconf-2.22.0-1-i686.pkg.tar.gz

Hth,
Andreas

Update solved the problem (tested twice).

After discovering the bug, I've added myself to group "policykit" and added "dbus" to rc.conf.

Yes, I can confirm this. The steps I did:
1. sudo gpasswd -a <username> policykit
2. sudo pacman -Syu
3. System restart (Logout/Login does not restart dbus...)
So it is not necessary to add dbus in rc.conf if you have already hal in this list.
Thanks Jan for this fast fix today!

Also adding the user to the "policykit" group doesn't completely fix the issue, I still receive errors using the "Root Terminal" and If I logout/re-login I receive tons of errors. Using the old gconf-2.22.0 it's all ok.

Adding my user to the policykit group resolved the

Oct 20 20:43:58 darkstar gdm-binary[4182]: atk-bridge-WARNING: AT_SPI_REGISTRY was not started at session startup.
Oct 20 20:43:58 darkstar gdm-binary[4182]: atk-bridge-WARNING: IOR not set.
Oct 20 20:43:58 darkstar gdm-binary[4182]: atk-bridge-WARNING: Could not locate registry
Oct 20 20:43:58 darkstar gdm-binary[4182]: Gtk-WARNING: Ignoring the separator setting

errors when logging out of gnome but didn't stop the

Oct 20 21:29:14 darkstar gvfs-fuse-daemo[4092] general protection ip:7f7de6e384ca sp:7ffff0a64f50 error:0 in libpthread-2.8.so[7f7de6e30000+16000]
Oct 20 21:29:42 darkstar gvfs-fuse-daemo[4355] general protection ip:7ff02fa464ca sp:7fff39673ab0 error:0 in libpthread-2.8.so[7ff02fa3e000+16000]
Oct 20 21:31:39 darkstar gvfs-fuse-daemo[4600] general protection ip:7f076da9e4ca sp:7fff776cbb00 error:0 in libpthread-2.8.so[7f076da96000+16000]
Oct 20 21:32:07 darkstar gvfs-fuse-daemo[4954] general protection ip:7f3ca9c9d4ca sp:7fffb38cad00 error:0 in libpthread-2.8.so[7f3ca9c95000+16000]

errors. And I'm still sporadically getting errors like this

Failed to get connection to session: Failed to connect to socket /tmp/dbus-SL89CuqY5z: Connection refused)

from various applets when I log in to gnome. Gah!

Downgrade to gconf-2.22.0-1 worked.

Adding yourself to the policykit group is not the way to fix this. Looking at the errors you get, there's a dbus socket address exported for a dbus daemon that isn't running (you get connection refused). This is not an issue with GConf, it's an issue with dbus on your system. A reboot should possibly solve your problems.

Rebooting (several times) doesn't fix the issue, I wish it was that simple

Jan wrote:
> Adding yourself to the policykit group is not the way to fix this.
Yes. That's true. I just removed myself from the policykit group and it's still working (after the dbus update).

gconf 2.24.0-1 works here with dbus-core 1.2.3-1 and dbus 1.2.3-3