Description of problem: Tried to run System->Admin->Add/Remove software, and when choosing a group to list, it says: "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)" Version-Release number of selected component (if applicable): 0.3.9-4 How reproducible: Tried to run System->Admin->Add/Remove software, and when choosing a group to list. Steps to Reproduce: 1. System->Admin->Add/Remove software 2. Choose a group to list 3. Error shown above appears in pop-up dialog box Actual results: Expected results: To be able to view the packages/group and add/delete apps. Additional info:
I'm seeing the exact same behaviour here, after recent packagekit updates: 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)
BTW this is on Fedora 9
Same here after most recent update. Fedora 10. This also affects Software Sources and Update System, where no repositories at all are showing. Yum works fine for updating, except for PackageKit which has a depsolve problem with gnome-packagekit-0.3.9-8.fc10.i386 needing libpackagekit-glib.so.10. However, libpackagekit-glib.so.10 is already installed, so no resolution can be made.
I got the same error message after updating to PackageKit-0.3.9-4.fc10 on my Centrino laptop and my Phenom desktop this morning. I notice that the System -> Software source box is now void of any repository information (I had Fedora and Fedora-Updates selected before). The repository information files still reside in /etc/yum.repos.d but PackageKit appears now unable to read them?
*** This bug has been marked as a duplicate of bug 475074 ***