Bug 18991 - Introspect error with PackageKit
Summary: Introspect error with PackageKit
Alias: None
Product: dbus
Classification: Unclassified
Component: core (show other bugs)
Version: 1.2.x
Hardware: x86 (IA32) Linux (All)
: medium normal
Assignee: Havoc Pennington
QA Contact: John (J5) Palmieri
Depends on:
Reported: 2008-12-09 16:30 UTC by Dan Ziemba
Modified: 2011-01-26 10:14 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Description Dan Ziemba 2008-12-09 16:30:00 UTC
When I install, update, or erase any package using yum, dbus gives an Introspect error, but the package still installs fine.  This is the error message:  

Running Transaction
  Installing     : dgen-sdl                                                 1/1 
ERROR:dbus.proxies:Introspect error on :1.50:/org/freedesktop/PackageKit: 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 "org.freedesktop.DBus.Introspectable" member "Introspect" error name "(unset)" destination ":1.50")
=============================== Leaving rpm code ===============================

This started with the dbus policy changes in 1.2.6, but I have upgraded to 1.2.8 and it still persists.  I am running Fedora 10, here is my relevant info:


I probably can't be much help actually figuring out what is wrong here, but I am willing to test any updates or patches.
Comment 1 Stian Skjelstad 2009-02-10 02:49:39 UTC
Have you checked that this is not a red-hat specific issue, or PackageKit. Looking at the error-message, my first suspision would be the config files PackageKit/Red Hat has supplied the dbus-daemon with.
Comment 2 Simon McVittie 2011-01-26 10:14:32 UTC
Either PackageKit should let itself be introspected, or whatever is introspecting it shouldn't. Either way, this isn't D-Bus' fault.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.