Dear Rocky Friends,
I was just rebooting a device, then this happened (Image).
I pressed Ctrl+ Alt + F2 & then systemctl status sddm.service
How do i resolve this issue please (anyone had this before)? 
What happens if you start it?
Is anything in /etc/sddm.conf or /etc/sddm.conf.d/ changed from the default settings?
1 Like
Well the useful information is further down below your cropped screen capture where it usually states how it failed or if not that the command to gather more information. As it is we know no more than what is seen in the caption.
So how did you get to this point since yesterday you couldn’t install KDErocky10?
sudo journalctl -b -1 -u sddm.service
might glean more info. You might run journalctl -b by itself to see the entirety of the boot messages in the event there may be other clues.
Other things that you can impart that might help us is to describe what actions you were taking prior to this event in the configuration of the system.
It is not clear wether this install is based on rocky 10.0 or 10.1 as there is no 10v.
1 Like
Thank you for your reply.
Well nothing happens when i start and i can browser to the files.
/etc/sddm.conf or /etc/sddm.conf.d/, but how can i tell if it has changed please?
I was only trying to update the OS after the repo changes by rhel/centos/RL…as announced. It was working fine, but froze when i launched the terminal, so i rebooted and this happened 
.
I can’t reinstall from scratch again, after another RL had a blank screen 
.
Thank you, i meant version 10 (10v kde desktop), which is the iso on the RL download link. That was the only details i had - cropped img.
- Installed RL a while ago but reboot failed and went blank, so i reinstalled it as i couldn’t find any soln (the post you saw yesterday).
- …but another RL now has this new issue after i tried to update via the terminal (it froze upon launching the terminal so i rebooted and the sddm failed). So now I’m stuck
. I don’t wanna reinstall another RL. - The cropped images are the exact details…the top bit pops up after booting. The 2nd image is after i typed the status command. No additional details were displayed.
- Device was working fine, then i rebooted (when terminal didn’t launch…slow or froze). I only wanted to update the OS.
Cheers 
The problem is that you have yet to provide any meaningful error information. The screen capture is the result of something else. Its like a picture of a house burning down and then you asking us to tell you what caused the fire. There’s just a thousand possibilities.
I gave you some tools to start the search for the cause yet you ignore them.
It may take some of your time scrolling through the output of those commands to start seeing relevant error information, but it is color coded to highlight problem issues.
From these comments it is hard to tell if we are talking about one install / reinstall on one machine or multiple machines. Are you doing the default install w/o adding any external software outside the rocky/ epel repositories?
1 Like
Thanks, again appreciate this forum 
- I’m only installing the default ISO (kde version), i don’t add any other desktops, apart from brave/chrome & other general tools from Rocky repo via KDE - for testing on 2 machines, epel is already installed with RL 10 KDE version.
- So, i tried to (systemctl) disable, enable & restart …all failed after kde dots flashed on the screen (turned blank).
- Please see images (journal) (tried to crop it without taking too much space on the forum ). I really don’t want to reinstall.
- journalctl -u sddm.service
- journalctl -o verbose | grep sddm.service
- journalctl | grep sddm.service
it seems to me that the first error line is this:
/usr/bin/sddm /lib64/libQt6Core.so.6 version '“Qt_6.9” not found
Google Gemini tells me that “The problem is that the SDDM package is too new for the Qt 6 library package.” and further that
“version 'Qt_6.9' not found: This is the core issue. The SDDM executable requires symbols (functions, etc.) associated with the Qt_6.9 version tag within the libQt6Core.so.6 library file. However, the installed library file only contains an older version of the core components (e.g., perhaps Qt_6.5 or Qt_6.7).”
Could this be a mismatch between 10.0 and 10.1 ?
Tony
1 Like
So now we’re getting somewhere. In the top caption it says /usr/lib64/libQt6core.so.6 is not found needed by blah blah.
My guess is that your machine crashed in the middle of an update or was rebooted before the update completed. You can try finding out what package provides this file with dnf and then reinstalling it. Since I’m running RL9 I can only go through the motions thus:
sudo dnf --releasever=10.1 provides */libQt6Core.so.6
Last metadata expiration check: 0:01:46 ago on Sat 29 Nov 2025 10:44:20 AM EST.
qt6-qtbase-6.6.2-1.el9.x86_64 : Qt6 - QtBase components
Repo : epel
Matched from:
Filename : /usr/lib64/libQt6Core.so.6
qt6-qtbase-6.9.1-1.el10.x86_64 : Qt6 - QtBase components
Repo : appstream
Matched from:
Filename : /usr/lib64/libQt6Core.so.6
Well that search worked by adding the “–releasever=10.1” to the dnf provides line.
The missing file is provided by the package qt6-qtbase, the command line would be:
sudo dnf reinstall qt6-qtbase
This may fix sddm but I’m worried that it is not the only problem if my hunch is correct about how this came about, crash or premature reboot, as there may be many more incomplete updates. In which case there is no way to fix it.
1 Like
Technically it could be recovered. I would first check with:
dnf update
to see if any remaining updates can be applied or not if it didn’t finish updating. If there is a failed transaction, dnf should inform us if that is the case. If not, then a potential option is:
dnf reinstall $(dnf list installed | awk '{print $1}' | grep -v Installed)
which would reinstall all packages. It may or may not help, but could fix some things if some packages only partially installed or didn’t run the pre/post scripts.
Otherwise we’d need to see what the failed dnf transaction shows if there is one, and potentially use an alternative method to recover.
1 Like
Thank you all…
- when i try ALT + CTRL + F2 & login as root - dnf update or upgrade , i get this:
- When i try : rpm -qa | grep qt6-qtbase, i get this:
Please Help ?
Unfortunately if dnf is borked then there is no way to fix. Even I would have to start over, which I had to do when a system disk had write errors.
1 Like
Reinstalling …upgrade seems to be working fine - cheers, appreciate all the support. God bless
1 Like
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.