Red Hat Bugzilla – Bug 699099
Empathy starts with error message: Failed to execute program /usr/libexec/mission-control-5
Last modified: 2011-04-25 09:56:13 EDT
Description of problem:
Empathy starts with the following error message preventing to access the accounts information:
"Failed to access account manager: Failed to
execute program /usr/libexec/mission-control-5: Success"
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. launch empathy
Error message at launch, accounts are unavailable
Empathy should start normally
It happened after a selinux-policy update. Happens on 3 different machines.
avc for 2 machines here: http://fpaste.org/HvxQ/ and here: http://fpaste.org/71VI/
Fixed using information in F13 bug: https://bugzilla.redhat.com/show_bug.cgi?id=616506
Confirm this bug.
I was told on #fedora-test that su -c 'fixfiles -R -a restore; reboot;' should also fix this. The person is also convinced "I did something" as the error is due to "unlabeled_t" which is unlabeled files (a start with SELinux disabled?). However one of the machine is a fresh install from LiveCD updated once on Friday (no problem) and once on Saturday (the issue arose). Nothing else was done on that machine.
(In reply to comment #2)
> I was told on #fedora-test that su -c 'fixfiles -R -a restore; reboot;' should
> also fix this. The person is also convinced "I did something" as the error is
> due to "unlabeled_t" which is unlabeled files (a start with SELinux disabled?).
Well, that doesn't solve the problem for me. I still get the message after running fixfiles.
chcon -t bin_t /usr/libexec/mission-control* /usr/libexec/telepathy*
fixes it for me, taken from https://bugzilla.redhat.com/show_bug.cgi?id=616506#c5.
I was updating a Fedora 15 alpha/beta/whatever installation and it also happend after some update, with no other action involved.
The command above fixes it for me too.
Is there any valid reason to display an error message saying “success”?
We turned off the transition from unconfined_t to telepathy confined domains, which broke running telepathy sessions. If you just killall telepathy sessions and restart, or log out and back in, it should fix the problems.
Sadly we can not fix this problem cleanly on a running F15 Beta system, it will not be seen on fresh installs of the next F15 release.
Pavel Not sure where you are seeing success, but the kernel is reporting whether the syscall completed successfully. The kernel can generate an AVC and have the syscall succeed, This can happen if the syscall went down a different path and worked, or if the machine is in permissive mode or the process is in permissive mode.
*** Bug 699012 has been marked as a duplicate of this bug. ***
*** Bug 699150 has been marked as a duplicate of this bug. ***