Re: Heads up: selinux-policy-3.14.1-25.fc28 breaks GDM

I got hit with this too on F28 using negativo17's nvidia driver packages.Downgrading selinux-policy-3.14.1-25 / selinux-policy-targeted-3.14.1-25 clears it up.There's a fedora update to -3.14.1-29 pending: https://bodhi.fedoraproject.org/updates/FEDORA-2018-a74875b364 Too bad dnf doesn't

Re: Heads up: selinux-policy-3.14.1-25.fc28 breaks GDM

On Wed, 2018-05-23 at 20:13 -0600, Jerry James wrote: > [1] Which is totally useless, by the way. It says "Oh no! Something went > wrong!" (Great. *WHAT* went wrong?) and informs me that I must logout. I > wasn't logged in. There's a nice logout button there, but it can't be > pressed.

Re: Heads up: selinux-policy-3.14.1-25.fc28 breaks GDM

On Thu, 2018-05-24 at 08:09 -0600, Jerry James wrote: > On Thu, May 24, 2018 at 12:39 AM, Heiko Adams wrote: > > > I can't confirm that. Maybe because I relabel my system after every > > selinux policy update. > > > > As I said in the original message: > > "I did a full

Re: Heads up: selinux-policy-3.14.1-25.fc28 breaks GDM

On 2018-05-24 10:09, Jerry James wrote: The problem may be restricted to systems using the Nvidia proprietary driver. I have that driver and was also affected, though am using sddm rather than gdm.  My work around was the following local policy: ~~~ module local_sddm 1.0; require {    

Re: Heads up: selinux-policy-3.14.1-25.fc28 breaks GDM

On 05/24/2018 04:09 PM, Jerry James wrote: > On Thu, May 24, 2018 at 12:39 AM, Heiko Adams > wrote: > > I can't confirm that. Maybe because I relabel my system after every > selinux policy update. > > > As I said in the original

Re: Heads up: selinux-policy-3.14.1-25.fc28 breaks GDM

On Thu, May 24, 2018 at 12:39 AM, Heiko Adams wrote: > I can't confirm that. Maybe because I relabel my system after every > selinux policy update. > As I said in the original message: "I did a full SELinux relabel immediately afterwards. Nothing relevant changed

Re: Heads up: selinux-policy-3.14.1-25.fc28 breaks GDM

I can't confirm that. Maybe because I relabel my system after every selinux policy update. -- Heiko Adams Am 24. Mai 2018 04:13:25 MESZ schrieb Jerry James : >I installed the latest batch of updates for F28 tonight. Since that >included a new kernel (4.16.10-300.fc28), I

Heads up: selinux-policy-3.14.1-25.fc28 breaks GDM

I installed the latest batch of updates for F28 tonight. Since that included a new kernel (4.16.10-300.fc28), I rebooted. The system came up with the GDM panic screen [1]. I rebooted into the previous kernel thinking that something might be wrong with the new one. Same result. I rebooted