Fedora Account System
Red Hat Associate
Red Hat Customer
After updating two separate systems, both of them crash on starting up a Plasma session. Plasma Keyboard crashes several times, then plasmashell. I have tried replacing the various KDE configuration files to no avail. Looking at the core dump under gdb, it seems to be crashing inside FontConfig. Reproducible: Always Steps to Reproduce: 1. Update Fedora 44 to plasma-workspace-6.7.5-1.fc44 2. Start a Plasma desktop session 3. Actual Results: Plasma Keyboard then plasmashell crash Expected Results: Desktop starts
Created attachment 2159022 [details] Stack trace of the crashing process
Note, this does not happen on the same system with a totally new account, so *something* in the configuration is triggering it, but it doesn't seem to be any "obvious" place. I will try to narrow it down as time permits, but it is 100% reproducible for me *and* I can reliably get a core dump, so if I can assist with debugging the problem let me know. I have attached the coredumpctl information showing the stack trace. As I mentioned, plasma-keyboard (6.7.5-1.fc44) also crashes. The coredumpctl info for it shows a shorter but still very similar stack trace. I will keep these core dumps around for a bit longer in case they can be useful.
Created attachment 2159023 [details] Stack trace from plasma-keyboard
Just a headsup, if this winds up being a packaging bug, then this ticket is fine, as this is something we'd need to handle. Otherwise, you might be better served by submitting a ticket upstream. To which component though, that I wonder...
Hi, I'm on an old laptop, Core 2 Duo with Intel internal GPU. I run Fedora 44 Plasma. I think I'm having a similar issue. After a recent update my sddm started crashing (I tried switching between sddm X11 and Wayland). I tried switching to plasmaloginmanager but it's crashing too. Then I set sddm to autologin my user, I tried both plasma and plasmax11 sessions, both crash. A dialogue about crashed "Plasma Keyboard" shows. I can still use text console or ssh. When I run `journalctl --user -b -e --no-pager`, it seems like plasma tries to start but keeps crashing on multiple components.
I have filed an upstream bug: https://bugs.kde.org/show_bug.cgi?id=526472 It is obviously hard for me to know as a user if this is caused by a packaging issue, an upstream issue, or an interaction with other packages issue.
Well, it turns out to be a bug in Chromium/Google Chrome, see links from the upstream bug.
I don't use chrome, I don't have it installed. In my case sddm and plasmalogin crash. I cat autologin into a Sway session and it works. I can run konsole and okular but running kinfocenter crashes.
Ok, I think mine is something else. I configured sddm to autologin to Sway session. It works, I can run `konsole` and `okular` but when I tried running `kinfocenter` I get this: ```KCrash: Application 'systemsettings' crashing... crashRecursionCounter = 2 zsh: illegal hardware instruction (core dumped) kinfocenter``` To me it looks like it was compiled with an instruction set that Core 2 Duo doesn't have (per my previous post I'm running Core 2 Duo with integrated Intel GPU (Intel(R) Core(TM)2 Duo CPU T7250 @ 2.00GHz))