I guess that it is a bug of awn rather than of gconf, as awn as far as I know is the only application to break after the update. Maybe it just exposed one of the bugs in awn which relies on specific behavior of gconf?
-- awn disappeared after update to gconf 2.28.0-1ubuntu3 https://bugs.launchpad.net/bugs/514134 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
