Thanks for the bug report. I believe this issue has been resolved in
the latest development version:
dave@voodoo:~$ sudo service libvirt-bin start
libvirt-bin start/running, process 21956
dave@voodoo:~$ sudo service libvirt-bin status
libvirt-bin start/running, process 21956
dave@voodoo:~$ sudo
(Sorry - somehow I failed to see the original response; bug should have
been new, not incomplete, so I'm re-opening).
Assuming you are still seeing this problem, please do
apport-collect 809632
to give us some more information about your system. What you are
describing should not be happen
[Expired for libvirt (Ubuntu) because there has been no activity for 60
days.]
** Changed in: libvirt (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in Ubuntu.
https://bugs.launchp
Please explain what "Job is already running" means when the job is _not_
already running. In the general meaning of "already running" there
should be, well, something running, a process, yet when this message is
issued there is no libvirt-bin or libvirtd or any related process at
all. Nor is there
Thanks for taking the time to submit this bug.
I'm afraid I don't understand the problem. Could y please tell us
exactly what you expect to happen?
** Changed in: libvirt (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Server T
