Martin, just to clear things up, I still tend to think it's still a PolicyKit bug :). if an application doesn't set I/O watch functions for config changes, PolicyKit shouldn't make use of its internal caches, as they aren't going to be updated properly, leading to serious (and unobvious) malfunctioning in that application, as we could see here...
Martin, just to clear things up, I still tend to think it's still a PolicyKit bug :). if an application doesn't set I/O watch functions for config changes, PolicyKit shouldn't make use of its internal caches, as they aren't going to be updated properly, leading to serious (and unobvious) malfunctioning in that application, as we could see here...