Bug 475103 - can't get TID
can't get TID
Status: CLOSED DUPLICATE of bug 475068
Product: Fedora
Classification: Fedora
Component: gnome-packagekit (Show other bugs)
All Linux
low Severity medium
: ---
: ---
Assigned To: Richard Hughes
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2008-12-07 15:05 EST by Matthias Clasen
Modified: 2008-12-07 19:21 EST (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2008-12-07 19:21:25 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
FreeDesktop.org 18931 None None None Never

  None (edit)
Description Matthias Clasen 2008-12-07 15:05:24 EST
When using the Refresh button in gpk-update-viewer:

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)

Looks like a dbus configuration problem, changing selinux from enforcing to permissive does not affect this.
Comment 1 Matthias Clasen 2008-12-07 15:23:17 EST
Fixed by this, but maybe there are more interfaces that should be added ?

--- org.freedesktop.PackageKit.conf.orig	2008-12-07 15:21:15.000000000 -0500
+++ org.freedesktop.PackageKit.conf	2008-12-07 15:20:59.000000000 -0500
@@ -14,6 +14,7 @@
  <!-- Allow anyone to call into the service - we'll reject callers using PolicyKit -->
   <policy context="default">
     <allow send_interface="org.freedesktop.PackageKit"/>
+    <allow send_interface="org.freedesktop.PackageKit.Transaction"/>
Comment 2 Colin Walters 2008-12-07 19:21:25 EST

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

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