incorrect dbus permissions

[Thom May]

Binary package hint: virt-manager

attempting to run virt-manager results in this output in ~/.virt-manager/virt-manager.log:
[Mon, 14 Apr 2008 14:28:39 virt-manager 7841] INFO (virt-manager:126) Application startup
[Mon, 14 Apr 2008 14:28:39 virt-manager 7842] DEBUG (engine:74) About to connect to uris ['qemu:///session']
[Mon, 14 Apr 2008 14:28:39 virt-manager 7842] ERROR (connection:158) Unable to connect to HAL to list network devices: '%s'<class 'dbus.exceptions.DBusException'> org.freedesktop.DBus.Error.AccessDenied: A security policy in place prevents this sender from sending this message to this recipient, see message bus configuration file (rejected message had interface "(unset)" member "QueryCapability" error name "(unset)" destination ":1.2")
Traceback (most recent call last):
  File "/usr/share/virt-manager/virtManager/connection.py", line 153, in detect_network_devices
    self._device_added(path)
  File "/usr/share/virt-manager/virtManager/connection.py", line 164, in _device_added
    if obj.QueryCapability("net"):
  File "/var/lib/python-support/python2.5/dbus/proxies.py", line 68, in __call__
    return self._proxy_method(*args, **keywords)
  File "/var/lib/python-support/python2.5/dbus/proxies.py", line 140, in __call__
    **keywords)
  File "/var/lib/python-support/python2.5/dbus/connection.py", line 607, in call_blocking
    message, timeout)
DBusException: org.freedesktop.DBus.Error.AccessDenied: A security policy in place prevents this sender from sending this message to this recipient, see message bus configuration file (rejected message had interface "(unset)" member "QueryCapability" error name "(unset)" destination ":1.2")

ii virt-manager 0.5.3-0ubuntu8

[Dustin Kirkland  (kirkland)]

Hello, thanks for the bug report.

Could you please try this again with the latest Hardy or, ideally on Intrepid?

I did some work recently integrating kvm support with hal in Intrepid that I think might address this problem.

:-Dustin

[Dimitrios Symeonidis (azimout)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!