Hm ... on my VM, abrt-configuration is still running after the sleep. This results in the next test failing because the interface from this test is used.

Suggestions:
* Fix the timeout. Running `abrt-configuration -t1` on my VM does not result in timeout at all (`abrt-dbus -t1` works fine).
* Using sleep to wait for the `abrt-configuration` to end in the test seems prone to race conditions. I'd rather increase the timeout a bit and then kill the program explicitly at the end.