Bug 2548952 - Plasma, sddm: illegal hardware instruction
Summary: Plasma, sddm: illegal hardware instruction
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: plasma-desktop
Version: 44
Hardware: x86_64
OS: Linux
unspecified
urgent
Target Milestone: ---
Assignee: KDE SIG
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-10-10 08:02 UTC by Martin
Modified: 2026-10-24 09:31 UTC (History)
6 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2026-10-24 09:31:51 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Martin 2026-10-10 08:02:52 UTC
I'm on old Dell laptop with this CPU: Intel(R) Core(TM)2 Duo CPU     T7250  @ 2.00GHz

A recent update of system, and probably KDE Plasma in particular, resulted in this problem. Looks like some components of the system were compiled with flags targetting it for newer CPUs. sddm (greeter probably), Plasma Desktop and apps like kinfocenter stopped working with an error like:
`zsh: illegal hardware instruction (core dumped)  kinfocenter`

I was able to configure sddm to autologin into a sway session and that works but still can't run some of the kde apps. Apps that do work include konsole and okular.

Running `/lib64/ld-linux-x86-64.so.2 --help` gives this: 
```Subdirectories of glibc-hwcaps directories, in priority order:
  x86-64-v4
  x86-64-v3
  x86-64-v2```

Reproducible: Always

Steps to Reproduce:
1.Turn on the laptop
2.Wait for SDDM login to show up

Actual Results:
SDDM login never shows up, it either drops to text mode or leaves the graphical mouse cursor visible (when sddm is configured to use wayland)

Expected Results:
Login screen appears, user can log in, plasma desktop and related apps work.

Comment 1 Martin 2026-10-24 09:31:51 UTC
The culprit was `vvdec-libs-3.0.0-5.fc44.x86_64` package. It comes from rpmfusion-free and removing it fixes the issue.


Note You need to log in before you can comment on or make changes to this bug.