Fix blueman startup when .cache dir doesn't exist

When blueman checks, if another instance is already running, it relies on the `~/.cache` directory already having been created before. It tries to write a file into that dir and raises an exception which is misinterpreted as another instance running.