My question is these processes are all immediately dying at login time preventing login, these aren’t slow edge condition style core dumps. Why are these being pushed out even on rawhide like that? I would think these critical processes instantly dying would show up with even the testing automation rawhide gets
May be a hardware issue.
I have rawhide + Kde on my laptop (intel +nvidia) and on my desktop (RTX 4070 sti) and I have no problem.
I have been using only rawhide for at least 5 years. The few problems I have had concern some critical package updates like glibc. When that happens I download the old versions on fedora koji and I do a downgrade.
FYI, critical-path rawhide builds all go through a gating CI that tests a bunch of things. It can of course miss things that are hardware specific or the like, but in general it works pretty well.
SIGABRTS are not something thats expected at all.
I’d suggest filing a bug (to start with) on plasmashell so developers can help track it down. If you want something more interactive, the #kde:fedoraproject.org matrix room may be able to help isolate whats going on.
FWIW, kde (wayland) runs fine here in rawhide. No particular problems.
I mean they shouldn’t be pushed out so fundamentally broken they instantly core dump. Isn’t there’s a test framework that checks for that?
Anyway, the update I did on 1/21 seem to fix it, which was weird because the packages updated had nothing to do with plasmashell