Bug 475763 - "failed to get a TID" - packagekit unusable
Summary: "failed to get a TID" - packagekit unusable
Keywords:
Status: CLOSED DUPLICATE of bug 475074
Alias: None
Product: Fedora
Classification: Fedora
Component: PackageKit
Version: 10
Hardware: All
OS: Linux
low
urgent
Target Milestone: ---
Assignee: Richard Hughes
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-12-10 11:44 UTC by An. N
Modified: 2008-12-10 12:16 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2008-12-10 12:16:34 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description An. N 2008-12-10 11:44:37 UTC
Description of problem:
After installing 126 updates (yes, that many were published in 1 push!), I get the following message when trying to use the gtk software installer in GNOME:

failed to get a TID: 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.PackageKit.Transaction" member "SetLocale" error name "(unset)" destination "org.freedesktop.PackageKit") (0)

The same message appears when trying to use system update.

When using yum, I get the following error:
ERROR:dbus.proxies:Introspect error on :1.33:/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.33")

Package kit seems to be unusable. What a mess!


Version-Release number of selected component (if applicable):
FC10 default after Dec 8 update

How reproducible:
Always

Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Richard Hughes 2008-12-10 12:16:34 UTC

*** This bug has been marked as a duplicate of bug 475074 ***


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