On Tue, 2013-04-30 at 22:29 -0400, Walter Dnes wrote: > I was going to file a bug at bugzilla, but this looks like it's going > to involve virtually every GNOME-related app, so playing whack-a-mole is > going to be painfull. It'll have to be tackled higher up, which is why > I'm posting here. I apologize if there is a more correct way of > reporting this. I'm not aware of it. Background... > > GNOME is migrating from GConf to GSettings, as per... > https://developer.gnome.org/gio/2.26/ch26.html > https://live.gnome.org/GnomeGoals/GSettingsMigration
GNOME *long ago migrated* from GConf to GSettings. The migration started years ago and was completed with GNOME-3.4, released in spring 2012. > This is starting to impact some Gentoo users... It impacts users who use stable keywords and are therefore stuck with GNOME-2.32. The workaround is for affected users to switch to ~arch keywords (note that GNOME-3.x ebuilds in ~arch get vastly more care and attention from us than the theoretically stable GNOME-2.32). And the real solution is to finally stabilize some release of GNOME-3.x
