Comment 81 for bug 1063617
Revision history for this message
| Carl-Eric Menzel (duesenklipper) wrote | #81 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
73416ba
(Get the code!)
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?