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?
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?