Bug 714341 - "No such method" DBus error when trying to install dependencies via virt-manager
Summary: "No such method" DBus error when trying to install dependencies via virt-manager
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: PackageKit
Version: 15
Hardware: x86_64
OS: Linux
unspecified
low
Target Milestone: ---
Assignee: Richard Hughes
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-06-18 08:21 UTC by Robin Green
Modified: 2012-10-23 12:22 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-07-22 08:03:08 UTC
Type: ---


Attachments (Terms of Use)

Description Robin Green 2011-06-18 08:21:04 UTC
Description of problem:
virt-manager is unable to install its dependencies for KVM

Version-Release number of selected component (if applicable):
virt-manager-0.8.7-4.fc15.noarch

How reproducible:
Always

Steps to Reproduce:
1. Run virt-manager
2. Click Yes to the question about installing hypervisor dependencies
  
Actual results:
Error dialog appears with these details:
Traceback (most recent call last):
  File "/usr/share/virt-manager/virtManager/engine.py", line 126, in check_packagekit
    packagekit_install(do_install)
  File "/usr/share/virt-manager/virtManager/engine.py", line 165, in packagekit_install
    timeout=timeout)
  File "/usr/lib/python2.7/site-packages/dbus/proxies.py", line 68, in __call__
    return self._proxy_method(*args, **keywords)
  File "/usr/lib/python2.7/site-packages/dbus/proxies.py", line 140, in __call__
    **keywords)
  File "/usr/lib/python2.7/site-packages/dbus/connection.py", line 630, in call_blocking
    message, timeout)
DBusException: org.freedesktop.DBus.Error.UnknownMethod: No such method 'InstallPackageNames' in interface 'org.freedesktop.PackageKit.Modify' at object path '/org/freedesktop/PackageKit' (signature 'iass')

Expected results:
The packages listed in the previous dialog should be installed

Additional info:
PackageKit-0.6.15-1.fc15.x86_64
KPackageKit is running

Comment 1 Cole Robinson 2011-07-13 02:14:08 UTC
Seems to be KDE specific. Maybe PackageKit is missing a dependency or something?

2011-07-13 02:14:06,437 (engine:76): Asking PackageKit what's installed locally.
2011-07-13 02:14:12,326 (engine:101): Missing packages: ['qemu-system-x86', 'libvirt']
2011-07-13 02:14:16,249 (engine:163): Installing packages: ['qemu-system-x86', 'libvirt']
2011-07-13 02:14:16,452 (proxies:400): Introspect error on :1.3:/org/freedesktop/PackageKit: dbus.exceptions.IntrospectionParserException: Error parsing introspect data: <class 'xml.parsers.expat.ExpatError'>: unbound prefix: line 5, column 4
2011-07-13 02:14:16,452 (proxies:403): Executing introspect queue due to error
2011-07-13 02:14:16,877 (error:66): dialog message: Error talking to PackageKit: org.freedesktop.DBus.Error.UnknownMethod: No such method 'InstallPackageNames' in interface 'org.freedesktop.PackageKit.Modify' at object path '/org/freedesktop/PackageKit' (signature 'iass') : Traceback (most recent call last):
  File "/usr/share/virt-manager/virtManager/engine.py", line 126, in check_packagekit
    packagekit_install(do_install)
  File "/usr/share/virt-manager/virtManager/engine.py", line 165, in packagekit_install
    timeout=timeout)
  File "/usr/lib/python2.7/site-packages/dbus/proxies.py", line 68, in __call__
    return self._proxy_method(*args, **keywords)
  File "/usr/lib/python2.7/site-packages/dbus/proxies.py", line 140, in __call__
    **keywords)
  File "/usr/lib/python2.7/site-packages/dbus/connection.py", line 630, in call_blocking
    message, timeout)
DBusException: org.freedesktop.DBus.Error.UnknownMethod: No such method 'InstallPackageNames' in interface 'org.freedesktop.PackageKit.Modify' at object path '/org/freedesktop/PackageKit' (signature 'iass')

Comment 2 Robin Green 2012-07-22 08:03:08 UTC
Bug no longer present in Fedora 17.

Comment 3 Sriram 2012-10-23 12:22:57 UTC
This issue doesn't seem to have been fixed. I am using Fedora 17 KDE and I am still getting this error message. Maybe it happens only in KDE, but it still exists.


Note You need to log in before you can comment on or make changes to this bug.