Comment # 10 on bug 1229813 from Simon Lees

I have been unable to replicate this on my systems, or on a fresh tumbleweed
install. Given that wtmpdb was already on my fresh tumbleweed install I presume
it has reasonable test coverage on openqa and the issue didn't show up on any
of the journal check tests there.

I'm going to need more info about the systems that were having this issue
before I can debug further, also lowering the priority as so far its only been
seen on one system.

Out of interest had these systems previously swapped to runnning dbus-broker?