Jamie Fargen wrote:
> On Aug 9, 2013 4:28 PM, <m.roth@xxxxxxxxx> wrote:
>> emmanuel segura wrote:
>> > 2013/8/9 <m.roth@xxxxxxxxx>
>> >
>> >> Just upgraded a user - one of the few on fedora - from FC 17 to 19.
<snip>
>> >> dbus-daemon[308]: dbus[308]: [system] Rejected send message, 2
>> >> matched rules; type="method_call", sender=":1.33" (uid=42 pid=933
>> >> comm="gnome-shell --mode=gdm ")
>> >> interface="org.freedesktop.DBus.Properties" member="GetAll" error
>> >> name="(unset)" requested_reply="0" destination=":1.11" (uid=0 pid=575
>> >> comm="/usr/sbin/console-kit-daemon --no-daemon ")
>> >>
>> >> And lots and lots of
>> >> setroubleshoot: SELinux is preventing /usr/libexec/mission-control-5
>> >> from 'read, open' accesses on the file
/usr/libexec/mission-control-5. For
>> >> complete SELinux messages. run sealert -l
982cd6bc-ff36-4a7e-868e-b215d2b1dbe0
>> >>
>> >> Basically, on the latter, whatever mission-control is (and on the GUI
>> >> screen, it complains telepathy-mission-control had a problem, which I
>> >> guess means it failed to read my mind), has no policy rights to read
>> >> its own files.
>> >>
>> >> Do I need to file a bug report?
>> >
>> > If i remember well you should upgrade in this way f17->f18->f19
>> >
>> So, fc17 full update, then ->fc19 wasn't enough? And why would the
>> selinux policy not work?
>>
> It seems more effective to just make
> /home a separate partition and to do a fresh install.
That's certainly not necessary, since the user's home directory is NFS
mounted via autofs. But what does that have to do with the selinux policy
with this mission-control-5?
mark "who also doesn't top post"
--
redhat-list mailing list
unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/redhat-list
