Comment 22 for bug 613273

My case resolved: somehow during upgrade I got /run as symlink to /var/run and /var/run as symlink to /run. After I patched this, the problem is gone. But it took time to spot it.

Regarding bug title: I find this error message to be not too informative… Providing some detail about the problem (which directory is not empty and what it contains, for example) woudl make resolving problems much easier.