I can confirm this bug for Ubuntu 18.04. with 0.0.svn13576+dfsg-3 too.
Really disappointing...
Workaround with manually starting it as flieller suggest works. :)
I can confirm this bug for Ubuntu 18.04. with 0.0.svn13576+dfsg-3 too.
Really disappointing...
Workaround with manually starting it as flieller suggest works. :)