I have a problem after upgrading my system from F42 to F43. I can no longer start a Gnome session, if I do, the gnome-session-init-worker process crashes an creates a core dump. I opened a bugzilla issue and found a similar one here. What I’m really worried about is the message I received in response from the automatic triaging system, which seems to indicate that I should not expect to get someone’s attention for this grave bug. Is it really the case that reports of fatal errors in a central component like gnome-session are not acted upon?
Don’t worry, it will be fixed 
1 Like
If it helps I just got hit by this tonight. Here’s what I found:
First, gdm was trying to do some relabel operations, selinux was denying that. this ended up being a red herring.
On my system I generated a new type enforcement policy to get past that part, but after testing once the root cause (more on that in a sec) was corrected i remove the semodule and verified everything still works (it does)
If you wanna follow along at home for the debugging steps, you could just set it to permissive temporarily (but it doesn’t fix the problem and very much do turn it back on after getting your logs), but you could just check if you have the issue I had directly without turning it off. in my case, my /etc/gdm/custom.conf had “WaylandEnable=false” due to my install being a few years old, and with f43 dropping support for x11, that ended up being the problem. If yours is set to false on 43+ it’ll bite you, needs to be true, we have finally entered the year of the wayland desktop.
No. I don’t have that line in my custom.conf file
Hi Thomas,
You might want to try this ….