On 11/25/2016 01:28 PM, Sam Varshavchik wrote:
> Patrick O'Callaghan writes:
>
>> On Fri, 2016-11-25 at 11:08 -0500, Sam Varshavchik wrote:
>> > Wondering if all upgrades with selinux enabled are broken, or just
>> something
>> > with this particular laptop. This doesn't look like a system-speci
Patrick O'Callaghan writes:
On Fri, 2016-11-25 at 11:08 -0500, Sam Varshavchik wrote:
> Wondering if all upgrades with selinux enabled are broken, or just
something
> with this particular laptop. This doesn't look like a system-specific
> failure to me, but if all upgrades with enforcing se
On Fri, 2016-11-25 at 11:08 -0500, Sam Varshavchik wrote:
> Wondering if all upgrades with selinux enabled are broken, or just something
> with this particular laptop. This doesn't look like a system-specific
> failure to me, but if all upgrades with enforcing selinux blow up like this,
> I w
On 25 November 2016 at 16:08, Sam Varshavchik wrote:
> With selinux set to enforcing, my system-upgrade to 25 failed to start,
> resulting in a reboot loop. I fished the following out of journalctl:
>
> Nov 25 09:51:55 thinkpenguin.email-scan.com audit[1]: AVC avc: denied {
> open } for pid=1 c
With selinux set to enforcing, my system-upgrade to 25 failed to start,
resulting in a reboot loop. I fished the following out of journalctl:
Nov 25 09:51:55 thinkpenguin.email-scan.com audit[1]: AVC avc: denied
{ open } for pid=1 comm="systemd" path="/var/lib/dnf/system-upgrade/.dnf-
sys
