Comment 3 for bug 367334

click170 (click170) wrote :

The nature of the problem is such that makes it rather hard to confirm.
I would propose that a check be performed instead of issuing that warning; Could console-kit-daemon not do an existence check before issuing that warning, and then only issue said warning if the directory does exist?
This would prevent any short-lived processes from generating those warnings in ckd, but would still generate warnings if for some reason the directory did exist but ckd could not read it.
In any event, its just an eye-sore seeing them in the logs knowing they don't need to be there. Short-lived processes, though rare, aren't something to be concerned about most of the time so it seems to me they shouldn't generate warnings.