"gconftool --recursive-unset /apps/gnome_settings_daemon" solved the problem.
Running "diff -U4 gsd-broken gsd-working" where gsd-broken and gsd-working is the output of "gconftool --dump /apps/gnome_settings_daemon" on a broken and unbroken account respectively, produced:
FINALLY, after checking each of those differences, it appears that the value in /apps/gnome_settings_daemon/gtk-modules/gail:atk-bridge, which on my jaunty system was an empty string, caused gnome-settings-daemon to crash under karmic. Replacing it with "/desktop/gnome/interface/accessibility" gets everything working right again.
How it came to be in that state, I do not know, but the crash under karmic is probably a regression.
"gconftool --recursive-unset /apps/gnome_ settings_ daemon" solved the problem.
Running "diff -U4 gsd-broken gsd-working" where gsd-broken and gsd-working is the output of "gconftool --dump /apps/gnome_ settings_ daemon" on a broken and unbroken account respectively, produced:
atrus@yeesha:~$ diff -U4 gsd-broken gsd-working
<key>gtk- modules/ gail:atk- bridge< /key>
<schema_ key>/schemas/ apps/gnome_ settings_ daemon/ gtk-modules/ gail:atk- bridge< /schema_ key> /desktop/ gnome/interface /accessibility< /string>
<key>keybinding s/calculator< /key>
<key>keybinding s/next< /key>
<schema_ key>/schemas/ apps/gnome_ settings_ daemon/ keybindings/ next</schema_ key> <Control& gt;XF86AudioRai seVolume< /string> XF86AudioNext< /string>
<key>keybinding s/pause< /key>
<key>keybinding s/play< /key>
<schema_ key>/schemas/ apps/gnome_ settings_ daemon/ keybindings/ play</schema_ key> <Control& gt;XF86AudioMut e</string> XF86AudioPlay< /string>
<key>keybinding s/power< /key>
<key>keybinding s/previous< /key>
<schema_ key>/schemas/ apps/gnome_ settings_ daemon/ keybindings/ previous< /schema_ key> <Control& gt;XF86AudioLow erVolume< /string> XF86AudioPrev< /string>
<key>keybinding s/screensaver< /key>
<key>plugins/ a11y-keyboard/ active< /key>
<schema_ key>/schemas/ apps/gnome_ settings_ daemon/ plugins/ a11y-keyboard/ active< /schema_ key>
<key>plugins/ a11y-keyboard/ priority< /key>
<key>plugins/ xrdb/active< /key>
<schema_ key>/schemas/ apps/gnome_ settings_ daemon/ plugins/ xrdb/active< /schema_ key>
<key>plugins/ xrdb/priority< /key>
--- gsd-broken 2009-09-04 11:05:25.822290806 -0600
+++ gsd-working 2009-09-04 11:04:19.845290295 -0600
@@ -10,9 +10,9 @@
<entry>
<value>
- <string></string>
+ <string>
</value>
</entry>
<entry>
@@ -59,9 +59,9 @@
<entry>
<value>
- <string>
+ <string>
</value>
</entry>
<entry>
@@ -73,9 +73,9 @@
<entry>
<value>
- <string>
+ <string>
</value>
</entry>
<entry>
@@ -87,9 +87,9 @@
<entry>
<value>
- <string>
+ <string>
</value>
</entry>
<entry>
@@ -150,9 +150,9 @@
<entry>
<value>
- <bool>false</bool>
+ <bool>true</bool>
</value>
</entry>
<entry>
@@ -354,9 +354,9 @@
<entry>
<value>
- <bool>true</bool>
+ <bool>false</bool>
</value>
</entry>
<entry>
FINALLY, after checking each of those differences, it appears that the value in /apps/gnome_ settings_ daemon/ gtk-modules/ gail:atk- bridge, which on my jaunty system was an empty string, caused gnome-settings- daemon to crash under karmic. Replacing it with "/desktop/ gnome/interface /accessibility" gets everything working right again.
How it came to be in that state, I do not know, but the crash under karmic is probably a regression.