Good to see that it's still being looked at. I'm trying the "dconf watch /" thing now, but I see two problems with it: The output of dconf is not timestamped nor does it show what process caused the dconf change. Is there any way to obtain that information?
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1063617 Title: 1:0.9.8+bzr3319-0ubuntu1 regression: keeps setting gsettings keys to wrong values To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1063617/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
